Author Topic: Fully non-respawnable (kicked by server during shooting range)  (Read 652 times)

0 Members and 1 Guest are viewing this topic.

Offline uehara

  • Busta
  • *
  • Posts: 2
  • Respect: +0/-0
  • Gender: Male
  • Buster
    • View Profile
  • MCNR name: uehara
I was at a shooting range and I got kicked for cheating because of multiple rapidfire warnings (I have no shame in admitting to this, I wasn't cheating, in fact, I was c-bugging. If you want to punish me for it, go ahead, but I wasn't using it on any player, so please be lenient if you do decide to punish me).

After I got kicked, I immediately relogged, and well, the video speaks for itself:


I tried getting teleported and whatnot but the helper/admin guy was saying you're not spawned or whatever.
This is a game-breaking bug and it's affecting my game, please, I really want to play on the server.

Offline uehara

  • Busta
  • *
  • Posts: 2
  • Respect: +0/-0
  • Gender: Male
  • Buster
    • View Profile
  • MCNR name: uehara
Re: Fully non-respawnable (kicked by server during shooting range)
« Reply #1 on: July 04, 2022, 06:14:27 pm »
resolved but the bug is still existent and coulod be game-breaking, as a future note, i was jailed by an admin and then unjailed which fixed the issue.

Offline SirenHead.

  • *
  • Posts: 350
  • Country: ir
  • Respect: +14/-24
  • Gender: Male
    • View Profile
Re: Fully non-respawnable (kicked by server during shooting range)
« Reply #2 on: July 04, 2022, 08:43:48 pm »
Hola @uehara
This is not a bug, the reason is your internet and the lagging you have.
It will be fixed with relog.

Offline Alex184

  • 𝐃𝐞𝐨 𝐅𝐢𝐝𝐞𝐥𝐢𝐬
  • *
  • Posts: 110
  • Country: us
  • Respect: +9/-7
  • Gender: Male
  • "Simplicity is the ultimate sophistication."
    • View Profile
  • MCNR name: Alex184
  • Discord name: Alex184#0530
Re: Fully non-respawnable (kicked by server during shooting range)
« Reply #3 on: August 02, 2022, 06:58:49 am »
Hola @uehara
This is not a bug, the reason is your internet and the lagging you have.
It will be fixed with relog.

Basically ^. The rapid fire issue is already being worked on.