Talk:Defeat the invading Awakened
Unique NPCs[edit]
I've been seeing some unique NPCS participating in the awakened portal events. I saw Exemplar Kerida with a pair of Shining Blade in two different locations in Queensdale, and I ran across Ballista Geargrind, Mangonel Gearstrip and a group of Iron Legion Marksmen in the Plains of Ashford. They have dialogue on current events during and after the event. Are there any similar NPCs in other maps? —The preceding unsigned comment was added by Finleyeff (talk).
- I've got Peacemaker Ninn in Metrica, and now Sigfast and Skarti in Wayfarer's. Seems like they all have something different. The grunts have a different end line if your race matches. SarielV 07:57, 20 January 2018 (UTC)
Now Southsun Cove should be addet to the possible locations. 79.18.63.89 19:26, 24 April 2018 (UTC)
Feedback 2018/04/24[edit]
This event's scheduling may have drastically changed in the Apr. 24 patch. Checked at 9:30 PM server time, and the only portal incursion reported by the Phasic Distortion Reader was Queensdale. --Hindbrain (talk) 21:35, 24 April 2018 (UTC)
From what I've gathered from others' information, there was an event in Southsun Cove at 6:30 server time. I witnessed Caledon Forest at 8:30, Queensdale at 9:30, Wayfarer Foothills at 10:30, Plains of Ashford at 11:30, Gendarren Fields at 12:30, Southsun Cove at 13:30, and Metrica Province at 14:30. I'm not sure which one was up at 7:30 server time, but I suspect it was probably Metrica Province. Given this data, the Awakened will continue to come forth every hour cycling through the seven zones. This means that the time of day will not dictate which zone will be active, making tracking a little more difficult without a phasic distortion reader.-- --Dharkon (talk) 02:21, 25 April 2018 (UTC)
The most recent Southsun event happened at 8:30am server time.[edit]
The next one should be at 3:30pm server time, assuming that it's 7h after the previous one. --138.75.82.239 10:21, 25 April 2018 (UTC)
Feedback 2018/12/01[edit]
Feedback from Friends of mine ( new players) who use this page. New players will not be familliar with the map names. So the table is hard to read because it is not organized/ ordered by day and they dont remember the map sequences. The ideal design for the table is (column x row by Time x Day) instead of ( Time x Location ). This is also easier maintained in the future as the column/row names do not need to be modified if anything changes in the sequence of locations.
I have prepared an image table of such a design using the data from original author where credit is due. --PlatinumHobo (talk) 05:27, 1 December 2018 (UTC)
- I agree that the current table format is really hard to parse, Dulfy's is much easier. Maybe there could be a running "next zone" table in the vein of Template:World boss table. -- kazerniel (talk) 20:50, 4 March 2019 (UTC)
- Alternatively it could be added to the Event timers page. -- kazerniel (talk) 10:29, 6 April 2019 (UTC)
Something Wrong with Schedule[edit]
At 8:30pm Central on Thursday 10/17 the schedule said the event would happen in Queensdale and everyone was waiting there. At 8:33pm I decided to start going to all the maps to see if the event was elsewhere or bugged. I found the event in Gendarran Fields but we were too late and the event failed. Is there any way to determine the location / time of an invasion without using the schedule on this page or going to each map? --Justaplayer (talk) 01:44, 18 October 2019 (UTC)
- Yes, you can use the Phasic Distortion Reader. --BuffsEverywhere (talk) 11:32, 18 October 2019 (UTC)
Feedback 2020/10/17[edit]
Something is off with the timer. Twice now the grid has said the invasion would be in Metrica when it is actually in Wayfarer. See Saturday 10-17-2020 at 20:30 eastern. --71.246.233.186 00:25, 18 October 2020 (UTC)
- Right now it's Sunday 12:30 UTC (13:30 local time) and it's correctly predicting Caledon Forest which I have confirmed ingame. Unless different days are incorrect, timer looks ok atm. -Chieftain Alex 12:32, 18 October 2020 (UTC)
- I beleave this (and the above for that matter as well) is to do with the way the schedule is presented. While it will be correct for everyone that is observing UTC, it will indicate something wrong for everyone else. As the times on the sides are adjusted to the local timezone, they will wrap over in one of the two directions depended on the sign of the observed offset from UTC. In other words this means that a full 0 to 24 cycle is no longer wholely contained within a single column. That effectively means people will consult two different columns over the course of their observed 24 hour day. As their 24 hour day is however offset from the 24 hour UTC day that is displayed in the table, there will be so many missmatches as their offset from UTC (at least for not 1/2, 1/4 and 3/4 offsets) as people will consult the wrong column as while it might be the previous or next day for them already, it would still be the next or previous day respectively as observed at UTC. Nightsky (talk) 05:21, 19 October 2020 (UTC)
- Seems obvious when you note the day of the week won't be the same for everyone depending on their offset and how close they are in the day to midnight. Shall we just change the table to UTC only? -Chieftain Alex 12:30, 19 October 2020 (UTC)
- I've done my suggested change. We could also change it to a single long column of Days + times in column 1, and Zones in column 2, which would allow us to use the "day" parameter of Template:UTC time. -Chieftain Alex 12:34, 19 October 2020 (UTC)
- (Edit conflict) I like your change for the times to be in UTC only. I however also have no trouble with the conversion between my local time and UTC, which might however not be the case for everyone. I guess adding in server time with a link to where to enable a display of it in the options might help those not as familiar with the concept of timezones. I was thinking to have it be a table of times with the zones as heading, though that didn't turn out as easy to understand as i hoped it would. (At least i think it didn't. I understand it but i guess it's maybe a bit overloaded in the amount of text it has and as such might not be particularily obvious to understand within a reasonable amount of time?) Your idea sounds good. I assume you mean to have it be a template and rotate though, as otherwise it would still wrapp around again, altough to a lesser extend. (Although it would also wrap around if it were a rotating template; at least if it then still covers a full week and doesn't also include dates to make it unambigous.) Nightsky (talk) 18:46, 19 October 2020 (UTC)
- Killer template Nightsky, nice work. -Chieftain Alex 16:55, 22 October 2020 (UTC)
Yellow highlighting not working[edit]
Yesterday (and previously) this page would have one entry highlighted in yellow for the next occurrence. But, today it doesn't seem to be working. I tried four different browsers. Daddicus (talk) 00:58, 3 December 2020 (UTC)
Request: Add highlighting regardless of lead time[edit]
I know the table was meant to work like the Phasic Distortion Reader, but in my opinion that doesn’t have any practical benefit. It would be far more convenient to see which location is up next regardless of how much time remains. Even if you know that the times in the table don’t match your local time, trying to cross-reference them across columns is quite a hassle, especially around daylight saving time changes.--Salvatos (talk) 16:59, 17 March 2023 (UTC)
- I've edited the template so it will highlight an invasion from 50 minutes prior until 10 minutes after. That should make a cell always be highlighted. Ideally the highlight would be a different color if the invasion is currently in progress, but there doesn't seem to be a way to do that. --BuffsEverywhere (talk) 04:56, 18 March 2023 (UTC)
- Thank you! That's much better already. I haven't worked with MediaWiki templates in a couple years, but replacing the line that calls the highlighting template:
-->{{Time based highlighting}}</includeonly><noinclude>
- with:
-->{{#ifexpr: {{#time: i|now}} >= 30 and {{#time: i|now}} <= 45 | {{Time based highlighting|css=.highlight-yellow { background-color: lightgreen !important; }}| {{Time based highlighting}} }}</includeonly><noinclude>
- seems to do the trick (i.e. between x:30 and x:45 inclusively, we pass a custom CSS rule to the template to override the highlighting color). I will refrain from applying the change since I'm not very well known here.
- Notes:
- 1. I know it seems like a closing bracket is missing after the CSS rule, but including all three as expected causes one to display under the table.
- 2. We have to keep the class name .highlight-yellow despite the obvious discrepancy in actual color. That's the only class that differentiates the active cell from other potential cells.
- Salvatos (talk) 05:47, 22 March 2023 (UTC)
- Nice! That's a great solution. I've made the change to the template and credited you. However I kept the 10 minutes highlighting and made the color pink.
- We are very easy-going here so please feel free to edit the templates since you clearly know what you are doing :). --BuffsEverywhere (talk) 06:21, 24 March 2023 (UTC)
- Edit: Unfortunately I had to revert the change because the highlight color is only updated when the page is purged. --BuffsEverywhere (talk) 06:52, 24 March 2023 (UTC)
UTC vs local time[edit]
Why is this the only chart on the wiki that displays UTC instead of local time?
Improving the article[edit]
Hello!
Could it be possible to move the time diagram close to the top of the page, like in the Day and night article, where the schedule will be after? This would make easier to catch current situation.
Another request: improve the time diagram by including the current map names to it, like "Awakened invasion on <mapname>", either on the diagram itself, or in a tooltip to the event. Such dynamic change may be not easy to implement, but I hope it's still possible. Thanks! --78.162.40.202 10:07, 29 November 2023 (UTC)