Widget talk:Linked worlds

Widget name

World linkings would be a more fitting name, and this would be the official name for this as well. —Nefastu 02:11, 14 January 2017 (UTC)

And with less dashes and titlecase.--Relyk ~ talk < 07:24, 14 January 2017 (UTC)

How about "Linked worlds"? (but yeah I agree the direct translation of the german isn't the greatest title ever) -Chieftain Alex 10:53, 14 January 2017 (UTC)

"Linked worlds" is fine. —Nefastu 15:12, 14 January 2017 (UTC)

Current score

In my opinion the current score columns isn't really needed, because it doesn't present any meaningful data. The current score is the sum of all the war scores of each skirmish, but this value doesn't have any impact right now. Currently, the place of a server in a matchup is determined by the sum of victory points awarded for 1st/2nd/3rd place (i.e. 5 points for the 1st, 4 for the 2nd, 3 for the 3rd) in skirmish depending on the achieved war score in the 2 hours a skirmish last.

So if you are interested in expanding this and making a wiki WvW match overview, then I suggest to add the following columns:

• Current skirmish war score
• Current income

---

• Number of castles owned (i.e. only Stone Mist Castle)
• Number of keeps owned
• Number of towers owned
• Number of camps owned

---

• Number of 1st places
• Number of 2nd places
• Number of 3rd places
• Victory points (this determines who wins the matchup)

---

• Kills
• Deaths
• KDR (Kills/Deaths Rate)

--Tolkyria (talk) 20:36, 12 July 2019 (UTC)

Hum. Good point on score not being used anymore to determine match placement. I hadn't realised that tbh. For the moment I've just switched Scores for Victory_Points - I wanted a quick way to check which world would be moved up/down in the next matchup. -Chieftain Alex 12:41, 13 July 2019 (UTC)

Thanks. Well, I took a look into the API and have to admit that I clearly underestimated the amount of available data which is needed to implement my suggestions. This is something for... ahhh... the future. --Tolkyria (talk) 19:03, 13 July 2019 (UTC)

Bug: Mobile

Been reported this widget fails to render the last cell in the table on mobile view only. Assume this is because I didn't migrate it to use proper js nodes like many of the others. -Chieftain Alex 23:06, 4 May 2021 (UTC)

Well.. technically the problem is that there are literal HTML ending tags used within the script tags that which the mobile parser apperently (for whatever reason that might be) removes. Nightsky (talk) 16:01, 5 May 2021 (UTC)

Yay I didn't fuck up the migration too badly. Bug is fixed now. -Chieftain Alex 17:23, 5 May 2021 (UTC)

Wrong display for NA worlds

Since the beta ended the display order for NA worlds is wrong, showing the linked server first and host server second. EU servers appear to show the order correctly. API seems to be reporting the correct order so issue is with the widget. Latest relink announcement for reference. --ItVictor (talk) 08:01, 3 February 2024 (UTC)

Thanks for reporting this. When I did the rewrite I only had the beta worlds visible.

EU was also showing wrong on a few links, I had the comparison operator inversed in the line putting the lead world at the front.

I've changed it to be a different method to do the same thing since I think its clearer what its up to.

            // For non-beta worlds, put the parent server up front. Don't do this for beta worlds since the parent world is invisible.
            if (!beta_flag) {
                links_clean = [v.worlds[c]].concat(links_clean).unique();
            }

-Chieftain Alex 10:55, 3 February 2024 (UTC)