Option to ban player until determined time. Like 08.08.2023 | 14:00 or Next Restart. If I want to ban player untill next restart (character wipe, database changes etc.) , I have to count hours and most of the time it wont match (20min short etc.)
#Ban untill option
tough epoch
wicked gate
Option to ban player until determined time. Like **08.08.2023 | 14:00** or **Nex...
Noted.
tough epoch
Keep up the good work! 
wicked gate
Thanks
idle tiger
It feels like many servers are programmed poorly, and corrupting txAdmin in the process.. this (as some other features) won't "work" in my server, as I don't have to restart the WHOLE server, just to do certain things like you mentioned... I just restart the resource that is responsible to the system I made changes and it works fine.
But still, if this feature would usable for me, I'd use it, but again, I don't restart the whole server, just the resource, so it won't unban the player...
desert jay
how are servers with scheduled restarts poorly programmed?
idle tiger
Because scheduled restarts is to restart the whole server, and here in this thread they use it just to fix one small thing. If you need to kick all the players and restart the whole server just to fix one small issue, it is poorly programmed, as the whole idea behind resources is to be able to restart just one resource seamlessly.
delicate nacelleBOT
Because scheduled restarts is to restart the whole server, and here in this thre...
:rocket: Congratulations @idle tiger, you leveled up to <@&828359841512816671>!
idle tiger
I restart the whole server maybe once in 2 weeks, and not for every small issue I wanna fix. Making this feature request to not work for me.
desert jay
clearing the database or wiping everyones charecters isnt something you can do without restarting the server
idle tiger
Yes it does actually
I just restart the resource, and it redirects everyone back to the character selection screen, and they just log in within 5 seconds to the same state they were in before.
desert gorge
ratio
vast cargo
Yes it does actually
Seconding this.
A well done ressource should not require a restart unless it's own code is modified.
However txAdmin gotta take into account the current state of servers instead of status quo.
So no opinion on whether it should be in or not.
idle tiger
How does supporting my opinion count as seconding it? Even though it is super unrelated to the topic, you mentioned it anyway. I didn't claim my resources are perfect nor say they don't, anyway you should restart your resources on changes, like updates (code or database). And my opinion was that in this case you should restart only the relevant resource and not the whole server and kick everyone in the process.
idle tiger
However txAdmin gotta take into account the current state of servers instead of ...
I agree, because you should favour where all servers are currently at, but still, maybe there is some tweak that could be done to make it perfect for the all of us
Like an API or something else?
vast cargo
How does supporting my opinion count as seconding it? Even though it is super un...
Seconding smth. = Supporting smth.
idle tiger
Oh, sorry, I guess this is some language barrier I have. Because in my native language this can be seen as something else
vast cargo
I am neither native so I also had my fair share of confusion here 😅