OFFICIAL NEWS


RYZOM CODE OF CONDUCT (2018-11)

III. Game Integrity Infringement

III.1. Servers data hacked, decrypted or assimilated (Critical Offence)

Changing the client or its means of communicating with the server in order to obtain an advantage is strictly prohibited and is punishable by a permanent ban.


III.2. Account Piracy (Critical Offence)

The taking over by a player of a Ryzom account that does not belong to him/her, regardless of the computer means used, is strictly forbidden and is subject to a definitive ban, except if it is done with the explicit agreement of its owner (for example to solve a technical problem via screen sharing) or if the owner has shared his login and password with this person (see I.6.).

III.3. Utilization of a bot (Major Offence)

Using a third-party program to play through scripted actions.

Using macros which are not part of Ryzom's integrated macro system in order to make your character partly or completely independent of your direct control is strictly prohibited.

Control of several characters by the use of a third-party program is strictly prohibited. If, during a check, the Support Team is not able to discern whether a player is abusing this rule, the player will have to provide the proof that he's not using any third-party software to control several characters at the same time.

III.4. Multi-boxing

4.1- General rule for multi-boxing 

Multiboxing (playing several characters at the same time, without the help of third-party software) is limited to two accounts connected simultaneously during outpost battles, bosses hunts, marauder boss attacks and Storyline scripted events (see III.4.2) and tolerated up to four accounts for other activities.

When a player plays several characters simultaneously (multi-boxing), there should be no doubt for an observer that they are controlled manually one after the other and not by a bot. In case of doubt, the observer is invited to send to the Support a video showing the characters acting in an apparently synchronized way. The Support will then decide if this constitutes a breach of this Code of Conduct and, if so, is the work of a possible bot (see III.3) or if it is a breach of this paragraph. In the latter case, the accounts concerned will be subject to a simultaneous connection restriction (inability to connect two or more accounts simultaneously).

4.2- Multi-boxing during fights on outpost, bosses and marauder bosses or on a scripted event of the Storyline

(Major Offence)
Multi-boxing is limited to two accounts connected simultaneously during outpost battles, bosses hunts, marauder boss attacks and Storyline scripted events. If you suspect abuse, please send a screenshot or video showing the violation to Support.

4.3- Multi-boxing for more than 4 characters

(Major Offence)
The number of accounts connected at the same time is limited to four. 
However, Customer Support may make exceptions in individual cases (such as a large family, public computer etc). If you believe you should be exempted, please contact Support at support@ryzom.com, mentioning the reason for your request along with the names of all the accounts concerned.

III.5. Exploit (Critical, Major or Minor Offence, depending upon the case)

The concept of exploit covers any use of a third-party program, a client modification or recompilation or a bug to gain an advantage over the other players.

Exploits are forbidden and punishable by the Customer Support Team, which has the right to decide the severity of the noticed exploit. On this subject, repeated offences are an aggravating factor.
If you suspect the use of an exploit, you must contact us using one of the means mentioned above.

Discovering a security breach or an exploitable bug does not constitute a breach of the Code of Conduct provided that it is immediately reported by email to the Support (support@ryzom.com) and is therefore not liable to be sanctioned, as long as the use of such is stopped after discovery.


III.6. Aggro dragging outside of outpost battles (Minor Offence)

Intentionally dragging one or several mobs towards another player in order to kill or harass them is prohibited. If a player sees or is informed that he has unintentionally committed aggro dragging, he must apologize and do his best to resurrect the concerned characters, if required.

If you are victim of intentional aggro dragging and can prove it (for instance a screenshot of a tell showing that, when being contacted by you, the person dragging didn't show any sign of remorse and didn't want to come back and revive you), you can contact Support Team through one of ways mentioned above. We will then open a file and act accordingly. Here again, repeated offences will be taken into consideration.
Only aggro dragging during an outpost battle is tolerated (see III.9. Disrespect of the PvP rules).


III.7. Kill stealing (Minor Offence)

Killing a mob which is already being attacked by another player or group of players, is considered as kill stealing and is prohibited.

If, after trying to resolve the situation between the parties involved, no solution is found, you may contact Support Team through the means mentioned above. However, before contacting any CSR, first try to communicate with the player(s) involved and resolve it yourself!

In the case of a Boss, a Named mob or a Marauder Boss, please refer to the following paragraph.


III.8. Rules regarding Bosses, Marauder Bosses and Named mobs(Minor Offence)

a) Theft of Bosses, Marauder Bosses or Named 

