I really like this - those second person dungeon master barks are comfort food.
I wander if a variant with shorter barks would not be prudent - it may be tricky to read these every second swing during combat.
How about something like “You parried” , “Harpy dodges” , “Harpy gets cut, bleeds lightly” Just to limit the number of words to scan through. Criticals could get extra verbose.
On an unrelated note: what are your settings? Your game looks quite a bit different than mine. I like it.
Ah. I did try these settings initially - I liked it in the dungeons but felt it was too much of an eye-scramble in the open world, with modern skies and render distance. Settled on 640 with no palettization in the end, but may change my mind yet. Thanks.
Aristide has since fallen, but would have appreciated the shorter messages you have implemented.
The verbose log documenting the event went something like this:
"AristideTorchia successfully commented, inflicting AoE damage with daedric logic" "PettyModerator just spawned" "PettyModerator successfully casts 'remove comment' spell, partially saving against reality" "AristideTorchia fails to save against 'enraged' spell, lands blunt insult on PettyModerator" "PettyModerator critically lands with the hammer of banning" "AristideTorchia just died"
Hey! I love the idea of this mod but currently it's a bit overwhelming when a lot of stuff is happening. Screen gets filled with 8 messages really fast filling up the space breaking immersion. I talked about this with some guys on discord and one of the guys pointed out that using MidMessage function could be a great solution to this.
The event message would be overwritten by the new event and the screen wouldn't get filled with messages. It would be enough to give that old school feedback feeling that at least something is happening rather than wondering if my attacks are swinging the air and so on. Having an option to turn on Midmessage function would be great!
That's the default Daggerfall behavior when readying a spell to fire. If you load up the Internal_Strings localization file, you can blank out the pressButtonToFireSpell value and it should effectively remove it from displaying.
16 comments
I wander if a variant with shorter barks would not be prudent - it may be tricky to read these every second swing during combat.
How about something like “You parried” , “Harpy dodges” , “Harpy gets cut, bleeds lightly”
Just to limit the number of words to scan through.
Criticals could get extra verbose.
On an unrelated note: what are your settings? Your game looks quite a bit different than mine. I like it.
My settings are just the regular graphics using retro mode in-game. It's 320x240 using palettization. It's fairly close to how it looks in DOS.
I also use my graphics mods that corrects a lot of the errors in the original graphics.
Ah. I did try these settings initially - I liked it in the dungeons but felt it was too much of an eye-scramble in the open world, with modern skies and render distance. Settled on 640 with no palettization in the end, but may change my mind yet. Thanks.
The verbose log documenting the event went something like this:
"AristideTorchia successfully commented, inflicting AoE damage with daedric logic"
"PettyModerator just spawned"
"PettyModerator successfully casts 'remove comment' spell, partially saving against reality"
"AristideTorchia fails to save against 'enraged' spell, lands blunt insult on PettyModerator"
"PettyModerator critically lands with the hammer of banning"
"AristideTorchia just died"
The event message would be overwritten by the new event and the screen wouldn't get filled with messages. It would be enough to give that old school feedback feeling that at least something is happening rather than wondering if my attacks are swinging the air and so on. Having an option to turn on Midmessage function would be great!
pressButtonToFireSpell,Press button to fire spell.
to this?
pressButtonToFireSpell,
That should tell it to blank out the line.