Mudpie 0.3.0 is out, and this one's a big deal
-
Mudpie 0.3.0 is out, and this one's a big deal.
This release is almost entirely about keyboard mode. When you enable it, Mudpie stops relying on TalkBack to read the game to you — it has its own built-in screen reader. Every incoming line is spoken in order, without requiring swipe navigation.
TTS interruption is new and highly configurable. Four methods to stop ongoing speech: shake the device (adjustable sensitivity, with a test button), press Ctrl on a physical keyboard, hit Enter (the command still sends), or just start typing (the keypress still goes through). Each method can be toggled independently. Settings apply globally, can be overridden per world, and can be overridden again per trigger — so a specific trigger can speak immediately and flush whatever was being said, even if interruption is otherwise off.
Character echo is also configurable: choose between none, characters only, words only, or characters and words together. Uppercase letters are announced.
On top of that you get a full menu bar (Session / Worlds / Edit / Settings / Help), reachable with Alt from anywhere. Every world, alias, trigger, and setting is manageable inline without leaving your session. Tab toggles between input and output. No touch required, ever.
MUD clients have always had rich keyboard support on desktop. This brings that to Android, properly, for the first time.
A massive amount of work went into this. If you play MUDs — sighted or not, keyboard or touch — your feedback is welcome.
Android only (for now).
https://github.com/aaron-gh/mudpie-releases/releases/tag/v0.3.0
#MUD #blind #accessibility #TalkBack #Android #gaming #screenreader #gamedev -
Mudpie 0.3.0 is out, and this one's a big deal.
This release is almost entirely about keyboard mode. When you enable it, Mudpie stops relying on TalkBack to read the game to you — it has its own built-in screen reader. Every incoming line is spoken in order, without requiring swipe navigation.
TTS interruption is new and highly configurable. Four methods to stop ongoing speech: shake the device (adjustable sensitivity, with a test button), press Ctrl on a physical keyboard, hit Enter (the command still sends), or just start typing (the keypress still goes through). Each method can be toggled independently. Settings apply globally, can be overridden per world, and can be overridden again per trigger — so a specific trigger can speak immediately and flush whatever was being said, even if interruption is otherwise off.
Character echo is also configurable: choose between none, characters only, words only, or characters and words together. Uppercase letters are announced.
On top of that you get a full menu bar (Session / Worlds / Edit / Settings / Help), reachable with Alt from anywhere. Every world, alias, trigger, and setting is manageable inline without leaving your session. Tab toggles between input and output. No touch required, ever.
MUD clients have always had rich keyboard support on desktop. This brings that to Android, properly, for the first time.
A massive amount of work went into this. If you play MUDs — sighted or not, keyboard or touch — your feedback is welcome.
Android only (for now).
https://github.com/aaron-gh/mudpie-releases/releases/tag/v0.3.0
#MUD #blind #accessibility #TalkBack #Android #gaming #screenreader #gamedev@fireborn Hmm, I wonder if this would work on the Braille Sense, since it seems to have a completely different keyboard system that some things don't recognise. Maybe one day Ill give it a go. Pity I couldn't import a world from Mushclient lol
-
@fireborn Hmm, I wonder if this would work on the Braille Sense, since it seems to have a completely different keyboard system that some things don't recognise. Maybe one day Ill give it a go. Pity I couldn't import a world from Mushclient lol
@davetaylor2112 It probably won't. I don't have one to test against.
-
@davetaylor2112 It probably won't. I don't have one to test against.
@davetaylor2112 the normal UI will work just fine though, and tts auto read and interrupts work the same way.
-
@davetaylor2112 It probably won't. I don't have one to test against.
@fireborn Yeah, sadly, that thing has been a bit of a fail the way they implemented Android, thought it was a good idea at the time
-
@fireborn Yeah, sadly, that thing has been a bit of a fail the way they implemented Android, thought it was a good idea at the time
@davetaylor2112 It's not as bad as the braille note touch.
-
@davetaylor2112 It's not as bad as the braille note touch.
@fireborn Nope, they definitely did a better job than that. I hear the BrailleNote Evolve is much better, but that's full Windows
-
@fireborn Nope, they definitely did a better job than that. I hear the BrailleNote Evolve is much better, but that's full Windows
@davetaylor2112 Again, haven't tried it, but not much could be worse than the touch.
-
@davetaylor2112 Again, haven't tried it, but not much could be worse than the touch.
@fireborn Agreed, I thought that literally everything about that was a mistake
-
P pixelate@tweesecake.social shared this topic