A daydream of a big game and thoughts therof.I've been thinking about Big Games (see post below). The event is described below in the form of stages, eventually I wish to use this as a framework for a big game plan, a brainstorm of an ideal. By compiling this over several days and letting it roll around in my brick-for-a-brain, I should come up with something.
This post should be best understood after reading my previous entry, An appeal for Big Games
which is found below. This post will most likely be edited if folks make comments on it.
Six weeks before the game event: The planning.Six weeks before the big game begins, the event is described to all of the participants, the date has been set for months, and some money has been pooled to secure the site. Players are divided into teams, ideally six or more per side. Each team decides upon a general, these generals and the game designer meet to receive secret missions, team-specific objectives, intel on the enemy, fluff, et cetera. The generals then confer with their team. They come up with a plan, a real plan on how to handle the enemy. Generals are given the ability to assign players to certain locations in the game, or to specific skirmish tables, according to the wishes and availability of the players. Things like when-the-player-is-showing-up and what-kind-of-army-the-player-has is considered. Since the first night (see Friday night) are smaller games, generals should be able to arrange challenges and call-outs made by players (e.g. Boroth vs. Cterry smackdown), and encourage their teammates to tailor-design their armies to handle a specific task.
The big game is a big event for the year. There's no reason why all the strategy has to happen Saturday evening after beer number five.