in my opinion, MBrahmanPoints was a subsidiary of Master Point that displays in the Website (not the actual Master Point) so it can be reverted to zero by creating an sql script. (e.g. SELECT * from dboTantra WHERE MBrahmanPoint > 0; ).
That's my opinion. But I don't revert them to 0. I don't know for what purpose is that.
That Area was not in my scope so I believe you should try GM tool as suggested by jbietz107. Thats the only access you can reach in .TAD file.
Anyone knows how to prevent this error in Zone Logs = "-system err GetGuildID:[]"
Appreciate your response guys!
I did not encountered that error... which part of zone was it?
here is mine:
130605 081128 00000000 -system ser start server
130605 081128 00000000 -system dbg Connect to DB-Server.
130605 081252 68af8a6e -system New Connection user:1
130605 081253 68af8a6e GM Terror sta 56.134.57.206 0000 user:1 result:0
130605 081256 68af8a6e GM Terror dbg Req initchar : terr
130605 081256 68af8a6e GM Terror init char:terr lev:200 x:511 y:87 rupiah: 2000000000, cargo: 2000000000, prana: 11886, bramanp: 99999999, class(2,4) connecttype:1, isDead:0
130605 081312 68af8a6e GM Terror clo ProgressWaitAction eWaitAct_Quit
130605 081312 68af8a6e GM Terror Party Out Leader: PartyCount:1
130605 081312 68af8a6e GM Terror logout charterr: positionX:511 positionZ:87 rupiah:2000000000 cargo:2000000000 prana:11886 hp:6438
My sample is zone 1. I think its not the zone log...
something else made that crash. but not really in the logs. i really can't imagine how did that happened.
The exploit would not show up in the logs. It would only show err clo read in the logs if anything.
not a bit of idea. i never crossed into that trouble.