Showing posts with label FAIL. Show all posts
Showing posts with label FAIL. Show all posts

02 April 2012

Math FAIL.

One of my surprise areas had a surprise itself: some of the data was incorrectly set because I did some bad math.  Bah.

Once the problem is resolved (the mistake was corrected but the script needs to be restarted), then I'll extend the accessibility to the area by a couple of days.

[Edit]: The fix has been applied, thanks to ServerGM.  Whew.

21 November 2011

Filter Denied

Today was a mixed day of productivity for me.

I wrote a new support script for a small upcoming quest, and then – while it was on my mind – turned my attention to a quest that has been simmering on the back burner for some while.  I launched my test server and tested the script over and over again, but the script was behaving unpredictably.

See (and this is where I get a little technical) we have some pretty cool filtering functions to support our scripts.  We can place a filter on a door that would translate into "allow only fighters to pass through this door" (a handy thing to have on the Fighter's Guildhall to keep those nosy mystics away), and we can also have a fancier filter that would translate into "allow everyone except fighters to pass through this door."  The former function is handled by the filtering function, while the latter is handled by the individual script calling the filtering function.

This means that not every script will support this exclusionary logic, and sho'nuff, the script which I was using for my quest did not support this style of filtering.  It took me two hours of debugging to realize that.

Good grief!

26 February 2010

YAPPYFAIL.

I'll give it one last run-through before dragging the NPCs into place.

It turns out that the reward NPC for the new quest is not delegating the rewards properly.  I've tried changing the format of how the reward is bestowed, but it's a graceless, kludgey fix and I'm very unsatisfied with it.  I may need to review the reward script, but I suspect it's just the way that I'm (mis)using it.

So, that's a YAPPYFAIL for getting this quest in and running on this update.  My goal is now to get this quest – plus another new quest – ready for V642.