[Bugs] Corpses issues with leavecorpses set to 1

[Magoth78]

Hi there,

On my server I've set the leavecorpses variable to 1 so people can loot each other after being killed.
But when a player dies (from PvP or PvE) the corpse disapears. Everyone has to zone to see the corpse. Looks like an info sent to clients is missing when a Player dies.

Does anyone experience the same problem?

Thx,
Mag

[sdabbs65]

Originally Posted by Magoth78

Hi there,

On my server I've set the leavecorpses variable to 1 so people can loot each other after being killed.
But when a player dies (from PvP or PvE) the corpse disapears. Everyone has to zone to see the corpse. Looks like an info sent to clients is missing when a Player dies.

Does anyone experience the same problem?

Thx,
Mag

What server version are you running ?
this is not a problem on my shard 6.0DR1

[Magoth78]

I'm running a 0.6.0dr2 server.

On Empire1, I used to have a 0dr1 server, all was fine. I guess I gotta find the dr1 sources and see the differences in attack.cpp and playercorpse.cpp :/

Anyway thx for the answer,
Mag

[FaerinTelDanor]

I have the same problem with 0.6.0 dr3 ... haven't been able to track down the problem yet.

[Magoth78]

sdabbs65> By any chance, could you send me your attack.cpp (in your 0.6.0dr1 sources), please? (funzy78@hotmail.com)

Cause, I remember having this bug in 6.0dr1 just after LE added the PvPreward/PvPitem/LootCoin features. But he fixed it very quickly and I dunno if the changes have ever been sent to cvs.

So maybe you got the changes pre-PvPreward and in this case, this won't help me, or post-PvPreward and it might help me.

Thx by advance,
Mag

[Magoth78]

I've looked into my old 5.7dr6 sources and checked the file. The corpse is made in the same way that in the 0.6.0dr2 sources (minus the check for the PvPreward variable).

// now we apply the exp loss, unmem their spells, and make a corpse
	// unless they're a GM
	if(!GetGM())
	{
		if(exploss)
			SetEXP(GetEXP() - exploss > 1 ? GetEXP() - exploss : 1, GetAAXP());

		BuffFadeAll();
		UnmemSpellAll(false);

		// check db variable 'leavecorpses'
		char tmp[20] = {0};
		database.GetVariable("leavecorpses", tmp, 20);
		int leavecorpses = atoi(tmp);
		if(leavecorpses)
		{
			// creating the corpse takes the cash/items off the player too
			Corpse *new_corpse = new Corpse(this, exploss);
			entity_list.AddCorpse(new_corpse, GetID());
		}

//		if(!IsLD())//Todo: make it so an LDed client leaves corpse if its enabled
//			MakeCorpse(exploss);
	}

So the solution is *probably* not there. Now I guess I gotta check how the Corpse() function is working since the PvPreward/LootCoin variables and the SetPKItem() function have been added.

I really do need to find a fix because I got some bad issues with the corpses on 6.0dr2...
1/ corpses poof just after being killed by a npc/pc, you have to zone/camp to see the corpse
2/ or corpses poof just after being killed by pain and suffering and you are not able to see them even after zoning or camping, you have to reboot the zone...

Mag
ps: sdabbs, can you check in your attack.cpp (.6.0dr1 right?), look for the leavecorpse check called in the void Client:eath function and says if you have any check for the PvPreward/LootCoin/PvPitem variables, please? if it's the case, that would really help if you could send me the files attack.cpp and playerscorpses.cpp. Thanks.

[Magoth78]

I've found in the code a very very very ghetto fix but that makes the player's corpses staying in the ground once they die.

Just after this line in your attack.cpp: (~1317)

entity_list.AddCorpse(new_corpse, GetID());

add

entity_list.SendZoneCorpsesBulk(this);

It's very ghetto as everyone will can see/loot the corpse but the player who' just died will crash everytime. I think I understand why when I looked at the SendZoneCorpsesBulk thingie, it's like I send a corpse zone's update to the client who just died once he 's dead, but honestly why should'nt it work after all?

