3 bugs detected * Checks for more perhaps *

[foody]

1 - Inventory problem in engine resulting in a severe crash.
2 - Weapon problem, damages is displayed but effect is not occured during combat. For example I created a weapon by the name of Giant Sword + 10 with the following attribute:

ROF/rd 1
Range 2
Damage Dice, Sm 14
Nmb Dice, sm 2
Damage Bonous, sm 10
Dmg Dice, lg 20
Nbr Dice, lg 6
Dmg Bonouse, lg 0

It says in the engine Damage 2D14 + 20 while in reality I want it to be 2D14 + 10 because I clearly specified 10 and not 20. Then during combat when I do the damage it says I make total damage of 24, 31, 34 and so on. But the monsters loses exactly no hit point. But when I used the most powerful sword in the game called, Magic Sword of Destruction + 30 it does damage of 2k+ and kills them with one hit. I used also the Ultimate Vorpal Sword and it too did deadly damage and killed them...but what I don't understand why this weapon which I created refuses to do damage to the monsters even if it clearly says I did such and such damage.

3 - Weight encumbrance (which I am bitching for a full month by the way) is not and I repeat is not working. I gave giant sword + 10 (in the engine it says + 20 which it shouldn't, let us not forget the inventory problem engine crash) an encumbrance of 12000 but what does the engine say...guess, guess. Ohh come on guess...it says NOTHING! Practically it doesn't even detect the encumbrance...sweet, no?

4 - * Goes happily to find more bugs to get it fixed *

[CocoaSpud]

Please email me a single file from your design, the items.dat file. I will import your items and perform the same actions you mentioned.

[CocoaSpud]

It says in the engine Damage 2D14 + 20 while in reality I want it to be 2D14 + 10 because I clearly specified 10 and not 20. Then during combat when I do the damage it says I make total damage of 24, 31, 34 and so on. But the monsters loses exactly no hit point.

According to the files you sent me from your design, you have checked the 'Is Non-Lethal' option for this Giant Sword. That means no damage will be done to the target.

I'm still working on the rest of your bugs...

[foody]

Is that what that is? I was wondering what that option is all about. Thanks [img]smile.gif[/img]

[CocoaSpud]

Weight encumbrance is not and I repeat is not working. I gave giant sword + 10 (in the engine it says + 20 which it shouldn't, let us not forget the inventory problem engine crash) an encumbrance of 12000 but what does the engine say...guess, guess. Ohh come on guess...it says NOTHING! Practically it doesn't even detect the encumbrance

According to the files from your design, this item has an encumbrance of 1200. When I changed it to be 12000 I was not able to give the character the item. I kept getting a warning from the engine stating that the item was too heavy for the character (with strength 145)). That part seems to be working just fine.

I changed the item back to 1200 encumbrance and ran a test with it. After taking the item, my character's encumbrance did not change, just like you said. The problem is that the engine ignored encumbrance for all magical items, and this Giant Sword +10 is magical. I have changed the engine so that it always computes encumbrance for magical items. If you want a magical item to have zero encumbrance then you can leave it a zero. This business of ignoring encumbrance for magical items is in the book, but it should only have been ignored for magical armor instead of for all magical items.

In the next release, non-zero encumbrance will be totalled for all items.

[foody]

* Bows down * I respect you man, like you never believe. It is true, you are a very cool person to respond to the board and your awesome when it comes to helping people. Your da man, your da man

[foody]

CocoaSpud do you log in in MSN?

[CocoaSpud]

CocoaSpud do you log in in MSN?

I have it installed, but I rarely use it. Mostly it's just for when I use GameVoice during a multiplayer gaming session. I usually don't have time to use it for chat.

[CocoaSpud]

1 - Inventory problem in engine resulting in a severe crash.

I believe I have this one fixed now.