10.06.2008, 13:42, written by Mario Donick

One Unique, Two Uniques, Three ...

While testing 0.3.1, I discovered a small bug in monster data file. Two unique monsters, the "weapon smith" (inhabiting LambdaRogue since the earliest versions) and the new unique "lonely librarian" accidently had the same dungeonlevel number.The "unique monster"-concept of LambdaRogue always had been "only 1 unique per dungeon level (and not every dlv has a unique)", but I always asked myself what would happen if there were two uniques in the same lvl. I never tried, until now.And the answer is: Nothing special. The first unique monster in the data file with the proper level number appears first. If it is killed, the next unique monster with the proper level number appears when the level is entered the next time. If no more uniques with the proper level number exist, nobody appears. No crash, no quest problems.So now I ask myself what to do about this bug. Leave it as it is? It surely gives me more flexibility, and ensuring that quest relevant uniques are the first ones to appear is easy, by simply ensuring the correct order in data file.Hm.

Earlier / Later / Permanent Link

 

Write a comment

Your name:


Headline:


Spam protection: Enter the result of »eleven minus six« as word:


Text of your comment:


Click »Send« to save your comment.

powered by d.elog blogging software v0.6 / 17.04.2009
© Mario Donick 2005–2009.
d.elog contains Xinha, a free WYSIWYG textarea editor.