Login to ZARP
|
|
@Tommy228 Tommy228 released this on 7 Sep 2017 · 59 commits to master since this release Assets Source code (zip) Source code (tar.gz) This new version includes bug fixes, new features and general improvement. Please note that the website code is not supported on this version. A new version for the website damagelogs is under development. If you are updating from 2.4, make sure you are updating your configuration file as well ! New features : Shot logs during the death scene. To use this, press the gun button. You can now force a player to stay on a chat. You can now create admin-reports on the reports menu. These can be used under different situations, for example you can question a player about an RDM even if he didn't get reported. You can also directly open a chat with a player using this feature. Players can now view their reports on the reports menu. ServerGuard support for the autoslay command. If you are using ULX, you can now replace autoslay by autojail (automatically jails a player for the round instead of slaying him). Language support. The currently included languages are english, german and french. Added cslays and cslaysid commands (for check slays). Allows you to see the remaining slays of a player. The sounds are now downloaded via the workshop by default (this can be changed to use FastDL instead). Added shot logs to the old logs tab. The creator of the RDM manager that this server is using has released this update on the 7th of september, not so long ago. Perhaps this time, the Death scene feature has been optimized? here's the link: github.com/Tommy228/TTTDamagelogs/releases |
|
Last Edit: 7 years 6 months ago by Gurren Lagan.
Login or register to post a reply.
|
This would of being very helpful but guess nope can't have it
![]() |
|
Login or register to post a reply.
|
Warning: Spoiler! [ Click to expand ][ Click to hide ] Johnler wrote:
_Max wrote:
It got removed as it was poorly coded and could not handle large amounts of players on the server. This caused it to lag the server and after a while crash the server. Every situation can be handled by looking at the logs so there is no point us spending a lot of time re-coding this. Alright, now i fully understand why you guys decided to remove it. You did very well. The second Part is where i disagree though. Situations like the ones Gurren mentioned: + "Player has been reported for propkilling, however the accused player disagrees with that" + "Player has been reported for rdming, however the accused player claims that the victim passed an unidentified body" Can not be handled by simply looking at the logs. So no. Not every situation. People also use these reasons as excuses. For example, P1 reports P2 for RDM. P2 says: "You passed by an Unidentified body" (but P1 didn't do so). P1 says that he didn't do that but P2 keeps using that to get away. At the end of the day, we are forced to ask for video proof and most people don't have it. So that makes us pass the report and P2 will get away with RDMing someone for no reason. So yes, 90% of the situations can be handled by looking at the logs, but in my opinion we should have all situations covered without the need of a video. So it would be Nice if some people in the community start working on that to make it better. Since the owners have too much work to handle with that stuff (which is understandable) the Members can start working on that. Gurren even mentioned of hiring someone to do that. But i don't know if that's a good idea. True, it would be a useful tool ingame, and we were all sad when it was removed, however it wasn't worth losing the majority of the playerbase due to the server lagging to shit over. The server used to have huge lag issues due to the Deathmatch and Death Scene features, as I am sure you remember, which was a huge issue for many players, causing the playerbase to struggle dreadfully. |
|
Discord: thexnator Former Community Owner: 2020-2022
Login or register to post a reply.
|
violetfriend_ wrote:
@Tommy228 Tommy228 released this on 7 Sep 2017 · 59 commits to master since this release Assets Source code (zip) Source code (tar.gz) This new version includes bug fixes, new features and general improvement. Please note that the website code is not supported on this version. A new version for the website damagelogs is under development. If you are updating from 2.4, make sure you are updating your configuration file as well ! New features : Shot logs during the death scene. To use this, press the gun button. You can now force a player to stay on a chat. You can now create admin-reports on the reports menu. These can be used under different situations, for example you can question a player about an RDM even if he didn't get reported. You can also directly open a chat with a player using this feature. Players can now view their reports on the reports menu. ServerGuard support for the autoslay command. If you are using ULX, you can now replace autoslay by autojail (automatically jails a player for the round instead of slaying him). Language support. The currently included languages are english, german and french. Added cslays and cslaysid commands (for check slays). Allows you to see the remaining slays of a player. The sounds are now downloaded via the workshop by default (this can be changed to use FastDL instead). Added shot logs to the old logs tab. The creator of the RDM manager that this server is using has released this update on the 7th of september, not so long ago. Perhaps this time, the Death scene feature has been optimized? here's the link: github.com/Tommy228/TTTDamagelogs/releases |
|
Login or register to post a reply.
|
would recording screenshots of the last 5 seconds and the 5 seconds after the person died cause lag?
eg 5 seconds before and after worth of screenshots of what the player sees |
|
Login or register to post a reply.
|
|