You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In BG1, the player can purchase Aule's Staff +3 (STAF08.ITM) from the innkeeper in Ulgoth's Beard.
BGT does not presently account for this unique weapon (with unique lore) because in BG2 STAF08.ITM is the more generic Martial Staff +3.
While the characteristics are practically identical (Aule's Staff weighs 1 pound less though), I strongly advocate its reinstatement because any unique item should be preserved throughout the trilogy.
BGT does usually do that by creating a duplicate item. In this case, it would be BGSTAF08.ITM and it would replace STAF08 in ULGOTH.STO.
The identified name and description can be imported from BG1.TRA Strings 23977 and 23978.
When SHS Forum is usable again, I will add the last strings from my BG1.TRA review. At the moment I have only a couple of hundred lines left and I should be done by tomorrow, probably before SHS is back online.
Cheers!
The text was updated successfully, but these errors were encountered:
In BG1, the player can purchase Aule's Staff +3 (STAF08.ITM) from the innkeeper in Ulgoth's Beard.
BGT does not presently account for this unique weapon (with unique lore) because in BG2 STAF08.ITM is the more generic Martial Staff +3.
While the characteristics are practically identical (Aule's Staff weighs 1 pound less though), I strongly advocate its reinstatement because any unique item should be preserved throughout the trilogy.
BGT does usually do that by creating a duplicate item. In this case, it would be BGSTAF08.ITM and it would replace STAF08 in ULGOTH.STO.
The identified name and description can be imported from BG1.TRA Strings 23977 and 23978.
When SHS Forum is usable again, I will add the last strings from my BG1.TRA review. At the moment I have only a couple of hundred lines left and I should be done by tomorrow, probably before SHS is back online.
Cheers!
The text was updated successfully, but these errors were encountered: