Test Server Feedback

GENERAL RULES

• DO NOT interfere with CCP, volunteer or player testing.
• DO NOT harass the BugHunters, Devs, GMs or Volunteers.
• DO NOT ask CCP Devs, GMs or BHs for skills, ships or items. They will not be granted.
• DO NOT make mass purchases or create oversize stacks of items. This can affect server stability and performance.
• DO NOT mass refine large numbers of ships or items. This can affect server stability and performance.
• DO NOT mass-drop of items in space. This can affect server stability and performance.

• Combat is by consent only, except in the designated combat systems (6-CZ49, PVH8-0).
• Keep Local Communications in English. As with the forums, it is the common language for the testers.
• Selling items on the Test server for ISK on TQ is not allowed.
• No offensive language in public chat channels.
• The rules of conduct for the Tranquility server apply on the test servers.

COMBAT SYSTEM (6-CZ49, PVH8-0) SPECIFIC RULES

• No fighting or other aggressive actions within 500km of the station and gates (no targeted or AoE warp inhibiting modules).
• No capitals in PVH8-0

Consequences

• Severe breach of the rules will cause permabanning from the test server (including alt accounts).
• All other test server bans, unless otherwise stated, are until the next mirror.
• Other possible consequences are: Being moved to a different system, losing your ship, losing all your skills
• Harassing Devs, GMs, or BugHunters on the #eve-chaos channel in attempt to have a ban lifted will result in ban extensions.
• Any further posts cluttering this forum with ban discussions will be locked.

RULES CONCERNING SOV, STARBASES AND CONQUERABLE STATIONS

Sovereignty

• The first person to put up a TCU (Territorial Claim Unit) and start bringing it online in an unclaimed system (that has no sovereignty) is entitled to hold sovereignty in that system.


• Exceptions from the above rule: If the sovereignty claiming is done with malicious intent, i.e. to disrupt other players' testing, the right to sovereignty is void.


• If the sovereignty-claiming TCU should go offline, the player loses the right to claim sovereignty in that system after the system becomes unclaimed again.


• Anchoring or attempting to online a SBU (Sovereignty Blockade Unit) without consent from the sovereignty-holding entity is classed as griefing, disrupting of the test server and non-consensual combat.


• Claiming sovereignty in a system already claimed by another alliance is classed as griefing, disrupting of the test server and non-consensual combat.

Starbases and station services

Starbases and station services are included in the "No non-consensual combat" rule. This means that you are not allowed to attack a starbase, starbase modules or station services that belong to someone else without their express permission. This rule does not apply in the main combat systems.

Conquerable stations and outposts

If a player gains ownership of a conquerable station or outpost he/she must NOT restrict access to that station and the station services in any way.

BUG REPORTING:

Bug reports are totally unrelated to petitions, and filing a bug report for reimbursement or help will not work, as bug reports are never seen by the GM/support team. The only time a bugreport will be answered is if CCP needs feedback on a specific report.

You can file a support ticket to get help from a GM by using the help center.

Please read this page on how to make good bug reports:

https://community.eveonline.com/support/test-servers/bug-reporting/

You can also use the ingame Report Bug feature that you find under the help menu (F12).

Written by BH Strijd, the following is an example of a well written bug report, it should inspire and help you write a more rounded report and give you some confirmation of what to include in a bug report. Just supplement your report with the information provided here. The contents of this report contain information based on a previous well known bug. Following the outline of this report will help us process your report quicker.

Title:
Jump Clones: Character sheet does not show updated attributes/augmentations after clone jump

Category:
Game Mechanics

Server/Build:
Tranquility/70124

Description:
After a player clone jumps, the augmentations tab on the character sheet does not show any implants. The previous clones attributes still appear in the Attributes tab and is used to calculate skill time.

This is causing confusion when skills are set immediately after activating a jump clone.

Relogging the client cleans up this issue but it appears the skill training needs to be restarted to take new implants into account.

Reproduction Steps:
1. Record the data in the character sheet's Augmentation tab and Attributes tab.
2. Jumpclone to a clone which contains implants.
3. View the Augmentation tab, notice no implants are listed.
4. View the Attributes tab, notice the attributes are the same as before jumping (same numbers recorded in step 1).
5. Restart the client.
6. Notice attributes and implants now appear correctly.

Computer:
Intel Intel Core i7-980X
Realtek on-board sound
Nvidia GTX980
24GB RAM

Files Attached:
Screenshots - drawn on in paint or similar application to highlight the problem
Logserver Logs
DxDiag