Topic: AOTK3: General Server rules  (Read 1576 times)

0 Members and 1 Guest are viewing this topic.

Offline FPF-DieHard

  • DDO Junkie
  • Captain
  • *
  • Posts: 9461
AOTK3: General Server rules
« on: May 02, 2007, 11:44:15 am »
This all should be commons sense by now, but I figure I'd post this now for review.   It'd all coppied from SGO7 and the previous servers.

General Rules


- If you are in a PvP and die, stay there in the battle till the match is over.

- If a mission causes all players to drop, then all those players must attempt to log back on and retry the mission at least once allowing the player with a slower connection to draft. If this player is known to cause drops or lags, this player must not be on the front lines drafting, being drafted and causing connection issues. It isnt fair to anyone else. They need to do missions elsewhere. Make sure your Firewall is OFF!

- If the server goes down and players are still in a mission, VC period ends, or the server concludes, it still counts. Once the server comes back up, the losing team at the request of the winning team is obliged to be drafted and disengage to properly reflect the DV change on the map if possible.

- During some missions, a player's name may not be indicated on their ship. If you suspect you are playing against a human, type a greeting in the chat.  All other human players are required to immediately respond with a text chat greeting and identify the ship they are in. Some missions drop hosts and clients. In suspected situations, a player has the right to ask if their opponent(s) is still present and that player(s) is required to immediately respond with a text chat greeting.

- If you disengage or are destroyed in a game and there are others still fighting, you may not leave the game until the match is finished.

Forfeiting Missions:

Do to unfinished game code we suffer from the following issues and I would like everyone to follow the following protocol otherwise, these issues may causes SERIOUS errors in the database and lead to CPU overload and eventual server burps:

- You are NEVER allowed to forfeit a mission under ANY circumstances on the map during a mission draft or a mandatory mission choice.

- If you are drafted you MUST accept the mission. You are NOT ALLOWED to logoff or FORFEIT. EVER.

- If your navigator is incompetant and has wandered into an enemy hex and you recieve a mandatory mission, you may logoff and relog on as long as you do not do this repeatedly. You are NOT ALLOWED to FORFEIT a mission.

- DO NOT park your ship anywhere near the front lines and go AFK. You will cause forfeits this way. Logoff the server till you come back as you may take up a player slot.

- Do not EVER ALT-F4 out of a bugged mission. In case of a buggy mission, the attacker must fly off the map and then ESC FORFEIT in battle to get it to close. Occasionally the defender may also need to exit the map and ESC Forfeit in battle. The attacker is defined by the side that is in a hex controlled by the enemy at the time of the draft. The defender is defined as the side that is in their own home space at the time of the draft.



Account Creation Guidelines:



- Chat channels don't work properly if you setup your character name to begin with a number or include spaces in your name or any non-letter or number symbol other than a dash - or underscore _
- Hexx/SAC will mess up his chat because of the / he added to his character name. Instead he should use: Hexx-SAC the Underscore or Dash symbol in place of the forward slash.
- Only non letter or numeric symbols are the dash - or the underscore. _ DO NOT put spaces in your name or start your name with anything other than a letter.
Who'd thunk that Star-castling was the root of all evil . . .


Offline KAT Chuut-Ritt

  • Vice Admiral
  • *
  • Posts: 26163
  • Gender: Male
Re: AOTK3: General Server rules
« Reply #1 on: May 02, 2007, 01:33:42 pm »
This all should be commons sense by now, but I figure I'd post this now for review.   It'd all coppied from SGO7 and the previous servers.

General Rules


- If you are in a PvP and die, stay there in the battle till the match is over.

- If a mission causes all players to drop, then all those players must attempt to log back on and retry the mission at least once allowing the player with a slower connection to draft. If this player is known to cause drops or lags, this player must not be on the front lines drafting, being drafted and causing connection issues. It isnt fair to anyone else. They need to do missions elsewhere. Make sure your Firewall is OFF!

- If the server goes down and players are still in a mission, VC period ends, or the server concludes, it still counts. Once the server comes back up, the losing team at the request of the winning team is obliged to be drafted and disengage to properly reflect the DV change on the map if possible.

