Template talk:Festival timetable

Suggested rename

Since GW2 has "events" as a major mechanic, could we rename this to "festival timetable" to avoid confusion? —Dr Ishmael 16:07, 14 June 2013 (UTC)

I have no problem, that's a good idea. I'll go ahead and move it before people do much editing. Vahkris (talk) 16:33, 14 June 2013 (UTC)

Updates needed

I pulled over the Timetable from GWW because it was a quick and dirty way to get a timetable in (couldn't see one existing) for the fireworks finale. Some players were asking for some way to track the schedule, and I remembered we did this on GWW before. Currently, though, the timetable only supports 12 rows, so only about 24 hours will be tracked whereas the fireworks finales take place over 4 days. If we could clean it up and get something where it'll show the entire schedule instead of just 24 hours, I think that'd be good.

Current use: http://wiki.guildwars2.com/wiki/Dragon_Bash#Dragon_Bash

I have no clue how to make the needed updates to prevent updating it every day, so looking for those who have skill to look at the table and see what updates can be performed. As far as I'm concerned, if someone wanted to rewrite it to make it better, I'm all for that, as long as it displays properly and retains the ability to update via the existing link.

We should be able to arraymap it in a similar manner to SDRH. -Chieftain Alex 16:47, 14 June 2013 (UTC)

So...apparently the Dragon Bash fireworks are not based on real life time, but on in-game time, so a schedule timetable is pretty much useless unless we can somehow grab each server's current in-game time. I don't know if this timetable will be useful in later events, but if they're going to remain using in-game time I don't see much use unless we can gather the aforementioned times. Vahkris (talk) 17:15, 14 June 2013 (UTC)

Unlucky. I'm sure we'll find a use for it. It should probably use {{UTC time}} to show the times. -Chieftain Alex 17:17, 14 June 2013 (UTC)

Yeah, we should still clean it up and get it to work with multiple days, etc, but not as pressing a concern at the moment. Vahkris (talk) 17:19, 14 June 2013 (UTC)

EU servers use UTC as server time; US servers use PST/PDT. That's the only "in-game" time I know of. —Dr Ishmael 17:34, 14 June 2013 (UTC)

Vahkris talks about the in-game day and night cycle within maps. No idea how that works though. poke | talk 17:46, 14 June 2013 (UTC)

I don't even know if there's a way to determine the in-game time (within the 2 hour day/night cycle)...other than the Ghastly weapons. There's no /time command. Is there even a clock in-game? Vahkris (talk) 17:56, 14 June 2013 (UTC)

No, nothing. The only other way would be looking up at the sky :P poke | talk 17:58, 14 June 2013 (UTC)

OH, that. I guess that makes sense, so that the fireworks always go off at night. —Dr Ishmael 18:07, 14 June 2013 (UTC)

(Reset indent) Well, I've made a template that should work fine at User:Chieftain Alex/sandbox10. I'm not sure that the "currently in progress" event should have grey text though. thoughts? -Chieftain Alex 19:08, 14 June 2013 (UTC)

I think the "active" event/interval green bar should be more opaque. I could barely see the green. Another concern I have is that if you go to the full 48 rows it becomes an incredibly long table. Is there any way to force it to extend to the right so it doesn't take up as much vertical space? A full weekend event timetable at 2 hour intervals will create a really long table to scroll down...unless it's not intended to show everything at once. Vahkris (talk) 20:13, 14 June 2013 (UTC)

I've changed the colour of the green bar. We could make it do columns instead of rows easily. I could make it such that it only displays say 10 events at once, the interval prior to the active one, and the next 8. The 48 was really just for fun, you'd probably just use 12 intervals. -Chieftain Alex 10:36, 15 June 2013 (UTC)

1. User:Chieftain Alex/sandbox10 - closest to the function of {{festival timetable}}.
2. User:Chieftain Alex/sandbox9 - similar to #10 but also has an option to display the table horizontally.
3. User:Chieftain Alex/sandbox7 - similar to #9 but removes intervals that have passed.

personally I think 10 is fine, that rows overcomplicate things, and that hiding previous intervals is awkward but saves space - so its necessary if you're using a horizontal version. -Chieftain Alex 12:33, 15 June 2013 (UTC)

I should add that I'm not sure it needs to display the date below the days that aren't the first day. Perhaps only display the date beneath the first entry for that day? -Chieftain Alex 12:40, 15 June 2013 (UTC)

1. User:Chieftain Alex/sandbox10 - as #10 above, but only displays date beneath row if it hasn't been displayed before. -Chieftain Alex 13:20, 15 June 2013 (UTC)

The horizontal version is difficult to parse, I don't like it. I like #7, removing past intervals, because they no longer matter and don't need to clutter the display; keeping the immediately previous interval would be fine for reference (how much did I miss it by??????). If you could make #7 display more than just the next interval (isn't that what timescale is for? doesn't seem to be working), that would be perfect. —Dr Ishmael 14:20, 15 June 2013 (UTC)

The end date on #7 was set to be too soon/not a big enough timescale value, using it with a longer date shows many more rows.. -Chieftain Alex 14:23, 15 June 2013 (UTC)

old sandbox version {{User:Chieftain Alex/sandbox7 | start = June 14 2013 18:00 | end = July 22 2013 08:00 | interval = 240 | timescale = 12 }}

It's only showing 2 rows. ----------------------------->

I think part of the problem might be this line:

-->{{ #ifexpr: {{#var:now}} > {{#var:utc}} | {{#ifexpr: {{#var:now}} < {{#var:utc next}} | {{#vardefine:after green bar|+}} }} }}<!--

The way Variables works, #vardefine functions are always parsed, even if they're inside an #if. You have to perform all the conditional operations within the #vardefine, not outside of it. —Dr Ishmael 15:02, 15 June 2013 (UTC)

Oops, I meant that the number of entries was too small for the old date. I think that setting to 12 resolves the problem you were describing, still something wrong? -Chieftain Alex 15:06, 15 June 2013 (UTC)

Hm, then it's not working how I expect it to work. I expected timescale to define how many entries are displayed. With it set to 12, it only shows 8 (which is in line with only showing 2 when it's set to 6). Apparently I don't understand how timescale is supposed to work. —Dr Ishmael 15:25, 15 June 2013 (UTC)

perhaps "max entries" would be a better name for it. -Chieftain Alex 15:36, 15 June 2013 (UTC)

(Reset indent) the wierdest thing about the most recent version at User:Chieftain Alex/sandbox10 is that {{UTC time}} isn't doing the javascript bit, even though it worked on sandbox 7+9. -Chieftain Alex 15:50, 15 June 2013 (UTC)

There's a JS error, line 127 in MediaWiki:Common.css: date.setUTCHours(time[1], time[2], 0, 0); Uncaught TypeError: Cannot read property '1' of null —Dr Ishmael 16:27, 15 June 2013 (UTC)

Lol. All those problems just caused by a single space between the time and the end of {{UTC time}} :D -Chieftain Alex 16:29, 15 June 2013 (UTC)