01-29-2017, 09:17 AM
When you ban a player on the first round it causes the ban to populate in ULX instead of gbans
We already know this however this can cause issues if we want to unban the player because gbans takes over the ban command. Someone is bound to forget or not be informed and then problems happen.
Once the player is written into the old ban file the player is at the mercy of dink going into the ban list and removing the player using FTP and notepad. If dink goes away it could be a long time before it is fixed.
This fix wont prevent an accident like this from happening but it will stop the ban from being written in the default ban file.
Using FTP go to the ban file
Right Click
File permissions
Set permission to 444 OR only check the boxes marked READ
Another possible fix would be to change the ULX ban command
Just go into the LUA and change it to !ulxban which would completely neuter it.
The command just would not work until gbans is up and running.
Any thoughts?
We already know this however this can cause issues if we want to unban the player because gbans takes over the ban command. Someone is bound to forget or not be informed and then problems happen.
Once the player is written into the old ban file the player is at the mercy of dink going into the ban list and removing the player using FTP and notepad. If dink goes away it could be a long time before it is fixed.
This fix wont prevent an accident like this from happening but it will stop the ban from being written in the default ban file.
Using FTP go to the ban file
Right Click
File permissions
Set permission to 444 OR only check the boxes marked READ
Another possible fix would be to change the ULX ban command
Just go into the LUA and change it to !ulxban which would completely neuter it.
The command just would not work until gbans is up and running.
Any thoughts?
