Item Logging

[GoogleCodeExporter]

Item logging needs to be improved.

1) Log ALL item transactions in a central source that is:
-Easy to read
-Easy to parse with custom tools

Purpose is to improve dupe and cheat detection.

Original issue reported on code.google.com by KimmySpr...@gmail.com on 9 May 2009 at 2:21

[GoogleCodeExporter]

Does anything need to be logged in addition to items moving around? For example,
creation or deletion via CreateItem functions, etc?

I would think the DB would probably be the best place to put this, since a 
flatfile
would be hard to manipulate. Then, we could incorporate it into the current HTTP
server for now, then expand to other tools later on. Depending on how much info 
we're
logging, it could cause some performance issues.

Original comment by AndMetal@gmail.com on 14 Jul 2009 at 5:38

[GoogleCodeExporter]

There is some code on the VZTZ source that will help with this, before Null 
quit 
this 2nd time he coded a Instance ID for items. When a new item is created it 
gives 
it a special InstID which follows that item no matter if a NPC, PC or forge, 
etc has 
it. Also we had a way of recording trading, etc in the database. I will try and 
post 
a diff when I can for the latest version of EQEmu.

Original comment by gmvo...@gmail.com on 25 Aug 2009 at 4:28

[GoogleCodeExporter]

Do the new QS functions address this issue?

Original comment by jeremiah...@gmail.com on 22 Jan 2013 at 1:46

[GoogleCodeExporter]

QS now handles item trades.

Original comment by jeremiah...@gmail.com on 3 Feb 2013 at 4:54

• Changed state: Fixed