Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
A: Technically, it's called "desync". Desync means that the player has lost their connection to the battle, but bits and pieces of their activity still reach the server and are applied to you or other players. In other words, this is not cheating, and it is caused by inconsistencies in Robocraft's networking aspect rather than by some means of hacking. This is expected to be fixed in future.
on robocraft form needs to be fixed you say its not cheating but technicly it is if its abused, an invisible invincible player taking down team and the core is unfair, so while the bug is not cheating staying in the match and abusing its atributes should be.
There is always a reason for ut
robocancer