What a horrible night to have a curse…
Oh, wait…
An English translation patch for the FDS game, “Dracula II: Noroi no Fuuin” is now available to download! You play the role of Simon Belmont seven years after the event of the previous game. Turns that after Simon dispatched Dracula, a curse was placed upon him by the Prince of Darkness. The curse would eventually claim Simon’s life, and the only way Simon can remove this curse is to gather five of Dracula’s body parts, each located in a mansion in the Transylvanian countryside, and bring them to the remains of Dracula’s castle to burn them and bring Dracula back so that Simon can kill him again.
This game was released in the US and Europe as “Castlevania II: Simon’s Quest”. As for the FDS version, there were changes between the localized and the original versions of the game.
1. You can now save your progress with a battery save instead of inputting passwords.
2. The music played during the game uses the extra sound channels provide by the Famicom Disk System.
3. When completing the game, you’ll receive a message of how many in-game days it took to beat the game followed with ending credits.
4. Loading times! Duh!
v1.0
Initial Release
v1.0a
The text from one of the thirteen tomes had its text fixed
CRC-32: 3a0bb17b
SHA-1: 82be8e77c41c2e9d0675dac8f20d6bf85c7f8f19
Anime_World: Author of Graphic Decompression & Recompression programs
mziab: Assistance with Title Screen Hacking
Cyneprepou4uk: Deactivation of Anti-Hack Checks
abridgewater: Assistance with Title Screen Hacking and Bug Fixes
bizqwit: Proving Notes on Dracula II
FCAndChill: Beta Testing and Rom Hacking
xttx: Beta Testing
Lorenz: Beta Testing
Just find one error where the book clue beside Deborah Cliff is a mess.. was it just me?
Can you post a screenshot and/or send a link to a Mesen save state before this happens? If there is an error in the patch, I want to see it for myself and fix it ASAP.
I found the problem area where the clue at Deborah Cliff was causing the game to spout garbage text. The line has been fixed with an update to v1.0a to the patch. Thanks for bringing this issue to my attention.