Game Selection

Table Game Selection
Table Games are selected prior to the start of a season. Players are responsible for building a team and applying to the game of their choice after the tables for the season are announced. The application process is as follows:
 * Players will build a team and decide which table they wish to apply to.
 * A chosen member of that team will send the team roster to the Plot Admin. This must contain, player name and character name for each player and which game the team is applying to.
 * A team may not apply to more than one game a season
 * A player may not apply with more than one team at a time
 * The Plot Admin will announce how many teams have applied to a game as they apply. Who applied to what games and with what team will remain secret until the deadline of submission
 * The Plot will submit the teams to the Admins who will go over the teams and choose which team sits at what table based on the laid out criteria

Table Games are selected with the following criteria in descending order:


 * The team with players who have not played in a table game the direct previous season
 * The team with the most players who have not played in a table game
 * The team with the lowest amount of collective seasons playing in table games
 * The team with the least amount of games played overall
 * Further ties will be broken by the Admins

Opportunity Game Selection

 * Opportunity Games are posted in the #job-board channel on the server. A game posted 4 days in advance will be open for applications until UTC 400 the day before the run, or 24 hours prior, whichever comes first. A game posted less than 4 days in advance is open for applications until 30 minutes prior to the run time. When applications close, the Head GM or a designated Admin is responsible for determining the resulting team based on Weighted Game Counts, who will be pinged with the news.
 * Weighted Game Counts are determined by taking your Seasonal Game Count and applying a multiplier of (1 + the number of games you have been awarded for this server week). Table games are considered to have been awarded for the entire server week.
 * Games that use Opportunity Recruitment accept applications from players in the following types.
 * Individual: A single player, with Weighted Game Count X.
 * Soft Group: A group of players (maximum 5), with averaged Weighted Game Count X and Low Game Count Y. This group will break down into Individual players to fill seats allocated to it if it is larger than the seats allocated.
 * Hard Group: A group of players (maximum 5), with averaged Weighted Game Count X and Low Game Count Y. This group will forfeit all seats allocated to it if it is larger than the seats allocated.
 * Clique Group: A group of players (minimum 4, maximum 6), with maximum Weighted Game Count X. This group only receives the game if no other applicants have a lower game count than the team's, but can 'blank' any excess seats instead of causing additional breakdown offers or backfill attempts.
 * A player may not apply to the same game more than once.
 * Opportunity games have 6 seats, which are assigned in order of lowest game count to highest. An Individual in the lowest six game counts receives one seat. If a group is in the order of the lowest six game counts applied, that group receives seats until either they have received one seat for each member or until there are no additional remaining seats. If there are seats remaining after every Individual and group has been considered, groups that have forfeited seats are simultaneously offered a second opportunity to break down into Individuals to fill remaining seats in order. If they refuse, the game follows Emergency Backfill policy for the remaining seats, up until 10 minutes into the Game Session, at which point the GM may decide to run the game understrength.
 * In the event that at any point in this process there is a tie between eligible Individual or Soft Group applicants with insufficient seats to solve, the Soft Group breaks down into Individuals. If there is still a tie between Individuals for an insufficient number of seats, compare the Server Game Count of those Individuals to reorder them. If there is still a tie after this, have each tied player roll a series of #bot-house 1d6 rolls. Each time the high roll goes to a number of players equal to or less than the number of remaining seats, award them each a seat.

Standard Backfills
If your team is selected and does not have a full complement of 6 players when they are awarded the game, you may recruit players from any other teams that applied to that game. This is not a required action and is up to each team to decide. In cases where a player has had to drop for any reason between the team being announced and the game the team may backfill from any other teams that applied first, then may recruit from the reserve players as a whole to fill the spot.

Missing/Absent Backfill
A player is considered Missing 5 minutes after game start unless they have informed the GM prior to the game start in that GM's game channel. If they have informed the GM prior to game start, they are considered Missing 10 minutes after game start.

The GM must ping any players who have not joined the Voice Chat once they are considered Missing, in their game channel. Missing players are allowed a 5 minute window, once they have been pinged. If they do not join the voice channel within that window, they are marked Absent and are no longer participants in that game. (Their game count is still increased as if they had played.)

Backfills are chosen by whoever posted the submission for the team.

Personal Runs

 * The spiritual successor of a Side RP, this is a complete run designed for either 1 character or up to 6 characters. Any player can put in a request for a Personal Run that covers a certain topic or achieves a certain goal, with as much detail as they can provide. These runs go in the soon-to-be #run-request channel for GMs to see. All run requests must be approved by the Head GM or an admin prior to being picked up by a GM. All Personal Runs a GM will run must be submitted in #run-submissions for final approval.
 * Format Components
 * Run Title (optional)
 * Run Date/Time: the requester is responsible for updating this as their availability changes. If the Date/Time has passed without an edit for longer than a week, the request will be archived and removed from the channel.
 * Characters Involved: Any characters pre-included in the run. Include Opportunity here if you would like the open seats to be posted as a job.
 * Run Structure: any requests on how the run should be structured should be here.
 * Run Theme: Tonal preferences explained here
 * Nopes: Anything that isn't prohibited by the Code of Conduct that you would like to avoid encountering in the game.
 * Objective: Reward or Effect you would like the run to have. Please keep in mind that the effect of your Personal Run, if quantified by XP, cannot exceed the reward metric for the final run. Non-XP rewards, like changes to setting elements or Break-a-Rule requests, may be instructed to be part of a longer narrative that will either shape your gameplay for a duration or require a number of Personal Runs.
 * Priority: Every Season, every player can submit one Priority run request, which qualifies for the 2 XP Scheduled Run bonus for GMs who pick them up.

Team Building
The Neon Jungle LC permits players to organize a set of characters into a persistent in-setting team. The team is permitted the following features.
 * 1) A team will be provided with an IC channel for players to interact IC with each other
 * 2) A team may request a pingable Role for each member to share, with a color of their choice that is not in use for Admin, Manager, or Moderator roles. The team may request their role to have color priority over the Reserve role if they want to use their own color, but not over the proscribed role types.
 * 3) Teams may apply to the seasonal table games during the off-season window.
 * 4) A team must consist of no less than 3 and no more than 6 characters
 * 5) A character may not be on more than one team
 * 6) A player may not have more than one character on the same team
 * 7) Teams must be submitted to an Admin for approval; modifications to the roster may be requested at any time.