Difference between revisions of "Autopilot in Coopetition"
From #openttdcoop wiki
m (added to research category) |
m |
||
| Line 28: | Line 28: | ||
</pre> | </pre> | ||
| − | == Handling of the | + | == Handling of the Game Time == |
As we play always until 1.1.1968 (this date can maybe change too if we have clearer rules) game should be paused at this day by the Autopilot. All players should be announcend if another year is over by our lovely Autopilot to be informed when the last year starts. | As we play always until 1.1.1968 (this date can maybe change too if we have clearer rules) game should be paused at this day by the Autopilot. All players should be announcend if another year is over by our lovely Autopilot to be informed when the last year starts. | ||
<pre> | <pre> | ||
Revision as of 17:47, 6 August 2006
by Osai
After our first successful Coopetition Game I thought about the usage of Brianettas Autopilot in Coopetition Games.
Note: Some of this ideas are already in preparation for a possible league/ladder system and we are far away from it. The first three ideas are important for Coopetition Games in general.
Autopilot should handle a lot of technical things I am going to list here:
Contents
Handling the Game Start
Autopilot should manage the game start, after starting the server both teams have time to get in contact with the map (the rules define the time). After this time Autopilot will start the game with an announcement.
5 minutes until the game starts. 1 minute until the game starts. 10 seconds until the game starts. 3 2 1 Game Started - Good luck and enjoy your ride!
Handling the Companies and Players
If the game is in progress, Autopilot should automatically pause the game when a player de-syncs or looses his connection. Actually OpenTTD can not restrict the company count to a special value. But Autopilot could check if there are more then two companies in the game and delete the third company. And of course Autopilot should manage the player count, any fifth player should be kicked out immediately!
Player 3 lost his connection. Game Paused. Game will continue in 3, 2, 1 second/s. Game continued.
Handling of the Game Time
As we play always until 1.1.1968 (this date can maybe change too if we have clearer rules) game should be paused at this day by the Autopilot. All players should be announcend if another year is over by our lovely Autopilot to be informed when the last year starts.
6 Years until game ends 2 Years until game ends This is the final year, from now on your train income counts The game is over - Congratulations to all Players
Auto-Savegame
If possible the game should be saved to a special folder where we can check all the data.
Game successfully saved.
Easy Administration via Webinterface
I am not sure if Autopilot is able to interact with a Database yet. But it would be awesome to be able to configure the Autopilot via an easy-to-use Interface before the game starts! Some other great possibilities came with this thing, but I wont talk about them!
The progress
| Idea | Player | Draft of idea | Testing | Completed | Remarks |
|---|---|---|---|---|---|
| Handling the Game Start | Osai | first version created | In progress | In progress | |
| Handling the Companies and Players | Osai | first version created | In progress | In progress | |
| Handling of the game time | Osai | first version created | In progress | In progress | |
| Auto-Savegame | Osai | first version created | In progress | In progress | |
| Easy Administration via Webinterface | Osai | first version created | In progress | In progress |
