Zound52 Beta 3
Ok another big update/fix.
Sorry for the quick update but thats it for now as we now just need to test it as I'm sure the bugs are going to be small.
1. Fixed when Admin bans a player and disables himself.
2. Fixed where everyone can see trigger when admin triggers a AdminOnly trigger.
3. Fixed where banned player can call display of triggers.
4. Fixed where banned player gets startup message.
5. Fixed where admin bans player but player still has some access.
6. Added New Menu
To make Zound unique it has its own menu look now which is more practical as it is offset slighty so the messages are seen.
7. Added Display Triggers button in Client Menu.
8. Added auto default syntax to [Zound52.ZPlayerList] and [Zound52.ZPlayerBan].
9. Added Player Enter Message.
This is also dependant on whether the player has been:
a) Banned from Zound
b) bAnnounce=True
10. Added Daily Chatlog
This will write a daily chatlog in the form of ZoundChat01.log up to ZoundChat31.log
2005/08/28 - 14:07:54 - ProAsm : This is a test message
11. Added Chat Filter
This is a basic chat filter and uses a stuct format.
[Zound52.ZoundFilter]
Filter=(CensorWord="****",BadWords="badword1,badword2,badword3,badword10,")
The CensorWord can be whatever the Admin would like to use to replace the BadWords.
The number of BadWords per Filter= can be 50 although practically only around 10 words should be used per Filter.
12. Removed Usehandler2 and corresponding BroadCastHandler
After several experiments it was found the BCHandler method that ServerExt uses is disasterous and can cause a huge crash on your server if not setup correctly.
It is for this reason I have switch back to the good ol Zound BroadcastHandler as its stood the test of time and with Zound now having its own Chatlog and Chat Filter it should no longer be an issue.
http://www.proasm.com/files/beta/zound52b3.zip
NB. For this Beta only, if using the Chatlog together with the ChatFilter, you will get 2 messages in the Chatlog if a player swears.
1 Before filtering and another afterwards.
This is just to see if all works ok - so swear away
Ok another big update/fix.
Sorry for the quick update but thats it for now as we now just need to test it as I'm sure the bugs are going to be small.
1. Fixed when Admin bans a player and disables himself.
2. Fixed where everyone can see trigger when admin triggers a AdminOnly trigger.
3. Fixed where banned player can call display of triggers.
4. Fixed where banned player gets startup message.
5. Fixed where admin bans player but player still has some access.
6. Added New Menu
To make Zound unique it has its own menu look now which is more practical as it is offset slighty so the messages are seen.
7. Added Display Triggers button in Client Menu.
8. Added auto default syntax to [Zound52.ZPlayerList] and [Zound52.ZPlayerBan].
9. Added Player Enter Message.
This is also dependant on whether the player has been:
a) Banned from Zound
b) bAnnounce=True
10. Added Daily Chatlog
This will write a daily chatlog in the form of ZoundChat01.log up to ZoundChat31.log
2005/08/28 - 14:07:54 - ProAsm : This is a test message
11. Added Chat Filter
This is a basic chat filter and uses a stuct format.
[Zound52.ZoundFilter]
Filter=(CensorWord="****",BadWords="badword1,badword2,badword3,badword10,")
The CensorWord can be whatever the Admin would like to use to replace the BadWords.
The number of BadWords per Filter= can be 50 although practically only around 10 words should be used per Filter.
12. Removed Usehandler2 and corresponding BroadCastHandler
After several experiments it was found the BCHandler method that ServerExt uses is disasterous and can cause a huge crash on your server if not setup correctly.
It is for this reason I have switch back to the good ol Zound BroadcastHandler as its stood the test of time and with Zound now having its own Chatlog and Chat Filter it should no longer be an issue.
http://www.proasm.com/files/beta/zound52b3.zip
NB. For this Beta only, if using the Chatlog together with the ChatFilter, you will get 2 messages in the Chatlog if a player swears.
1 Before filtering and another afterwards.
This is just to see if all works ok - so swear away