Quote:
Originally Posted by bog18dy
Certainly the most honest, certainly the only server where you will see GM logs public  .
I will resume to posting patch notes here, sad to see a forum with such a long history getting taken over by kids due to the lack of moderators. |
You cant make the logs 100% transparent, unless you open a text field for the end user to pass a sql Select statement to either of the following Databases and tables
DB>=GMS
Table=[dbo].[OPER_Log]
Fields
[who]
[server_group]
[verb]
[what]
[priority]
[when]
DB>=ND_LOG_0
Table>=[dbo].[itemlog]
Unfortunately this table has no datestamp field . So i created a trigger to create a date stamp with the relevant itemlog_id into a new indexed table called[dbo].[itemlogdate]
fields of concern
[code] 'Transaction code'
1 LOG_ITEM_DNPC_DROP_
14 LOG_ITEM_MOVE_VILLAGE_
15 LOG_ITEM_PC_DROP
16 LOG_ITEM_PC_GRAP
17 LOG_ITEM_PVP_TRADE
18 LOG_ITEM_BUY_FROM_NPC
19 LOG_ITEM_SELL_TO_NPC
20 LOG_ITEM_SELL_CLAN_GIVE
21 LOG_ITEM_CLAN_GIVE_MONEY
22 LOG_ITEM_QUEST_GIVE
23 LOG_ITEM_QUSET_REMOVE
24 LOG_ITEM_MONEY_INVAILD
25 LOG_ITEM_BREAK_ITEM
26 LOG_ITEM_SAVE_STORAGE
27 LOG_ITEM_TAKEOUT_STORAGE
28 LOG_ITEM_SOCKET_INSERT
29 LOG_ITEM_CLAN_GIVE_KICKUSER
30 LOG_ITEM_STORAGE_KICKUSER
31 LOG_ITEM_PSSHOP_TRADE
32 LOG_ITEM_SAVEMONEY_STORAGE
33 LOG_ITEM_TAKEOUTMONEY_STORAGE
34 LOG_ITEM_BUYSTORAGE
35 LOG_ITEM_GAMBLE
36 LOG_ITEM_ELIXIR
37 LOG_ITEM_BOXGAMBLE
38 LOG_ITEM_NPC_BOX_GAMBLE
39 LOG_ITEM_USE_
40 LOG_ITEM_ADD_FROM_GMS_SUCC
41 LOG_ITEM_ADD_FROM_GMS_FAIL
42 LOG_ITEM_REM_FROM_GMS
43 LOG_ITEM_DS_UPDATE_MONEY_
45 LOG_ITEM_ADD_FROM_EVENT_SUCC
46 LOG_ITEM_CHANGE_BLOODPOINT_
50 LOG_ITEM_INCHANT_RESULT_
51 LOG_ITEM_INCHANT_SUCCESS_
52 LOG_ITEM_INCHANT_FAIL_
53 LOG_ITEM_INCHANT_REMOVE_
54 LOG_ITEM_PROTECT_ITEM_
55 LOG_ITEM_INCSTR_ITEM_
61 LOG_ITEM_RESOURCE_REMOVE
62 LOG_ITEM_COLLECT_GET
63 LOG_ITEM_COLLECT_REMOVE
64 LOG_ITEM_RESOURCE_GET
71 LOG_ITEM_KILLMONSTER
72 LOG_ITEM_PK_RESULT_
73 LOG_ITEM_NAME_CHANGE_
74 LOG_ITEM_PK_LTS_
80 LOG_ITEM_TAX_ADD_
81 LOG_ITEM_TAX_TAKE_
90 LOG_COMBAT_CHALLENGE_
91 LOG_COMBAT_STEP_
92 _LOG_COMBAT_THREATEN_
95 LOG_HERO_WINNER_REWARD_
100 LOG_CASHITEM_RECEIVE_
101 LOG_CASHITEM_REMOVE_
[zone] map id 1-23 "does not report back a zone(zone=0) when gm tool injection occurs"
[from_uid] ign unique id
[itemfrom] ingame name
[to_uid]
[itemto]
[type1] 0-20 ie 1=cloth,resrources=7
[type2] item id number
Piece of mind i think the community has a right to have access to this sql script, as it will report all the transactions within the server. But ofc for most concerns are item injections and removals.
code>=40 means gm tools to add item to user
code>=42 means gm tools to remove item from user
---------------------------------------------------------------------
USE [ND_LOG_0]
GO
SELECT ItemLog.ItemLog_id, ItemLog.code, ItemLog.zone, ItemLog.from_uid, ItemLog.itemfrom, ItemLog.to_uid, ItemLog.itemto, ItemLog.money, ItemLog.type1, ItemLog.type2, ItemLog.moreinfo, Itemlogdate.Dated
FROM ItemLog INNER JOIN
Itemlogdate ON ItemLog.ItemLog_id = Itemlogdate.ItemLog_ID
WHERE (ItemLog.code = '40') or (ItemLog.code = '42')
ORDER BY Itemlogdate.Dated
-------------------------------------------------------------------
This will report all GMTOOL activity on removal and addition of items.
The image below will show you how easy it is to filter out what you dont want people to see.
By simply adding a 'WHERE' cluase to filter out the sql user login or filtering out a wild card within the object field( ie WHERE Object <>'%such%')
Your website shown below of GM logs are not actually reassuring. Whos to know you are not filtering out certain actions.
I am not having a go at you guys. All i am saying is. Allow people the option to send a sql script to report back where they can filter out what they dont need to see. Hard coding your reports, certainly wont reassure everyone.
