Posted August 22, 2018
I am currently playing through the Apple 2GS version of Bard's Tale 1, and I currently have a setup that makes it so that I don't have to worry about SP at all; no more trips to Roscoe's!
* Mage Staff: When equipped, regenerates SP both in and out of combat
* Conjurerstaff: When in inventory (doesn't have to be equipped! at least not in this version), cuts SP costs in half
Combine these two with the fact that spells in Bard's Tale 1 are cheap (12 for Restoration, 10 for Mind Blade, which become 6 and 5 respectively) and my SP is constantly at maximum, and I no longer have to stop by Roscoe's between expeditions.
This strategy does work in the Apple 2GS version of Bard's Tale 2, but that game does have some more expensive spells; Mangar's Mallet is 80, and the Dreamspell is 100! (No, not 100 factorial; that would be too large for the game to handle.) With more expensive spells, I do, in fact, need to be careful of my SP (plus, there are SP drain squares in dungeons).
By the way, some other things about BT2 2GS from quick testing:
* If you know the code and have level 7 Sorcerer spells, you can cast the dreamspell even if you haven't yet been told the code. (This is unlike the DOS version, where the spell fizzles if you try to cast it.)
* You have to enter the Dreamspell's code to cast it; if you try to use the mouse, the spell will not show up on the list of spells to cast.
* Spellcasting items don't need to be equipped to be used (unlike BT2 DOS, but like BT1 2GS).
* In the Grey Crypt, spellcasting items (at least the Galt's Flute that I tried) will not work. (Unlike BT2 DOS)
* The Destiny Stone looks like the Cellar or Castle from BT1. (In the DOS version, it looks like Mangar's Tower.)
* Late game enemies still have too many hit points. In a little test, I cast the Dreamspell, and then my Monk attacked, hitting for over 700 damage (on an enemy that had already taken damage from the Dreamspell), and the enemy didn't die! "hit 13 times for 713 damage."
Incidentally, I have read that, apparently, in the BT1 remaster, the two items mentioned are broken, but that the upcoming (currently in beta in Steam) patch should fix this.
* Mage Staff: When equipped, regenerates SP both in and out of combat
* Conjurerstaff: When in inventory (doesn't have to be equipped! at least not in this version), cuts SP costs in half
Combine these two with the fact that spells in Bard's Tale 1 are cheap (12 for Restoration, 10 for Mind Blade, which become 6 and 5 respectively) and my SP is constantly at maximum, and I no longer have to stop by Roscoe's between expeditions.
This strategy does work in the Apple 2GS version of Bard's Tale 2, but that game does have some more expensive spells; Mangar's Mallet is 80, and the Dreamspell is 100! (No, not 100 factorial; that would be too large for the game to handle.) With more expensive spells, I do, in fact, need to be careful of my SP (plus, there are SP drain squares in dungeons).
By the way, some other things about BT2 2GS from quick testing:
* If you know the code and have level 7 Sorcerer spells, you can cast the dreamspell even if you haven't yet been told the code. (This is unlike the DOS version, where the spell fizzles if you try to cast it.)
* You have to enter the Dreamspell's code to cast it; if you try to use the mouse, the spell will not show up on the list of spells to cast.
* Spellcasting items don't need to be equipped to be used (unlike BT2 DOS, but like BT1 2GS).
* In the Grey Crypt, spellcasting items (at least the Galt's Flute that I tried) will not work. (Unlike BT2 DOS)
* The Destiny Stone looks like the Cellar or Castle from BT1. (In the DOS version, it looks like Mangar's Tower.)
* Late game enemies still have too many hit points. In a little test, I cast the Dreamspell, and then my Monk attacked, hitting for over 700 damage (on an enemy that had already taken damage from the Dreamspell), and the enemy didn't die! "hit 13 times for 713 damage."
Incidentally, I have read that, apparently, in the BT1 remaster, the two items mentioned are broken, but that the upcoming (currently in beta in Steam) patch should fix this.