and if I add:

entity_list.SendZoneCorpsesBulk(other->CastToClient());

it makes a zone corpse's update to the player who has killed the other one. The player killer crashes, but not the player who just died, this time..

Any help would be appreciated,

Thx by advance
Mag

[Dakaar]

Im getting this problem in 6.2-DR1 Right now.

When player A kills player B, player B's corpse is visible to everyone but player A. Player a can zone and then see the corpse. Anyone can loot player B's corpse(as it should be), but when they do so they are 'bugged' untill they zone and cant access inventory, target stuff,etc.

Zone.exe reports no funky opcodes or anything during this time.

[Dakaar]

In Attack.cpp line ~1,165
in Client:eath()
this line :
entity_list.QueueClients(this, &app);

Shouldnt it be:
entity_list.QueueClients(this,app); ?

I am at work and just going over the code.

Im thinking maybe its a problem in Corpse::Corpse ? If someone could post older versions of the functions to compare with? Thanks

Also, consider going through NPC:eath and seeing hwo the two corpses are handled and whats different? Just grasping at straws here..

Was addcorpse function changed around the time of rewarditem code? I see the arguments that get passed got simplified alot, could be something there..

looking at npc::death.. Shouldnt the entity_listQueueClients(this,app); in Client:eath be entitylist.QueueClients(other,app); ?

[vRandom]

I think the best way to look at the older code would be to browse the cvs, http://cvs.sourceforge.net/viewcvs.py/eqemulator

vRandom

[Dakaar]

The biggest thing that perplexes me.

Is when I kill another character, their corpse briefly appears before it fades away, and if i try to loot during this period, the server crashes.


Having a hell of a time trying to figure out whats wrong.
One thing I notice is that corpse::corpse() constructor changed, but everything else seems practically identical!

SetPKItem() just changes a single variable directly ... its a one line function so I doubt thats it...

CorpseDecayTimer.Disabled is used instead of set to 0 in the new code, might have something to do with it, as thats exactly what the corpse does, is instantly decay, as far as the client can see.

Does SendCorpsesBulkZone crash because in Client:eath the app packet does nto get deleted before a new one is sent?

Someone should try SendZoneCorpses() instead and see if it works!


UPDATE: SendZoneCorpse() to the corpse player makes it so that if you quickly loot before teh 'corpse' disappears, the server wont crash,so thats progress.

When I tried looting, I got an error the "LOOTING FOOKED3", and that is only displayed when the corpse object is not a corpse(or is null), soo i think its more of the wrong corpse being looted!

SendZoneCorpse(other); doesnt seem to do anything..

one thing i notice, is if the client isnt grouped, he doesnt get permission to loot corpse?

[Magoth78]

The only fix (very ghetto) i've found is the use of SendCorpsesBulkZone. But, it makes the player on who it's sent, crashing.

Mob::Addcorpse() is the same as it's been on old version and I don't think that the problem comes from attack.cpp. The only new thing added is the PKitem and PvPvariable added, wich is working perfectly.


There is also an other problem about corpse. A corpse be rezzed without having the dead player's approbation.


I remember LethalEncounter fixed it quickly just after he added the Pkitem/pvpvariable thing. But i don't think the fix has been sent to Sourceforge.

[Dakaar]

Was really tired last night... Soo ignore some of that

The big question, is why does sendcorpsesbulk crash the player, and what can be done to prevent that!

I tried making a packet with just the new corpse, but I dont think that worked , using the template of sendcorpsesbulk

[Dakaar]

This bug occurs because the new_corpse's id and the client's id are the same. when a player dies, that id is despawned.. the corpse gets despawned with the client.

The corpse and the client need to have differing ids.

Everything is working perfectly on my server, will have a fix in a few

[Magoth78]

Nice one there., I've been searching for some times and did not find anything interesting.

Also, did u notice any bug when a player is killed by 'Pain and Suffering'? looks like his corpse just poofs.