From time to time situations arise that might call for a game to be backed out and rerun. These situations are:
Items (1) through (4) apply to all games, no matter the frequency. The global nature of the problem calls for some action at host. Item (5) does not apply to games that run daily, as the disruption to the game flow is too great. Item (5), in all other games, will cause the game to be STALLED until feedback of a democratic nature can be gathered.
Please note that in ALL cases, any TRN that was sent in after the Host ran the initial turn will NOT be accepted or used. The TRN must clearly have some internet timestamps that indicate it was mailed 3 HOURS before due date. And I mean CLEARLY, as the multiple time zone problems and servers not following timestamp standards can muddy the waters.
Note that item (2) refers to file corruption, not feature bugs. A feature bug does not prevent the creation of RST files. If the game can progress, then it is not file corruption. If a host version is available that can fix a problem then a standard vote to rerun can be initiated.
Under no circumstance beyond total file corruption will a game ever be rerun to a turn prior to the current turn. That is, if a game is to be rerun, only the most recent turn can be rerun... not the one before that. So if you hope to get a turn rerun, MAKE SURE it does not run again. Act quickly, or your cause is lost. And make sure it is mot a daily game.
It is possible that what some players consider normal, others may consider abuse. In general I'd like to see a site that is pleasant for all to play at. It is, after all, the game that brings us here. Although abuse is difficult to define, for the purpose of this policy, anything that the recipient finds abusive or offensive (i.e. material with sexual connotations, profanity, excessive/personal taunts, personal threats and slander) will be considered abuse. No one should feel afraid to open EMail that has been directed to them by Robo.
To this end, no matter what, please avoid flames and flame-bait. Please also avoid deliberate abuse of your fellow players. Such activity ruins the game for all players. If you truly wish to humble someone, then shoot their ships and planets... if you are not successful, then feel yourself humbled. Descending into abusive Email, messages, and any other such attempts to 'rattle' the enemy, is not acceptable.
There is a line between the race that a player is playing, and the player playing that race. It is expected that taunts might appear, but only in context, good taste, and limited duration. Nothing personal please.
If you find yourself the recipient of abuse, please follow these steps:
A word of warning: I don't care who started it! If in reviewing the abuse I find both parties guilty, they will both be warned. The one to continue gets banned. If both continue, they both get banned. So if someone else starts in on you... DO NOT RESPOND IN KIND.
Should you have a subscription outstanding and wish a refund, please supply us with your full name and address, email address, and former Robo codeword to verify that it is you, and a refund will be issue you minus a handling fee of $2.50. Should your refund be less than this amount no refund can be issue. All refunds will be in Canadian funds regardless of original submitted denomination.
Any player that causes Robo to violate any of IslandNet's policies will be immediately terminated, and banned from Robo. Putting Robo in harm's way is not acceptable, and will not be tolerated.
Submitting official Robo EMail (eg. containing TRNs, complaints, abuse, etc...)
with a false return address will result in termination and banning. This is mainly
targetted at those attempting to circumvent the TRN submission authorization code,
but will be applied to any related offense. This includes all misrepresentations
of identity with intent to harm.
It is sad to have to have such a policy... it's just a game!
There are various forms of cheating, and Robo does his best to block the ones he can.
Unrepentant cheaters might get BLACKLISTED. [an error occurred while processing this directive]