6.53
July 23rd, 2008There was a really stupid bug in 6.51 preventing loot from making it to the bidding window. I believe its been fixed now, and I’m trying to get 6.53 out the door on all sites.
There was a really stupid bug in 6.51 preventing loot from making it to the bidding window. I believe its been fixed now, and I’m trying to get 6.53 out the door on all sites.
Hey folks. I think I finally managed to get a proper build of 6.51 out the door. wowace, wowi and wowui all have it. I’m still working with curses new build system to get it posted properly, but those problems should be resolved shortly as well.
Sorry for the absence here for a bit. Its been a busy few month or so. I’ll try to answer a bunch of questions all at once with this post.
First, 6.51 is not yet released, but it IS very close. I was hoping for this Friday, and may still make that, but its getting close, and there’s still stuff to be done.
Yes, I know there are list corruption issues. I’ve found a number of them in my own testing, and certainly have had GREAT response on the jira tickets to provide LUA files and data for debugging those. Many of those fixes will be present in the 6.51 release. I just tried making a custom filter for all the stuff thats resolved for 6.51, try this url: http://tinyurl.com/5fgprq
No, this project hasn’t been abandoned. Vacation to Hawai’i, general burnout, and preparing for the arrival of our first child has me devoting less time than I’d like to this. I’m also hoping the 6.51 release will address a good portion of the problems being reported out there.
In any case, please feel free to comment here, or (of course) leave more jira tickets. They will be addressed as quickly as I can get to them.
Peace,
- ZJ
This will be pushed out later today, and will hopefully solve the most recent spat of bugs that have cropped up after gold release.
Two things of note:
I don’t believe this is comprehensive. I suspect there are still ways for the lists to get screwed up under some circumstances, but I can’t fix ‘em if I don’t know what happened. So … again, please. If you note some weird behavior, please ticket it on the jira, attach your SKG.lua saved variables file if you can, and I’ll do my best. PLEASE run bugsack/buggrabber as well so I can get good clean stack traces when errors do occur.
Oh, finally, I’m leaving for hawaii tomorrow morning for a week’s vacation. Other than infrequent web access, I won’t be touching anything until I get back in a week, so bear with me, and I’ll do my best to fix stuff when I return.
Thanks for being patient…
ZJ
Thanks to bug reports, I now have at least two distinct failures that have occurred with the gold version that cause list wipes (or, at least, the appearance thereof). I’ve so far identified at least two causes, and I’m analyzing a third now. In order to prevent these from occurring, the following changes are being made:
* If SKG detects that an earlier version of SuicideKingsGeo is running or loaded, it will COMPLETELY DISABLE. At least two of the cases where this happened, someone had just logged in with an old version running, and this caused big issues. As has been mentioned in EVERY SINGLE POST I’ve made about this topic, it is a VERY bad idea to try and load them side by side. Don’t do it. Just don’t. Please.
* I’m now going to be doing significantly more checking to see if a bad value is passed along with any attempt to move a player, whether through a PLRMV (move player up or down), PLRSC (suicide), or PLRIN (insert) command. Two of the cases involving corruption showed a nil or 0 value being passed in. This should prevent that from occurring.
I’ll post more details as I understand them.
Alright. Its out there. Can’t believe I finally made it to a public release. It feels like it took 7 months. Oh… thats because it did.
Thanks for y’all being patient with me as I learned how to do all this. Hopefully, you find it was all worth it.
- ZJ