quote:Originally posted by Survey_Says

My last post got me thinking... you know what would be cool is some sort of auditing system for sysop actions.

Like once a game is banged and the 1st player logs in, the system would then track and timestamp every change made in TEdit. This log would then be accessible in game with the use of a new global command. I think this would solve a lot of disputes and give players peace of mind and also allow sysops to once again play in their own games without being harassed.


This doesnt belong here....
But anyhow..
You shouldnt play in games where the op of the game or the op of the server plays in the game (general rule #1)
also if they are cheaters and liars then I guess that the audit logs are going to be a bit useless arent they cause they will just edit the logs. PsychicRealms is a bit like this, they edit using tedit then edit the daily logs to fit new things like invasons that didnt happen, palayers that were #sd# now brought back to life and that's removed from logs, ect ect

quote:Originally posted by Doctor Who

quote:Originally posted by Survey_Says

My last post got me thinking... you know what would be cool is some sort of auditing system for sysop actions.

Like once a game is banged and the 1st player logs in, the system would then track and timestamp every change made in TEdit. This log would then be accessible in game with the use of a new global command. I think this would solve a lot of disputes and give players peace of mind and also allow sysops to once again play in their own games without being harassed.


This doesnt belong here....
But anyhow..
You shouldnt play in games where the op of the game or the op of the server plays in the game (general rule #1)
also if they are cheaters and liars then I guess that the audit logs are going to be a bit useless arent they cause they will just edit the logs. PsychicRealms is a bit like this, they edit using tedit then edit the daily logs to fit new things like invasons that didnt happen, palayers that were #sd# now brought back to life and that's removed from logs, ect ect



Your "forum-nazi-attitude" doesnt belong here....
But anyhow..

I apparently made the mistake and thought it would just be assumed that if we were talking security logs there would have to be some mechanism to "secure" them such as encryption or something similar to prevent editing. Common sense?

I find it amusing you site another example of dishonesty in tradewars to write off an idea about curbing dishonesty in tradewars.

alright lets start a new topic for this in Smack talk i would like to really see what you guys have to say
STRIDER

This is for whoever maintains the code of this forum. Something useful would be a bugzilla type database on eisonline.com where users could enter bugs/ideas. JP would then assign them priorities and versions. This way, we don't lose any of these good ideas even if most of them are not implemented in v3 and also leaves an audit trail so we can see the status without having to email/bug JP so much.
earth.

I have a bug tracking tool available if JP wanted to use it. It handles bug entries, notes, status, what version it was found in, what version it will be fixed it. You can add attachments to help better fix the bug, screenshots for example.

JP could create accounts and assign rights to them giving them or restricting access to the bug list

I created the tool for bug tracking of my own projects

Silly