Posted February 01, 2020
high rated
Ever wonder why Archery sucks so had in the first Ravenloft game? It's actually because there's an error in the game code. Arrows always do 0 damage. If you've ever killed anything with a bow in Strahd's Possession, it was Undead and you were using an Undead Slaying arrow, because everything else just bounces harmlessly to the ground.
This is a problem I discovered way back in the day of release, but I don't believe it's well known. It stems from the fact that there were two versions of Strahd's Possession, a disk based and a CD based. The CD based included voices and new characters and quests, and it's the one being offered on GOG. Now, when these new quests were added in, some new items needed to be added too, causing a reorganization of OBJECTS.DAT. The arrows were moved to a new position in the hex code, but unfortunately their damage values were left behind, so now the hex for their damage reads 00 in all six instances, instead of the correct 01 06 00 01 06 00 (for sm - 1d6+0, lrg - 1d6+0).
I've made a working copy of Objects.Dat that will repair the issue, but I'm not sure if GOG is interested in community fixes to 27 year old games. If you'd like to fix it yourself, I've included an image of the exact hex that needs to be edited. Or, like, don't use bows like you've been doing. I'm just happy to see this issue finally be documented.
Happy gaming.
This is a problem I discovered way back in the day of release, but I don't believe it's well known. It stems from the fact that there were two versions of Strahd's Possession, a disk based and a CD based. The CD based included voices and new characters and quests, and it's the one being offered on GOG. Now, when these new quests were added in, some new items needed to be added too, causing a reorganization of OBJECTS.DAT. The arrows were moved to a new position in the hex code, but unfortunately their damage values were left behind, so now the hex for their damage reads 00 in all six instances, instead of the correct 01 06 00 01 06 00 (for sm - 1d6+0, lrg - 1d6+0).
I've made a working copy of Objects.Dat that will repair the issue, but I'm not sure if GOG is interested in community fixes to 27 year old games. If you'd like to fix it yourself, I've included an image of the exact hex that needs to be edited. Or, like, don't use bows like you've been doing. I'm just happy to see this issue finally be documented.
Happy gaming.
No posts in this topic were marked as the solution yet. If you can help, add your reply