A Boss, Marauder boss or Named belongs to the first team that has locked it, as long as the lock is active. (See https://app.ryzom.com/app_forum/index.php?page=topic/view/27212 for more information.)
A second team may assume the Boss, Marauder boss or Named only if it is not yet locked or it is unlocked. To do this, it can exclusively:
  • Fight the first team in PvP;
  • Take advantage of the departure of the first team, which automatically unlocks the Boss or Named. Note that if there is only one player left alive or present from the team that has locked the Boss, Marauder boss or Named, it will be unlocked.
Aggro dragging aimed at weakening the other team is prohibited and is therefore punishable (see III.6).

A Boss, Marauder boss or Named is considered free as long as it is not locked by any team.
The pull of Boss, Marauder boss or of Named by a single person, that is to say without team, is possible but insufficient to cause the locking. To re-acquire the Boss or Named in this case is not considered to be kill stealing.

b) Camping of Boss or Named spots

Camping of Boss or Named mobs’ spots is not regulated because it is often impossible to prove.


III.9. Disrespect of the PvP rules (Minor Offence)

In Ryzom, PvP is at all times consensual. Activating your PvP tag, entering a PvP zone or engaging in an outpost battle implies that you accept the consequences. To put it simply, if you do not want to take part in PvP action, then it is your responsibility to not activate your tag or not go into PvP zones.

a) Faction PvP

A player who activates his PvP tag accepts the consequences, whatever the circumstances.
E.g.: being killed while foraging, at the stables, while afk, at a respawn point near a vortex.

If, despite your tag, you wish to avoid the fight, you can wait for detagging to occur, hide, use a TP, change place or region, etc.

b) Zone PvP

The player who enters a PvP zone accepts the consequences, whatever the circumstances. However, as a specific exception, killings at respawn points near vortices are prohibited and punishable if proven. If you are tagged for Zone PvP and you are the victim of a kill at a vortex respawn, you can contact us through one of the ways described above. In this case, it is strongly recommended that you add a screenshot to support your claim (please ensure that the SYSTEM INFO window is visible in the shot).

c) Outpost battle PvP

The player who enters an Outpost battle area and chooses a side, accepts the consequences, whatever the circumstances.
However, as a specific exception, kills at respawn points near a vortex are prohibited and punished if proven. If you are under OP battle tag and you are the victim of a kill at a vortex or respawn, you can contact us through one of the ways described above. In this case, it is strongly recommended that you include a screenshot to support your claim.
Untagged characters in the OP must be removed during the battle as they distort the targeting of the protagonists. CSRs can move them if required.
If, despite your tag, you wish to avoid the fight, you can wait for detagging to occur, hide, use a TP, change place or region, etc.

Rules regarding outposts (OP)

a) CSRs will, as a general rule, not be present at outpost battles. However, if you notice a violation of the rules of decency and behaviour, you can immediately contact the Support team.

b) If you have become stuck in the landscape in a region where an outpost battle is taking place, first try to teleport. If you don't succeed, you must contact Customer Support, describing your situation. A CSR will then help to free you.

c) Everything that falls under the normal mechanics of the game is allowed in combat zones, provided that all those involved are tagged for PvP.
1 - A Mektoub packer might die. By bringing it into a combat zone, you are exposing it to risks.
2 - Spawn camping is almost impossible because of the security zone around the respawn points, and is thus allowed. If you die and your enemies are near your respawn point, you will have either to wait for regeneration in the safe zone or to choose another respawn point/Teleportation pact to rejoin the battle.
3 - During outpost battles, using aggro dragging and killing Yelks near the fight is valid and allowed game strategy.

d) Outpost Blocking
Declaring war on your own OP or that of one of your allies, or having your allies declare war on your OP(s) in order to prevent someone else declaring war on it, is considered an exploit and is prohibited.
The transferring of ownership of an OP from one guild to another is allowed. Raising the threshold is then forbidden, as is the handing over of the OP multiple times in a row, this being considered as blocking the OP.

e) Repetition of false declarations of war

Repeated false declarations of war, i.e., not followed by a real attack of the guild or its allies or with too few combatants to be able to raise the threshold against the NPCs alone, are considered harassment.

If you think your guild could be charged with this offence, take a screenshot showing all the players present on the outpost during the attack to show it to the support team if necessary.

Please note that this rule does not apply to counter-attacks (attacks launched to counter an outpost attack).
Show topic
Last visit Fri Dec 4 15:08:38 2020 UTC
P_:

powered by ryzom-api