Search the Community

Well, if you've played on our Pokemon Trade server, you may have seen the maps with the teleport that leads either to the left of your spawn or behind your spawn. Anyways, you may have missed them because the teleport was sapped, when it shouldn't have been able to. There are two sappers in the game right now - Default and the Red-Tape Recorder. One of which (default) cannot sap the teleport to destroy, only to disable until an engineer removes the sapper. The Red-Tape however works differently, it, with it's degrading ability, destroys the teleport leaving the team only one way to exit the spawn. This post/poll is merely for my concern on whether or not we as staff and members of the server should consider it a bug, or just push it aside. Counterargument for those who say "yeah frick you tatost this is fine." You'll say something around the lines of "but as long as it doesn't disrupt game play it's fine!" Actually, no, it isn't fine since the teleport since it obviously can't be sapped by the default sapper, and can by the other, it's a bug.

Playing JB this morning, I have realized that the JB server is getting worse with bugs and problems as time passes. As of right now: CT guns spawning in T cells (with CT's name on the gun, It's a issue with jb_lego_jail_v8) Some of these issues are minor, but they all add up. T's can't rebel because of their names showing when they kill a CT. And the fact that you can't even play a full game without a mapchange 5 rounds in. I'm glad that things are being added like !settings, but now it's time for serious bug fixing, otherwise more problems will probably pop up. @Bleed @Lithium @Snackbar EDIT: Some of the stuff I posted earlier was fixed. Removed from the list. Stuff that was addressed (Thx bbys): After 5 rounds, a mapchange occurs (not done by RTV)(Fixed). !call still doesnt work if no admins are on.(Might not be possible, RIP call BOT.) Shot4Shot is still broken. (should be fixed next map change) Tick rate is still 51.2 (Helps server load, maybe will change, who knows) When a T kills a CT, it no longer hides which T killed the CT.(Fixed by Bleed) Thanks @Bleed and @Lithium for fixing the problems quickly! :D