Lai Yonghao (http://laiyonghao.com)
Yesterday, I saw this message through Google Reader at the venue of the 3rd technology salon in Guangzhou (http://developers.solidot.org/article.pl? SID = 09/11/14/0641223 & amp; from = RSS), a burst of excitement. When I came back, I took a look at the relevant documents. I thought it was quite interesting and I just translated it. If any, please correct me.
Competition rules
- No registration fee required
- No bonus
- All videos of the open competition after the competition
- Starcraft Brood War 1.16.1 is used in all competitions
- Starcraft is a registered trademark of Blizzard Entertainment.
- Legitimate copies of Starcraft and extensions required by participants
- We will confirm that the StarCraft owned by contestants is legal and require participants to log on to battle.net as part of the registration process.
- Blizzard does not assume any responsibility
- We do not assume any responsibility
- This includes the issue where your CD Key is blocked by battle.net due to running a third-party Starcraft runner.
- Entries must use the Brood War API provided by this website.
- Robot execution of malicious behaviors will be canceled and prohibited from participating in the next competition. The so-called malicious behaviors include but are not limited:
- Deliberately caused Starcraft to crash
- Install worms/viruses/malware
- Malicious exploitation of resources, such as sockets, files, and zombie processes (100% of Ram and 100% of CPU are allowed)
- Spread "junk" (interference information, etc.) on the game console)
- Attempts to cheat will be disqualified
- Robots need to disable the perfect information mark in 1, 2, and 4 games.
- In the competition, the StarCraft crash is negative
- There will be a series of tests several weeks before the start of the competition to ensure that the contestant program runs correctly on the competition Machine
- The robot will run in a Windows XP/Vista Environment
- The entries should be submitted after the Windows XP/Vista test is installed.
- We will not be held responsible for the StarCraft crash caused by program participation due to our system configuration
- The competition is semi-automated. For more information, see the competition configuration page.
- Robots will run in a LAN and cannot access the Internet
- A single place can only be submitted for one competition program, but different robots can be submitted for each sub-member than cold.
- Robots cannot slow down the game
- The fastest setting will be used for the competition, with 24 frames per second
- Here are the details about how to compile the Remote Process of AI.
- During the game, robots slow down the game for a long time.
- Participants do not need to disclose source code
- Provide a DLL. For more information, see the submit page.
- However, the contestant must provide a brief description of the execution details.
- Open-source or closed-source components are allowed for entries
- Works can be used to communicate with remote processes.
- The remote process must click to run the application (for example, we will not install a Lisp compiler on the host to run a robot)
- Compile other details of the remote process.
- Entries can be written to a local directory.
- Allow robots to save the status of both sides in a round of competition
- However, these files will be cleared after each round.
- The robot cannot pause the game. If the robot suspends the game, the game will be negative.
- The following Starcraft errors/tips are acceptable:
- Plague on interceptor
- Units pressed through
- Drops to defuse mines
- Mineral walk
- Manner Pylon
- Lurker hold position
- Observer over turret
- Stacking air units
- However, all of the following errors/vulnerabilities are forbidden. Robots exploiting these vulnerabilities will be disqualified from the competition. This includes but is not limited:
- Flying drones and Templars
- Terran sliding buildings
- Stacking ground units
- Allied mines
- Gas walk, to get through blocked entrances or ramps
- Do not encourage bad behaviors in other competitions, but do not prohibit
The above rules are formulated according to the orts 2009 rules.