PlaneShift

Development => Development Deliberation => Topic started by: ctlmo5 on July 20, 2007, 02:12:09 pm

Title: PS 2007.05.07.00.00.00 quest error!?
Post by: ctlmo5 on July 20, 2007, 02:12:09 pm
Hello, i downloaded and built the planeshift version 2007.05.07.00.00.00.
i find out there have error, if i type "can bring you" to npc (Merchant), and i will have a quest.
The quest ask me to give he a "Steel Falchion".
I gave him a Steel Falchion, and the quest is completed.
Now i can see i only have one item in the "server"(there have two items before i give the Steel Falchion to Merchant)
Sending 1 items...
   Inv item Claymore, slot 17, weight 9.0, stack count 1
In ~Exchange()

And i open the "Inventory", there have one item (seen correct).
However if i check the "server" now, i can see there have two items.
Sending 1 items...
   Inv item Claymore, slot 17, weight 9.0, stack count 1
In ~Exchange()
Sending 2 items...
   Inv item Claymore, slot 17, weight 9.0, stack count 1

And the "server" will die in next several seconds.

I restart the server and i can find the Steel Falchion still on my Inventory.

I think the client and server and no synchronize, and i can see the Segmentation fault after the server is died.

I test this error on both windows xp and mac 10.4.10.

How can i fix this problem!?
Title: Re: PS 2007.05.07.00.00.00 quest error!?
Post by: Lanarel on July 21, 2007, 12:06:53 pm
Is this still happening with most uptodate cvs code? Because crashes like this one happened before, but were fixed at some time.
Title: Re: PS 2007.05.07.00.00.00 quest error!?
Post by: ctlmo5 on July 21, 2007, 03:17:21 pm
i do not have the more update cvs code.
if i only want to fix this problem, can i only download few cvs code and rebuild the PS!?
Title: Re: PS 2007.05.07.00.00.00 quest error!?
Post by: Lanarel on July 21, 2007, 05:49:49 pm
Because you tested this on a 'homebuild' server, I expected you to have built it from source :) You have to update the whole source, but that does not mean you will get a new version of all files, only those that were changed. But I would assume the fix was server side, so that at least means it should not be happening on laanx.