Quote:
Originally Posted by Matt Arnold
We've heard this requested before, and would agree that it would be great to have. But as someone who has worked at a previous company and added an audit log to a fairly complex database, I can tell you that it's a hellova lot of work to do, moreso if you need to make sure the audit log is tamper proof as well, so I don't think this is really a realistic option in the near future, unfortunately.
|
Not to oversimplify the development that goes into it, but I don't think it is as complex as you make it out to be. All in-game changes are submitted back to a server and updates are made to that player in the database. It shouldn't be a monumental effort to log that change out to a separate table in the database before the update is made. It shouldn't matter even if your database table is relational. The log entry can just be something as simple as having (ChangeSource, ChangeMade) field, with the ChangeMade field as a text blob containing a key value pair for the: Field, ValueBefore, ValueAfter.
ChangeSource | ChangeMade
IPAddress:98.xxx.xxx.xxx | {BatterPower,50,60}
I have the knowledge to be fairly confident in saying that this shouldn't be a big development effort. Now whether the OOTP sees enough value in furthering the online league experience to prioritize this is a separate matter.