The difference between Tranquility and Entropy

Tranquility is the “live” server, the EVE game world where most of the action takes place. Entropy is the test server where players can experiment with new features and changes without risking loss or changes to their favorite characters on the live server.

Periodically, the latest data from Tranquility will be uploaded to the Entropy server. This process is called “mirroring” and allows players to use their existing characters from the Tranquility server rather than having to start new characters on Entropy. Data is not transferred from Entropy to Tranquility, so whatever is done on the test server will not affect characters in the “real” game world.

Why you should help

Playing on the Entropy test server is completely voluntary. Many subscribers enjoy having the opportunity to explore changes or features that are in development before they are introduced on the live server. This helps them to understand how things that will be implemented may affect their characters.

The EVE developers monitor the Patch Review forum and #eve-chaos channel on the Coldfront (irc.coldfront.net) IRC server for feedback regarding the latest build versions. The exchange of ideas between testers and the developers is invaluable to both as they work together to balance and improve the game experience for all of our players.

How to access the test server

The test server is open to everyone, but the information about the accounts and characters is only updated periodically from the live server. You may not be able to log onto Entropy if your EVE account was created after the last update. From the EVE log in screen, select the “Test” option to enter the test server. A message will be displayed to alert you whether or not the build you have of the EVE client is compatible with what is currently in use on the Entropy server.

Location of patches for the test server

•  http://www.eve-online.com/patches/testpatches.asp

You should make a copy of your EVE directory for use on Entropy, patching separately from your normal version. Test patches should not, and often cannot, be used on the live server. Installing a test patch into your regular EVE directory will result in an incompatible client version and you will not be able to connect to the Tranquility server.

Test server available?

There is no regularly scheduled time for Entropy to be running. It is patched and restarted as needed, but occasionally will experience extended downtimes for any number of reasons. CCP makes every effort to have it up and going as much as possible.

Getting a message saying that your version is incompatible

There may be days when several builds are released over a short period of time as issues are found and fixed after being discovered through testing. Many times, you can guess the number of the patch you need based on the patch numbers shown on the list as they increase in value by one. Enter the number directly into the browser using this format, inserting the correct codename and replacing the x’s with the build number: http://patch.eve-online.com/test/evepatch.codename.xxxx-xxxx.eve . For example, the patch for the Castor build from 1283 to 1284 would be http://patch.eve-online.com/test/evepatch.castor.1283-1284.exe .

Help for Entropy-related questions and problems

There is an in-game channel named EVE-Entropy where players on the test server exchange information. Testers are also invited to join the #eve-chaos channel on the Coldfront IRC server or to participate in discussions in the Patch Review forum on our boards. The petition system is unavailable on Entropy and Game Masters will not be able to address issues related to Entropy.

Patrons of #eve-chaos are asked not to use identifying tags, such as corporation tickers, though you will see some names in the user list that do include tags. These are EVE volunteers who can provide you with information or assistance when you are on the Entropy server. [BH] tags identify the special group of volunteer bughunters who are part of our volunteer program.

Role of bughunters

Bughunters are not game masters or EVE developers. They are members of the Interstellar Services Department, our volunteer program, who assist our programmers by testing game features and items on Entropy, filtering bug reports that are submitted and helping to establish a priority for fixes and changes that need to be made. Bughunters do not have special characters or abilities on Tranquility.

Becoming a bughunter

Although interested players can use the application on the website to apply for other branches of the volunteer program, acceptance into the bughunter group is by invitation only. Leads for the division observe and invite candidates based on participation in the #eve-chaos channels, on the forums and by the quality and quantity of the bug reports they have submitted. The best way to become a bug hunter is to help out frequently and express an interest to someone in the division.

Getting extra stuff to help in testing

There is a corporation available to all Entropy players called Fight Club Co (FCC). The offices are located in PF-346, Planet 1. Joining FCC will give you access to all of the items on the live server as well as any items that are being tested on Entropy before they are introduced on Tranquility.

Rules of the Fight Club Co (FCC)

The purpose of Fight Club Co. is to provide people with items for testing without the worries of losing something valuable they have worked to obtain. Entropy players are encouraged to use FCC inventory to test combat features, also, provided these two simple rules are observed:

•  Combat is by mutual consent only. Since the main purpose of the server is testing, attacking people who may be attempting to test something specific, trying to reproduce a bug or merely minding their own business, is not allowed.

•  There is no pod killing without mutual consent. Although Entropy is periodically updated with new character data from Tranquility, being pod killed may result in the inability for someone to continue testing effectively.

Consequences of braking the FCC rules

Should you encounter someone who is breaking the FCC rules, report it to a member of the BH squadron immediately. If none are available, make a post on the Patch Review forum. Do not try to exact avenge yourself. Please try to maintain a sense of propriety and remember that stirring things up on the forum only serves to escalate problems more often than not. Each case is investigated individually when a complaint is received. Repeat offenders may be temporarily or permanently banned from Entropy.

Joining the Fight Club

If you own shares in your current corporation, you will not be able to join FCC. To correct this, make a new corporation on Entropy, then resign from it. Those who need money may request it in #eve-Entropy in game (but generally most players will not give it to you).

Handling of bug reports

Frequently, a bug will require more than one report in order to be fixed due to the complexity of some issues. It isn’t always possible to pinpoint what is causing the problem with the information given in a single report. By including as many details as you can when filing a bug report, the time to investigate the issue will be reduced and a fix can be implemented more quickly.

Information required in a bug report

Always provide as much information as you can – give details, circumstances, locations and anything else that could possibly factor into the problem. Attached files can be especially helpful when sent in the following formats listed below:

Combining and compressing information: Please use Zip files to combine and compress a number of files that you may be submitting. Using a Zip file makes it much easier to guarantee that everyone can open the files easily and reduces the amount of time needed to upload the information. Please specify in the bug report text what the Zip file contains.

Images

Images can communicate an abnormality more efficiently than trying to communicate it through text. Use the “Printscreen” on your keyboard to capture images to your Eve/Capture/Screenshots directory, and then convert them to jpg format before submitting them. Drawing a red ring around specific areas, taking care not to obscure important parts of the image, may help clarify what you are reporting.

Crash Dumps

Typically, when EVE crashes, a crash dump file (.dmp) is created in the Eve/Logs directory. The format for file names of this nature is generally similar to this: #crash b11113 2003.07.20.00.07.24.dmp, where the first number corresponds to the version, then the date is YYYY.MM.DD format, followed by the time when the crash occurred. Before sending in these files, verify that the file size is greater than 0 KB. A file of 0 KB indicates a missing dll, which Microsoft provides as a download here. (This file is only installed on Win2K and Windows XP, apparently.)

EVE Log Server Files

The EVE log server is located in the EVE directory. It can be set up to monitor what happens on your client and/or the errors it encounters. These files may contain confidential information about your account, so be very careful to submit them only by an official bug report and do not share the files with others.

To activate the log server, start it before you start your EVE client. Go to the File menu and select “Create a new workspace.” Start your EVE client as usual. When you encounter a problem or abnormality, exit the EVE client, then save the workspace file the server log has created.

If you are running EVE in windowed mode and anticipate a lot of activity with the client before you are able to reproduce the issue you want the log server to record, you can use CTRL-DEL in the log server window to clear the current log. This will enable you to document only the portion of play you want to capture.

DXDiag System Information

To collect this information, go to the Start menu, then select “Run” and type “dxdiag” (without quotation marks) in the available field. When the program is done, select “Save All Information” to get the combined information on your system and drivers as a text file that you can attach to your reports. This can be especially helpful when dealing with issues that may be related to your sound or graphics cards.