Difference between revisions of "Tronic"

From Armagetron
Line 6: Line 6:
 
=meta: [[contributor's guidelines]]=
 
=meta: [[contributor's guidelines]]=
 
Since all pages on the wiki are editable, all contributions must be constructive and additive: alternative solutions are explored like the growing branches of a tree. Visitors are invited to contribute to to the expansion of any idea, comparing different branches of solutions. Arguments, contention, are conducted in forum, chatroom, or informally through PM's, emails, or telephoney eg skype.<br>
 
Since all pages on the wiki are editable, all contributions must be constructive and additive: alternative solutions are explored like the growing branches of a tree. Visitors are invited to contribute to to the expansion of any idea, comparing different branches of solutions. Arguments, contention, are conducted in forum, chatroom, or informally through PM's, emails, or telephoney eg skype.<br>
The overal structuring of this invitation follows the transition tree of Theory of Constraints, a process engineering tool; we may also want to use the process-management mechanisms followed by the developers, eg with version 0.2.7.1 replaced by 0.2.8, following open-source philosophy.<br>
+
The overal structuring of this invitation follows the transition tree of Theory of Constraints, a process engineering tool; we may also want to use the process-management mechanisms followed by the developers, eg with version 0.2.7.1 replaced by 0.2.8, patch-programming and trunk modifications, and following open-source philosophy.<br>
 
Alternative steps to arriving at the idealistic objective are presented as alternatives on this page below. Clicking on any item or heading opens up a page which allows further elaboration, more precise definition, and more practical eventualities.
 
Alternative steps to arriving at the idealistic objective are presented as alternatives on this page below. Clicking on any item or heading opens up a page which allows further elaboration, more precise definition, and more practical eventualities.
  

Revision as of 12:41, 18 February 2006

Tron International Competition: TRONICv1.2

idealistic objective

1,000,000 players in a year's time self-organising a tournament of Fortress to be held in one day, the winning team earning £16,000, with post-dated funding of server admin, programming-developers, and game-designers.

meta: contributor's guidelines

Since all pages on the wiki are editable, all contributions must be constructive and additive: alternative solutions are explored like the growing branches of a tree. Visitors are invited to contribute to to the expansion of any idea, comparing different branches of solutions. Arguments, contention, are conducted in forum, chatroom, or informally through PM's, emails, or telephoney eg skype.
The overal structuring of this invitation follows the transition tree of Theory of Constraints, a process engineering tool; we may also want to use the process-management mechanisms followed by the developers, eg with version 0.2.7.1 replaced by 0.2.8, patch-programming and trunk modifications, and following open-source philosophy.
Alternative steps to arriving at the idealistic objective are presented as alternatives on this page below. Clicking on any item or heading opens up a page which allows further elaboration, more precise definition, and more practical eventualities.

timeline

1 month: players self-organise competition with the system already in existence: THE SPOON.
3 months: 100 players competition, first test: THE LADEL.
6 months: 1,000 players competition, first incremental test: THE BOWL.
1 year: 1,000,000 players competition, entry fee £1: THE CUP.

There isn't much point in working out all the solutions for the final 1,000,000 player competition for obvious reasons. Players are encouraged to provide solutions for the next target with a sense of the final target to make their solutions future-proof. That is, instead of merely producing a solution which can only work for 100 players, it is built to be able to deal with 100 players now, with the potential for the system to be extendable up to the final target. That is, the development core is organic.

THE SPOON

Without changing any of the current settings, can a bunch of players organise themselves such that they have a great day. They must organise themselves into teams. They must decide on a day to play together. Teams must meet on an agreed server at an agreed time. The winning team wins the prestigious TRONIC SPOON.

This experience may produce the following learning outcomes:

  • it's fun
  • high level of play: appreciation of individual skill and teamplay.
  • highlight some of the technical difficulties with respect to PING and servers
  • highlight the social problems of time-differential globally, registering of team-names, determining winners and losers, length of matches.
  • bolster the confidence of players to organise themselves
  • enable players to invite developers to provide solutions to improve gameplay and ease of use for the next competition: the even more prestigious TRONIC LADEL.

extras

wordplay

The title TRONIC is a working title. Feel free to suggest alternatives.
The titles of the various competitions are also working titles.
We may be familiar with jargon such as rubber, grind, grid, etc, and we can take this a step further by encouraging players to share their own favourite terms or phrases, eg woot, pwned, hold the line.
You know the term slip-stream? The acceleration a lightcycle gains from its proximity to a light-trail works in a similar way; does grinding adequately convey this?

previous versions

The original idea (TRONICv1) was presented to Wolverine, Ghableska, and Mazuffer through Skype in order encourage immediate feedback. Initial responses included disbelief, practical considerations, and enthusiasm.
A week later, the same group met to discuss more details (TRONICv1.1). Responses included the formation of a network of developers, and the inherent importance of enabling uninterrupted playy. The group disbanded after serving its purpose, to initially receive the idea, and to open up the idea to the community in general.
This version (TRONICv1.2) has been permitted by Z-man, Tank Program, and Lucifer.