Armahacktron
(→Features) |
|||
| (One intermediate revision by one user not shown) | |||
| Line 48: | Line 48: | ||
|authentification || several settings to control players joining a game || ePlayer.* || REPLACE FEATURE || none | |authentification || several settings to control players joining a game || ePlayer.* || REPLACE FEATURE || none | ||
|- | |- | ||
| − | |[[ | + | |[[ladderlog | ladderlog]] || Extra messages to send information to script via ladderlog file || ePlayer.cpp, eTeam.cpp, gGame.cpp, gWinzone.cpp || MERGE with ladderlog || styball first, then arma |
|- | |- | ||
| − | |[[ | + | |[[ladderlog#COMMAND | /cmd]] || send a COMMAND entry to the script || ePlayer.cpp || Stable. ACTION? || sty+ct |
|- | |- | ||
|chat log || Separate log file for chat to allow a view on the server action from a webpage || ePlayer.* || Experimental. ACTION? || sty+ct | |chat log || Separate log file for chat to allow a view on the server action from a webpage || ePlayer.* || Experimental. ACTION? || sty+ct | ||
|- | |- | ||
| − | |[[ | + | |[[ladderlog#PLAYER_GRIDPOS | positioning]] || Tactical positioning of cycles || gCycle.*, gGame.cpp || Experimental. || sty+ct |
|- | |- | ||
| − | |Experimental AI Control || The goal was to give some control over bots to be able to create single player games ||Files Affected?|| Experimental. | + | |Experimental AI Control || The goal was to give some control over bots to be able to create single player games ||Files Affected?|| Experimental. DELETED || none |
|- | |- | ||
| − | |[[Settings#SVG_output_settings | SVG output]] || generate and SVG image of the current game play. || ???|| | + | |[[Settings#SVG_output_settings | SVG output]] || generate and SVG image of the current game play. || ???|| DELETED || none |
|} | |} | ||
Latest revision as of 07:49, 29 May 2012
Contents |
Armahacktron
This place is dedicated to trying to document the hacks that have been done to Armagetron Advanced.
Groundpig started it all off with his hacks that included shooting, zombies, styball and capture the Flag.
We have built upon his work adding the ability to produce decent ladders, on the fly zone spawning, extra log files and many more.
This is the version of armagetron that runs Crazy Tronners Wild Fortress.
Source
Our current source code is on BZR (bzr >= 1.0)
bzr co http://bazaar.launchpad.net/~armagetronad-ct/armagetronad/0.2.8-armagetronad-sty+ct
To update the code move to the 0.2.8-armagetronad-sty+ct directory and use the following
bzr up
An older source code with sample tables and scripts can be Downloaded here
Settings
Extra settings that have been added
The ability to spawn/collape/move/resize zones, either via the console or script.
ladderlog
ladderlog.txt. was previously edlog.txt, but it was merged with ladderlog.txt. it gives a lot of extra information. To be read by a script to do all sorts of wonderful things.
Running a Server
So, what can I actually do with it?
Features
To merge features of Armahacktron back into the main armagetron repository (at LINK launchpad.net). CT_voodoo and [User:joda.bot] created this feature list. The list also contains actions to be taken for each feature. If we missed a feature or you think the feature should go to another branch. Please correct the information here.
the extra features are :
| feature | details | affected files | Action | Add to Branch |
| new zone interaction code | rewrite of bouncing to include time parameter in the bouncing algorythm + extra settings: ball_interacts, ball_kills, ball_team_mode | gWinzone.* | To be debug | sty+ct |
| target zone | Zone to give points to the first players to reach it | gWinzone.* | STABLE INTEGRATE | sty+ct |
| blast zone | A zone in which the player tail is erased | gWinzone.* | Experimental. To be debug. | sty+ct |
| spawn_zone, zone_radius, zone_position | Command to interact with zones from console/script | gwinzone.*, tString.* | Stable. | sty+ct |
| spawn_explosion | Command to spawn an explosion from console/script | gwinzone.* | Experimental. | sty+ct |
| respawn_player | Command to respawn a player from console/script | ePlayer.* or gCycle.* | Experimental. | sty+ct |
| add_score_team/player | Command to grant points to team/player from script | ePlayer.*, eTeam.* | Experimental. ACTION? | sty+ct |
| authentification | several settings to control players joining a game | ePlayer.* | REPLACE FEATURE | none |
| ladderlog | Extra messages to send information to script via ladderlog file | ePlayer.cpp, eTeam.cpp, gGame.cpp, gWinzone.cpp | MERGE with ladderlog | styball first, then arma |
| /cmd | send a COMMAND entry to the script | ePlayer.cpp | Stable. ACTION? | sty+ct |
| chat log | Separate log file for chat to allow a view on the server action from a webpage | ePlayer.* | Experimental. ACTION? | sty+ct |
| positioning | Tactical positioning of cycles | gCycle.*, gGame.cpp | Experimental. | sty+ct |
| Experimental AI Control | The goal was to give some control over bots to be able to create single player games | Files Affected? | Experimental. DELETED | none |
| SVG output | generate and SVG image of the current game play. | ??? | DELETED | none |
Goal: Add Links or short descriptions to each feature. Possible Target? branches are general feature/"bug fix" goes to arma, styball related to styball, all others to CT branch (which will probably be a styball subbranch).
Currently voodoo is working on gWinzone, while joda.bot is working on merging ePlayer and eTeam.
