In the course of testing the Risk ruleset I have run into a few bugs that I collectively call the "View" bugs that I am unable to ascertain the origin of. It was initially my impression that these bugs were somehow caused by an error in my object visibility code, but in light of recent discoveries I am inclined to feel as if the bugs are somehow caused by server caching.

I've also recently discovered a bug I call "phantom ownership" where a player can issue orders on enemy systems they previously owned. I originally felt this related to the "view" bugs, but it just occurred to my that my transfer of ownership may not be complete. At present I am merely transfering ownership by calling the setOwner method with the new owner; This method has seemed to been effective until I noticed the old owner could still issue orders. Is there an additional procedure I should do to completely remove any phantom ownerships?

Back to the view bugs. At present I have documented a few, most likely related, bugs where the players client shows player-owned territory as unowned territory (red, instead of green) and sometimes enemy territory as owned territory (green, instead of red.) All the while players can still issue orders properly on their ACTUAL owned territory. This problem initially arose with similarly named players, like test, and test1, and I noticed the problem didn't occur if names were drastically different, such as Ryan, and test.

What I'd like to know is if anyone has seen anything similar to this? Do my problems seem like server-caching issues, or improper ruleset code for ownership/player joining? This isn't meant so much as a FULL request for help, I'm merely just probing. If anyone would like a more detailed account of the bugs please let me know.

Sine
Ryan 'jphr' Neufeld
---------------------------
visit me at hammerofcode.com

_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel

Reply via email to