New bag bugs
A few weeks ago, I thought I finally fixed the last problem with the bags.
In case you don't play the game, the problem happens when you open a bag but can't get its content.
There were two other problems with the bags, which were fixed in the past, and I thought that this problem was related, so fixing those two bugs would fix this one as well.
One of the bugs was with the client, and when people still reported the problem, I dismissed it to them not using the latest CVS.
3 days ago, I was testing the new way of sending the bags to the client, and specifically asked everyone that wants to help to come on the test server ONLY with a recently compiled client from the CVS.
Some people reported a few issues with the bags, so in order to check if the problem is with the new way of sending the bags, I switched back to the old way, and people still reported issues.
Based on those reports, I added additional debugging code on the server, which pinpointed the problem: The client was sending spurious "close bag" messages.
The client is supposed to send a "close this bag" message only when the player presses the "x" button on the bag window.
However, the client code has been buggy for like 3 years, and it was sending that message each time the bag was closed, regardless of the way it was closed.
So this is what happened:
1. Player opens bag.
2. Player moves to another bag.
3. Server detects the move, and closes the bag the player has open, sending a "close bag" message to the client.
4. The client gets that message, and wrongly sends a "close bag to the server".
5. Sometimes: LAG
6. The player moves to another bag and opens it.
7. The server finally gets the message from the client: "close bag" (step 4)
8. The server closes the NEWLY opened bag.
9. Player tries to get the items from the bag.
10. Server sees that the bag was closed, and will not allow the client to get items from it.
Learner fixed the client bug, but we are having some problems with the CVS which is not working for most of the team members (server won't authenticate them).
Hopefully by tomorrow we can test the problem again, and put an end to a 3 years old bug.
In case you don't play the game, the problem happens when you open a bag but can't get its content.
There were two other problems with the bags, which were fixed in the past, and I thought that this problem was related, so fixing those two bugs would fix this one as well.
One of the bugs was with the client, and when people still reported the problem, I dismissed it to them not using the latest CVS.
3 days ago, I was testing the new way of sending the bags to the client, and specifically asked everyone that wants to help to come on the test server ONLY with a recently compiled client from the CVS.
Some people reported a few issues with the bags, so in order to check if the problem is with the new way of sending the bags, I switched back to the old way, and people still reported issues.
Based on those reports, I added additional debugging code on the server, which pinpointed the problem: The client was sending spurious "close bag" messages.
The client is supposed to send a "close this bag" message only when the player presses the "x" button on the bag window.
However, the client code has been buggy for like 3 years, and it was sending that message each time the bag was closed, regardless of the way it was closed.
So this is what happened:
1. Player opens bag.
2. Player moves to another bag.
3. Server detects the move, and closes the bag the player has open, sending a "close bag" message to the client.
4. The client gets that message, and wrongly sends a "close bag to the server".
5. Sometimes: LAG
6. The player moves to another bag and opens it.
7. The server finally gets the message from the client: "close bag" (step 4)
8. The server closes the NEWLY opened bag.
9. Player tries to get the items from the bag.
10. Server sees that the bag was closed, and will not allow the client to get items from it.
Learner fixed the client bug, but we are having some problems with the CVS which is not working for most of the team members (server won't authenticate them).
Hopefully by tomorrow we can test the problem again, and put an end to a 3 years old bug.
posted by Radu at 12:05 AM
3 Comments:
While we're at the bags, why not make a bag in use when someone is standing on it so it doesn't poof on it's own. IMO this should have been fixed long ago and it makes 0% changes in the gameplay except making game more logical.
And don't say that it would be a performance impact on the server, people who don't want their bag to poof drop stuff in them anyway, except for few (new) players. So in the end you even end up saving some bandwidth :).
The reason is that people will get used to this feature and a lot of people will use their bags in this fashion (many even while AFK) which leads to a shortage of available bags for those maps.
And bags were NEVER meant for long term storage, or for manufacturing items.
Hi we’re the providers of the software program Video Game Design Pro which helps game designers create and manage their Video Game Design documents.
I was specifically contacting you because I think that your blog, and its readers, would be interested in learning about a solution like ours and its benefits on the game design and development community.
If you could please tell your readers about it, ask them to offer suggestions for improvement, or just simply link to our site so they could download a trial, it would be enormously appreciated because your blog seems to be extremely popular and it holds a lot of sway within the game development community.
Before heading directly to our site to learn more about VGDP, why don’t you check out this funny “commercial” that we put together. It’s actually a nice (30 second) introduction to our program and concludes with a link to our site. http://www.thecorpament.com/Super%20Failure.htm
I look forward to hearing back from you, thanks!
P.S. - When the movie concludes it directs you to our website where you can download a trial version of the program or learn more about it…conversely, you could just go straight there: http://www.thecorpament.com/features.html
Post a Comment
<< Home