Ikariam PH

Quoted

1. Bashing Report / Appeal
Title: [server name], Bashing to Report/Appeal, in-game ID

Server name:
Your account: in game ID
Report account: in game ID
Contents:
Screenshots: military adviser Screenshots with Bashing report details
» Your picture may not be larger than 256 KB.
» Furthermore the following formats are allowed: jpg, jpeg, gif, png, bmp » If your image doesn't match these requirements your response will be saved without it.

Notes in Bashing :
1. The definition of Bashing: It is not allowed to attack any given city owned by a player over 6 times in a single 24 hours period. For example: A has three cities, B can attack each of these THREE cities SIX times, if any city got attacked more than six times then it is Bashing. Sea Battle is not taken into account. We are using the number of Combat reports with LOOTS - Successful attacks in determining how many times each city has been attacked. Attacking troops that are completely destroyed- Failed attacks do not count. Reinforcements will also be counted as 1 attack. Fore more information, please check the Bashing FAQ .
2. Be sure to provide a clear picture, (military advisers results) or it will not be entertained.

Quoted

2. Multi accounts Report/Appeal

Title: [server name], multiple accounts appeals / Report , the appeal / report account's name (if you want to report several accounts you can write as "multi-accounts")

Server name:
Your account: in game ID
To appeal / complain account: in game ID
Ban reason and GO who banned you:
Report / Appeal:

Notes in Reporting/ Appealing for Multiple accounts :
1. If you would like to Appeal, the reason why you got banned and the GO who handled your case can be found in-game.
You can do this by clicking Highscore -> Pillory
Copy and paste them to ban reason column.
2. Any chat tool's dialogue record, assumption, forum discussion, or forum message can not be used as evidence.
3. If GO decides to release your account, it will still be in vacation mode for a period of time. Please wait.

Quoted

3. Notification for Same IP

Title: [server name], Notification for same IP, account names

Server name:
IP address that you want to Inform GO :
Game accounts Using this IP:
When these accounts use this IP:

Please make the information above as a list for the GOs to check

Notes in Same IP Notification :
1. Notification for same IP only helps in avoiding potential misunderstanding with the GOs, but does not excuse your account/s in the banning process.
2. If GOs find out that you have other violations, your account will be banned. Notification won't help you.
3. If GOs find out you actually are a multi-account user, you will also will be banned. Notification doesn't work.
4. Players should use the Email address they registered in Ikariam.ph game in notifying GOs.
5. GOs will instruct you about your limitations (The no fleet contact rule) after notification.

Quoted

4. Account exchange

Title: [server name], account exchange A account <-> B account

Server name:
account A, score:
account B, score:
date when Account exchange will happen :
Other :

Notes in the exchange of accounts:
1. Account Exchange without a notification from a GO will result to the banning of the 2 accounts concerned.
2. You'll need to wait for the GO's response and confirmation before you use the traded accounts. Logging in before the GO's notification will lead to a ban (multi-accounting).
3. For players who already have an account in this world and wants to abandon his/her original account after Account Exchange, please state it in the "Other" column.
GO will perma ban his/her original account after Account Exchange is finished.
4. Player should use the Email address they registered for Ikariam.ph game in requesting or the GOs will not entertain it.
5. Exchange of account will include exchange of your account number, password, email and so on. After Exchange, you can now log in to your new account by using their original ID and password.

Quoted

5. Reporting Stolen accounts

Title: [server name], account stolen , account name

Server Name:
Account Name:
Stolen Time: (must be specific on that date)
Original account registered mail:
Account registration date:
The city where you live (in real life):
Screenshots of your original cities: (full-screen shots of the game)
Screenshot of your original game settings: (full-screen shots of the game)
Screenshots of your original islands: (full-screen shots of the game)
Used IP: (possible)
Player who can prove that the account is Yours: (he should use his registered email address in submitting a ticket to a GO, specify the title: [server name] witness! ,witnessID, stolen ID)
Your account has been operated by which GO: (for example, has been banned, the reported data...)
Your account's permanent Email:
Other:

Notes in reporting stolen accounts :
1. Account stealing is a very serious incident, so our investigation process is also extremely prudential. Players must back up their accounts' original data from time to time. Fill up report template seriously.
2. If you provide more specific information to the GO, the chance of getting your account back will definitely increase.
3. In case some information in this template are missing, please leave those blank.
4. If you provide incorrect account information, you may no longer get your account back.
5. If you have any updates in your report, please inform the GOs immediately.

Quoted

SUBJECT TITLE: (should contain gist of problem) ex: Nawala units ko after pillage
description of problem (short summary) ex: Nawawala yung 200 phallanx ko nung magsikalat sila matapos akong matalo. 2 araw na yun.

- Bug date: time when bug happened, ikariam time found on the upper right corner of game window ex: 28.11.2009 10:16:03
- Gameversion: version of game, ex: ver 0.3.2
- Browser and Version: browser name and version number ex: Firefox 3.5.2
- Extensions: scripts/add-ons that are used in the game ex: greasemonkey with ikariam solaris ver 1.2

- Server and Nation: country and world, ex: ph1 (alpha) ~ ph4 (delta)
- Nickname: ingame-nickname
- Account ID from Options:
- Premiumfeatures: none
- Last action before the bug appeared:

- Bugdescription:
whole explanation of bug

- Screenshots: