Printable View
There is some insane numbers going into TBL_UserItems
bt values are becoming very large, color is becoming very negative and quantity is becoming large
M2sever say randomly:
TBaseObject: Destroy code 21
Invalid pointer operation
This was not a problem until updating, maybe I did something wrong maybe there is a bug.
Please advise
and shortly after I post this spam came up in m2sever
[03.05.2007 12:44:22 AM] [Exception] TBaseObject::SearchViewRange 1-1 Zombie0 D406 82 74 13
[03.05.2007 12:44:22 AM] Access violation at address 005EF528 in module 'M2Server.exe'. Read of address 00000018
[03.05.2007 12:44:22 AM] [Exception] TUserEngine::ProcessMonsters 13
this for all different monster
the destroy thing caused the other errors but anyway
any idea which items gone missing ? (prob some storage items)
it seemed like it started with some storage items yes, it was ok for 2 hours until it started it happened loads
items will have random values in them field, some like 567 in the quantity and if you drop an item with 567 quantity 567 of them go on floor and 566 stay in you bag!
I did not yet enable new guild features but do have guild tables
Just wondering did you find any that might cause this error in the code?
All I do is update the exe, update the database (I use just 1 not 2) and deleted all guilds.
so really I can not have done something wrong?
hehe k just checked turns out there is(was) a bug in the storage system related to stacked items
fixed it
although it must have been there for quite some time
btw should have fix uploaded tonight :p
I am pleased you find something but it conserns me that you think it must be there for previous versions
This error happen with in 30 minutes of the sever going on line and I reboot, delete all user items and then it happen again with in 1 hour and 15 minutes (I look for error in the m2 log folder)
but this m2 sever error come some short time after the item become corrupt
thank you for your attention
Just happen again on the new exe must be something else
m2 error come a long time after the item start to error
it seem everything after duramax become corrupt and when it start once it go wild and suddenly every item go mad
the stack bug has been around for ages.
I posted about this, adn said it was best the people change there stackable items.
Glad it is fixed now tho.
qwqwqw there was a bug related to stacked items with storing/taking back
technicaly you had to have the same makeindex stacked items in your storage several times in order to create the bug
(basicaly storing say 5 items then storing another 5 from the same 'pile' in your bag ect)
i didnt notice till now cause i changed it so all the stackable items now get merged in storage rather then all seperate slots
as for the weird numbers: do you still get the m2server error about tbaseobject::destroy?
I did not run it long enough to see it, it come 10-20minute after the item bug begin last time.
I made a mistake some other field has error: makeindex this become a 5 digit number in one case and color become a 9 digit number as for the items added stats they show silly also like this 0-0-245-123-93-58-0-0-210-0-0-0
I run the old exe from april 21? and it did not bug
Also set FLD_Index + FLD_CharName to group primary key and DBSever kept saying violation of primary key which mean some strage happening, some dupe or something
Does anbody else have problems with the recent build?
qwqwqw: obvioulsy since both stored 'stacked' items and stacked items in your bag have the same makeindex it will give dupe errors :p
if you have 10 items in bag and you store only 5 then the server will split the items in bag but keep the same makeindex for both (stacked items do not have unique makeindex values)