freezing on zoning

[vladimir]

Wiz, Image asks which process he should change from 250 to 500. THanks for you help so far

[image]

I think I found it, just wanted to make sure if wasn't something else, the line is like data < 5 && last->PacketSent + 250 .... I set the 250 to 500.

[Wiz]

Originally Posted by image

I think I found it, just wanted to make sure if wasn't something else, the line is like data < 5 && last->PacketSent + 250 .... I set the 250 to 500.

That's it.

[fathernitwit]

I think these are things that should not remain hidden in the netcode, so I will make them into defines in features.h. I am not sure the right names for them. I have turn this:

if (((pack->LastSent + 500) <= Timer::GetCurrentTime()) || (datahigh < 5 && (pack->LastSent + 250) <= Timer::GetCurrentTime())) {

into:

if (((pack->LastSent + DATA_RESEND_DELAY) <= Timer::GetCurrentTime()) || (datahigh < 5 && (pack->LastSent + DATA_RESEND_DELAY_IDLE) <= Timer::GetCurrentTime())) {

I am not sure if those two names are really the right words though. Does anybody have any better suggestions for names on these parameters?

[Wiz]

Nix the differentation between data < 5 and data >= 5. It's pointless. Just make it a halfsecond either way.

[mwmdragon]

I found that a character will become corrupt and then start to kick on zoneing. Also the character will not be able to fight or interact with anyone or anything on the server.

This has occured after equiping certain items... I found that after a character equipped a cloth cord (or whatever the iksar cloth cord it called, Silk sash or something) in the waist slot. The zone.exe will report an unexpected packet every time the corrupted character tries to do something.

Wiz, you seem to know most fixes.. How can I uncorrupt the character file. I have tried to delete all back ups of the character from the database but for some reason the character has the same problem.

UPDATE

I have deleted everything in the player inventory and now the character isn't corrupt.. Any suggestions on what i should be looking for to correct this corruption problem in the database... or is it in the 6.0dr2 release ?