0.2.8-armagetronad-sty+pvp
0.2.8-armagetronad-sty+pvp
Hi everyone...
I started a new personal project today. It's called 0.2.8-armagetronad-sty+pvp and it will strive to create an easy way for server administrators to create a server that will allow player versus player sessions and wars very easily. There will be new settings/commands for administrators to use: START_PVP <playername1> <playername2> and START_WAR <teamname1> <teamname2>
https://code.launchpad.net/~smoothice/a ... ad-sty+pvp
What do you guys think?
I started a new personal project today. It's called 0.2.8-armagetronad-sty+pvp and it will strive to create an easy way for server administrators to create a server that will allow player versus player sessions and wars very easily. There will be new settings/commands for administrators to use: START_PVP <playername1> <playername2> and START_WAR <teamname1> <teamname2>
https://code.launchpad.net/~smoothice/a ... ad-sty+pvp
What do you guys think?
Last edited by smoothice on Sat Jan 31, 2009 4:25 pm, edited 1 time in total.
-
- Average Program
- Posts: 61
- Joined: Fri Jul 25, 2008 11:24 am
An interesting idea
Some rambling thoughts:-
* Avoid clan terminology . From my point of view, using MATCH_START <<team name>>, MATCH_START_PVP, is clearer. Also means you can store your variables in the same place: MATCH_FIRST_TO_WIN etc.
* I can understand why you want to specify the team names, why do you need to specify the player names for pvp?
* Maybe check the Team variables to see how many teams are expected, for sumo compatibility.
* Multiple match support, eg. FIRST_TO_WIN.
* Look up eLadderLogWriter? from CT branch, add current match scores to it,
* Improving the output of the score files is a small bonus too ^^. var/players.txt var/scorelog, I think the names are.
All the best with it!
Some rambling thoughts:-
* Avoid clan terminology . From my point of view, using MATCH_START <<team name>>, MATCH_START_PVP, is clearer. Also means you can store your variables in the same place: MATCH_FIRST_TO_WIN etc.
* I can understand why you want to specify the team names, why do you need to specify the player names for pvp?
* Maybe check the Team variables to see how many teams are expected, for sumo compatibility.
* Multiple match support, eg. FIRST_TO_WIN.
* Look up eLadderLogWriter? from CT branch, add current match scores to it,
* Improving the output of the score files is a small bonus too ^^. var/players.txt var/scorelog, I think the names are.
All the best with it!
yes, a good idea.Pink Tomatoes wrote:An interesting idea
* I can understand why you want to specify the team names, why do you need to specify the player names for pvp?
specifying the player names could be to tell the server which players are in the fight, so others can come to the server to watch, and wait to play.
an idea about the team names.
have the command for naming the team
and one that auto selects the teams depending on tags in their name
commands for this could be TEAM_NAME <team number> <name>
TEAM_TAG <team number> <common tag of team>
so if you have a server with 2 clans ready for a war,
you would specify a 'common tag' for each team/clan playing.
then have the server look at names,
players that have neither tag are put into spectator mode.
players that have 'tag1' in their name get put into 'team1',
players that have 'tag2' in their name get put into 'team2', etc.
if it doesn't include someone on the team(maybe they have a different tag), the normal commands to +/- players from teams could be used.
this could save a bunch of effort on admins assigning players to teams.
although, that effort others are saved, you would have to put in yourself to get it working
Oooh, I like the idea of FIRST_TO_WIN. Some of these features I can definitely add but may take a while.Pink Tomatoes wrote:An interesting idea
Some rambling thoughts:-
* Avoid clan terminology . From my point of view, using MATCH_START <<team name>>, MATCH_START_PVP, is clearer. Also means you can store your variables in the same place: MATCH_FIRST_TO_WIN etc.
* I can understand why you want to specify the team names, why do you need to specify the player names for pvp?
* Maybe check the Team variables to see how many teams are expected, for sumo compatibility.
* Multiple match support, eg. FIRST_TO_WIN.
* Look up eLadderLogWriter? from CT branch, add current match scores to it,
* Improving the output of the score files is a small bonus too ^^. var/players.txt var/scorelog, I think the names are.
All the best with it!
-
- Average Program
- Posts: 61
- Joined: Fri Jul 25, 2008 11:24 am
Only because we have always had enough administrators to do the counting for us . Getting computers to do human work has always been the main goal . You can't argue with a computer either. Would make it much neater too, score display has always been done in a hurry.DDMJ wrote:that seems semi-pointless but whatever
No idea how you would display it, CONSOLE_MESSAGE every round maybe. Adding to where it should be on the scoreboard would be client dependent?