Maintenance for the week of December 23:
· [COMPLETE] NA megaservers for maintenance – December 23, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
· [COMPLETE] EU megaservers for maintenance – December 23, 9:00 UTC (4:00AM EST) - 14:00 UTC (9:00AM EST)
· [COMPLETE] NA megaservers for maintenance – December 23, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
· [COMPLETE] EU megaservers for maintenance – December 23, 9:00 UTC (4:00AM EST) - 14:00 UTC (9:00AM EST)
gotta love the cheaters man
yourhpgod
✭✭✭
there this new cheat where you can't bar swap or move even though you're not knocked down, stunned, or any kind of immobility status
https://tiktok.com/@yourhpgod/video/7412553639924944159?is_from_webapp=1&sender_device=pc&web_id=7405052762109806122
"Health tanking in Cyrodiil isn’t about glory—it’s about stepping up when no one else will. Someone has to stand their ground, and if it's going to be anyone, it might as well be me."
"Health tanking in Cyrodiil isn’t about glory—it’s about stepping up when no one else will. Someone has to stand their ground, and if it's going to be anyone, it might as well be me."
2
-
CameraBeardThePirate✭✭✭✭✭
✭✭✭✭✭Dude you need to stop spamming the forums claiming that every technical issue or bug you come across is cheating.
No, there are no cheats preventing you from bar swapping. You're likely just lagging.Edited by CameraBeardThePirate on 26 September 2024 01:2625 -
yourhpgod✭✭✭its not spam its making conversation.
I do feel bar swap nightcapped
https://tiktok.com/@yourhpgod/video/7412553639924944159?is_from_webapp=1&sender_device=pc&web_id=7405052762109806122
"Health tanking in Cyrodiil isn’t about glory—it’s about stepping up when no one else will. Someone has to stand their ground, and if it's going to be anyone, it might as well be me."0 -
Theist_VII✭✭✭✭✭
✭There is a bug going around in Battlegrounds where when you die you can respawn without the ability to barswap.
The only fix to this happening is to die again, which is quite easy when you’re stuck on your front-bar.
Perhaps this problem happened to the OP.5
