hedge-dev / hedge-dev/UnleashedRecomp
Accessibility Options
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5.1k
- Forks
- 421
- PR merge metrics
- No merged PRs in 30d
Description
In recent HD games, a notable accessibility toggle that always peaks my eye makes it so any QTE that requires the repeated tapping of a single button to succeed in an action now boils down to just holding that same button down to achieve the same action, achieving the perfect mash. On top of wasting less time for casual runs and speedruns, this makes it better for people with hand or arm-related disabilities that can not do such an action as easily as myself.
Also, there should be a "Hold" prompt or a different animation for the buttons to imply that you need to hold the button and not tap it. I believe that regardless of the option chosen, The Last of Us has rotating lines around the button, regardless of whether you are tapping or holding the button.
Notable and "recent" examples I can think of games that have this include The Last of Us franchise on PS5 and 2019's Star Wars Jedi: Fallen Order.
The Warehog has these mashing-style QTEs for things like activating mandatory levers, and I think it would be excellent in general for Unleashed Recomp to receive an Accessibility tab, along with something like "Hold or Toggle to Run" as the Werehog.
This would be a perfect first addition to an accessibility tab that Unleashed Recomp should have. Having another option to relegate it to only a single press would be even better, but one thing at a time.
While I do not have a health issue that would make this option just for me, and this is a niche feature, for sure, I think it would be great to streamline the Werehog gameplay even more.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the Werehog mashing-style QTEs and the existing input or settings code, then determine how an accessibility tab could expose hold or toggle behavior. Done should cover the requested QTE interaction and a clear Hold prompt or animation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100