Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
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