# Talk:Events

## Event Page Name

I don't know. I created Events on 18:49, 30 March 2016. Dhrekr created Event on 06:27, 2 April 2016‎.‎ The same thing happened with They Came from the Holodeck on 20:18, 30 March 2016‎, and Axer made They Came From The Holodeck on 12:56, 31 March 2016. People need to search before creating an entirely new page. Most upcoming events I have been on top of to create the page(s). Both of them should be combined. Jello (talk) 15:25, 25 April 2016 (CDT)

## New Event Format needed for "Supply Missions"

Trying to keep things updated so people understand how to play this new event style. 1. Click on event screen (upper left corner 2. Click 'Enter Event' 3. Collect items that have have all green items (enough of each item to craft larger item) 4. Click on yellow items (enough sub-items to craft main item)

 A. If all sub items are already acquired, select crew to do the building and build it.


5. Click on red items (additional sub-items are needed)

 A. Collect any missing components (clicking on component gives missions that drop it).


.... Fill in rest of page with parallels to regular events.

Lorian Tucker (talk) 14:38, 16 June 2016 (CDT)


## Calendar

Can i suggest that the calendar be reversed. (i.e. The order be flipped) That way the dates are in chronological order. -- 22:39, 27 July 2016 (CDT)

## Question?

What happened to the other event page? Is this the same page just "cleaned up". Having to remember which icons mean "Galaxy Events" vs "Expedition Events" does not seem like an improvement. How do people feel about putting the labels back?

I answered this on your talk page. -- 23:57, 30 November 2016 (CST)

I see that the Skirmish section is a work in progress. I have screenshots of the 3 new Skirmish tutorials, if they would be of any use to whoever is writing/creating that section. ~peregrine~ (talk) 18:55, 17 September 2018 (CDT)

## Organization For Years to Come

As 2016 comes to a close, we have to start thinking about how to manage the event page to prevent an insanely long event list. My suggestion is to split it into multiple pages. Main Events Page would Link to event pages by year. This table is a layout of my suggestion. It is also explained below.

 Main Events Page Events Event Pages by year Events 2016 Events 2017 Events 20## This would be at the top ofevery Event Page by year. {{Template: EventPage}} Yearly Event List using template Event List 2016 Event List 2017 Event list 20##

Each event page would have a template at the top called {{Template: EventPage}} that would contain all header information. (that would keep the top of the page consistent between years). The difference would then be the table of events at the bottom of the page which would continue to use {{EventList}} and {{EventListHeader}}. Let me know what you think. Id volunteer to set this up (Can do it next week).

• Additionally, this is almost mandatory because the current EventList template uses the expensive function "IfExist" to check if the file for the event exists. This can't be removed as we have an event we don't have a picture of. As more events are released, eventually we will get to the point where the using the template will throw an error because of too many expensive function calls.
• Another thought would be to separate the pages by year as above, except have the main events page have links to all the years at the top, then have the rest of the page be the exact same as the current year. (using {{subst::Pagename}} to sub the current years event list)

Thanks, 12:06, 14 December 2016 (CST)

Do you support the organization of Events Page as listed above?
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 01:06, 25 February 2017.
poll-id DD198BF37474A9A604051665A856BF4E

If the only reason for the usage of "IfExist" is that one missing image (I didn't check), then it should simply replaced with a placeholder image, or we should live with a "broken file link". --Crunch (talk) 14:33, 14 December 2016 (CST)
It is also there to prevent a bad file link before an image is uploaded for the event. However, i do agree that a placeholder image should be used. What about using the file below for any current or future events that do not have a file? In that case, i suppose we could just create sections on the event page for years, so each year would have its own table/event numbering, and old years would be collapsed by default. (Uploading file momentarily) -- 19:34, 14 December 2016 (CST)
Suggested Image:
Well, i think i just solved the expensive parser function problem. I removed the ifexist and added an ifeq to the template checking specifically for the event name "Unlikely Heroes", as that is the only event without an image. If future events are added that don't have an image, then the template will need to be modified to nest another ifeq statement with the new event name. Until an image is uploaded for the event, any pages using the template with that event will have a bad file link. This means that using the collapsed table for past years should work. -- 20:04, 14 December 2016 (CST)
I'm in favor of a placeholder image that would be inserted into the base template and can be changed to any uploaded event image. I don't really like hacks like using ifeq. They're ugly and should only be used temporarily. --Darxide (talk) 21:58, 14 December 2016 (CST)
Agreed, however what image would you suggest? A simple solution would be to leave it as i changed it, then when the event is repeated use that image. -- 00:30, 15 December 2016 (CST)
I think even just using a blank image would be fine. Or one with "No Image" across it. Something to quickly indicate that an image is missing and hopefully prompt someone to grab one and upload it before the event is over. --Darxide (talk) 04:22, 20 December 2016 (CST)

## Revising Events page format

If no one objects, I'd like to take a stab at fixing up the Events page. The note at the top of the Events page is correct - it does need some cleaning up. But before I went and started making a bunch of updates all willy-nilly, I wanted to see if anyone had any objections or suggestions. What I'm thinking: Keep the main sections on the Events page with a brief description of the event type. Keep the highlights but move the details to a separate page. For instance, under Expedition Event, the comment "One strategy recommended by Disruptor Beam is to hold stronger crew in reserve for the Elite and Epic missions. The harder the mission, the more victory points Victory Points earned, critical successes also reward more victory points" seems more suited for a details page. Another example, the table of rewards for Faction Missions could be moved to another page. Things like this would certainly help keep this as a highlights page, with more information available on another page(s). As far as the calendars, I would suggest moving previous years' calendars to a single "Events Archive" page. The current year could be kept as is, or separated somehow to reduce the amount of information on the page. I think if making some other changes suggested above, keeping the whole current year would probably be fine. It is certainly less work than constantly moving the information from one page to the other.

So, to recap, I suggest: 1. Keep a brief overview of the event information on the Events page while moving the more detailed information another page (or pages). This include some of the textual information as well as tables and graphics. 2. Move the previous years' events lists to another "Events Archive" page while keeping the current years' events as-is on the page.

Does anyone have any objections or suggestions for this? Mattyj86 (talk) 12:46, 3 August 2018 (CDT)

Everything above sounds good, except will you leave previous years where they are? They can all be collapsed under a new collapsable that named Archive. I will deal with all of that section this fall when i have time to automate the categories list. I want to make a template that autopopulates based on the category Events and uses subpages of the event for information such as crew type and faction. This can be done via DynamicPageList3, but will take a little work to ensure everything is populated correctly. 17:01, 3 August 2018 (CDT)
Also, if you want to move Faction Events (and others) to be subpages of Events: Events/Faction Events, etc. that might help with organization. That way all pages related directly to Events are listed as a subpage. (Pages like Factions are related, but obviously are general to the game, so they should remain where they are.) 17:04, 3 August 2018 (CDT)
Very good. This fell off my radar for a bit but hopefully I can get some work done this weekend. Thank you for the tips! Mattyj86 (talk) 07:17, 7 September 2018 (CDT)