- During some missions, a player's name may not be indicated on their ship. If you suspect you are playing against a human, type a greeting in the chat.  All other human players are required to immediately respond with a text chat greeting and identify the ship they are in. Some missions drop hosts and clients. In suspected situations, a player has the right to ask if their opponent(s) is still present and that player(s) is required to immediately respond with a text chat greeting.

- If you disengage or are destroyed in a game and there are others still fighting, you may not leave the game until the match is finished.

Forfeiting Missions:

Do to unfinished game code we suffer from the following issues and I would like everyone to follow the following protocol otherwise, these issues may causes SERIOUS errors in the database and lead to CPU overload and eventual server burps:

- You are NEVER allowed to forfeit a mission under ANY circumstances on the map during a mission draft or a mandatory mission choice.

- If you are drafted you MUST accept the mission. You are NOT ALLOWED to logoff or FORFEIT. EVER.

- If your navigator is incompetant and has wandered into an enemy hex and you recieve a mandatory mission, you may logoff and relog on as long as you do not do this repeatedly. You are NOT ALLOWED to FORFEIT a mission.

- DO NOT park your ship anywhere near the front lines and go AFK. You will cause forfeits this way. Logoff the server till you come back as you may take up a player slot.

- Do not EVER ALT-F4 out of a bugged mission. In case of a buggy mission, the attacker must fly off the map and then ESC FORFEIT in battle to get it to close. Occasionally the defender may also need to exit the map and ESC Forfeit in battle. The attacker is defined by the side that is in a hex controlled by the enemy at the time of the draft. The defender is defined as the side that is in their own home space at the time of the draft.



Account Creation Guidelines:



- Chat channels don't work properly if you setup your character name to begin with a number or include spaces in your name or any non-letter or number symbol other than a dash - or underscore _
- Hexx/SAC will mess up his chat because of the / he added to his character name. Instead he should use: Hexx-SAC the Underscore or Dash symbol in place of the forward slash.
- Only non letter or numeric symbols are the dash - or the underscore. _ DO NOT put spaces in your name or start your name with anything other than a letter.


Perfect.


Offline Julin Eurthyr

  • Veltrassi Ambassador at Large
  • Lt. Commander
  • *
  • Posts: 1057
  • Gender: Male
  • Back in Exile due to Win 7 - ISC RM/Strat Com.
Re: AOTK3: General Server rules
« Reply #2 on: May 03, 2007, 06:20:58 am »
Too short. :P

Can you add 6 pages of worthless drivel, asinine explanations, contradictory details and repetitive clarifications to bring the :rules: up to our usual extra long and confusing standards???

Otherwise, perfect... ;)

AKA: Koloth Kinshaya - Lord of the House Kinshaya in the Klingon Empire
S'Leth - Romulan Admiral
Some anonymous strongman in Prime Industries

Offline Dizzy

  • Captain
  • *
  • Posts: 6179
Re: AOTK3: General Server rules
« Reply #3 on: May 08, 2007, 06:12:21 am »
I think these are general rules. There are 6 pages of additional rules I'm sure. ;) Above rules are the same we've used on all past SG servers... Wait, did I say 6? I meant 26. ;)

EDIT: Oh, and since DH didnt highlight the important general rules, it's all important, but since it's so short, the general rules are the MOST important. So memorize the above.

Offline Electric Eye

  • Lt. Junior Grade
  • *
  • Posts: 484
Re: AOTK3: General Server rules
« Reply #4 on: May 12, 2007, 08:47:20 pm »
 During some missions, a player's name may not be indicated on their ship. If you suspect you are playing against a human, type a greeting in the chat.  All other human players are required to immediately respond with a text chat greeting and identify the ship they are in. Some missions drop hosts and clients. In suspected situations, a player has the right to ask if their opponent(s) is still present and that player(s) is required to immediately respond with a text chat greeting.


That takes a lot of fun out of it. I remember AOTK and some peeps were sniffing around a starbase I was hanging out with. It was funnier than Hades watching them wonder WTF was going on because the SB was firing pretty darn good compared to an AI controlled SB, hehehehehehe... I only responded and let them know what was going on when they were limping away off the map.  :rofl: