1. Workshop maps failing to update
Dedicated server can return an Item State 4 that the map is up-to-date which is incorrect. This forces you to delete custom map from both locations it's installed and delete all its traces from the appworkshop file in order to get an updated version. Launching the server with Steam closed can help a few times but not always. Eventually your server will stop updating all Workshop maps entirely. I was told this was a Steam issue but I still haven't seen any fixes for it yet.
2. Server failing to show important Warnings
The server can fail to return Workshop ID warnings that are crucial to the Admin. For example, when a Workshop page is private or taken down, this what the server should get.
However, it does not, and instead returns an Item State 4 like everything is fine and dandy. The only way to get this warning to appear is by deleting all your workshop map data for your server and starting fresh, but it will stop working again very quickly
3. Prevent initiating kick votes on an Admin
Right now, Admins cannot be kicked which is good but not good enough. Players can still initiate a kick vote on an Admin. This should not be possible at all. It should return an error such as "This player cannot be kicked."
4. Web Admin Chat Problems
When you use Web Admin to send a message to the players in-game, your name will show up as a SPECTATOR which is false. On top of that, there's an extra set of SPECTATOR tags and more which looks absolutely ridiculous. I believe this became an issue back when VS mode was added. Here's an image:
On top of that issue, players using chat wheel commands like AFFIRMATIVE do not show up in Web Admin chat. They may be replying to the Admin because they believe they're spectating the game.
5. Chat Logging doesn't log Team Chat
A minor issue but still an issue. I've had players harassing others using team chat. Whether it was a mistake or intentional, it didn't show in my chat logs.
6. Admin can't see player who initiates kick votes
Even if you're logged in in-game as Admin or check your server logs, you'll never know who started the kick vote. It's quite humorous the server logs dosh tossed from players and logs players trying to change perks mid-game but it won't log a kick vote. Very funny.
7. Admin can't close active kick votes
As an Admin, you'll have to make a Yes or No vote and cannot close an active vote you may disagree with.
8. Disabling Spectators problem
You can disable spectators by setting the value to 0, but when players connect it doesn't tell them spectators are disabled. It says the server is full. Not a big issue though. The main problem I have with disabling spectators is that Admins are also excluded from spectating.
9. Admin Pause is confusing players
There needs to be a GAME PAUSED BY ADMIN message in the center of the screen. Right now, players literally think their game is frozen unless an Admin warns them ahead of time that game will be paused.
10. Admin automatically signed out every new game
You'll have to type in adminlogin password every game or bind it to a key if you want to stay signed in as Admin.
11. Web Admin crashes server at 519 custom maps (issue was addressed)
I'm not concerned with this issue anymore since TWI briefly addressed it in the past and I'm probably the only player in the game that deals with it. But it is still a problem.. Luckily I've come up with my own workaround.
That's all I got for now.
zachjd
Dedicated server can return an Item State 4 that the map is up-to-date which is incorrect. This forces you to delete custom map from both locations it's installed and delete all its traces from the appworkshop file in order to get an updated version. Launching the server with Steam closed can help a few times but not always. Eventually your server will stop updating all Workshop maps entirely. I was told this was a Steam issue but I still haven't seen any fixes for it yet.
2. Server failing to show important Warnings
The server can fail to return Workshop ID warnings that are crucial to the Admin. For example, when a Workshop page is private or taken down, this what the server should get.
However, it does not, and instead returns an Item State 4 like everything is fine and dandy. The only way to get this warning to appear is by deleting all your workshop map data for your server and starting fresh, but it will stop working again very quickly
3. Prevent initiating kick votes on an Admin
Right now, Admins cannot be kicked which is good but not good enough. Players can still initiate a kick vote on an Admin. This should not be possible at all. It should return an error such as "This player cannot be kicked."
4. Web Admin Chat Problems
When you use Web Admin to send a message to the players in-game, your name will show up as a SPECTATOR which is false. On top of that, there's an extra set of SPECTATOR tags and more which looks absolutely ridiculous. I believe this became an issue back when VS mode was added. Here's an image:
On top of that issue, players using chat wheel commands like AFFIRMATIVE do not show up in Web Admin chat. They may be replying to the Admin because they believe they're spectating the game.
5. Chat Logging doesn't log Team Chat
A minor issue but still an issue. I've had players harassing others using team chat. Whether it was a mistake or intentional, it didn't show in my chat logs.
6. Admin can't see player who initiates kick votes
Even if you're logged in in-game as Admin or check your server logs, you'll never know who started the kick vote. It's quite humorous the server logs dosh tossed from players and logs players trying to change perks mid-game but it won't log a kick vote. Very funny.
7. Admin can't close active kick votes
As an Admin, you'll have to make a Yes or No vote and cannot close an active vote you may disagree with.
8. Disabling Spectators problem
You can disable spectators by setting the value to 0, but when players connect it doesn't tell them spectators are disabled. It says the server is full. Not a big issue though. The main problem I have with disabling spectators is that Admins are also excluded from spectating.
9. Admin Pause is confusing players
There needs to be a GAME PAUSED BY ADMIN message in the center of the screen. Right now, players literally think their game is frozen unless an Admin warns them ahead of time that game will be paused.
10. Admin automatically signed out every new game
You'll have to type in adminlogin password every game or bind it to a key if you want to stay signed in as Admin.
11. Web Admin crashes server at 519 custom maps (issue was addressed)
I'm not concerned with this issue anymore since TWI briefly addressed it in the past and I'm probably the only player in the game that deals with it. But it is still a problem.. Luckily I've come up with my own workaround.
That's all I got for now.
zachjd
Last edited: