TASEmulators / TASEmulators/BizHawk
Enhancement: NEW SOCD option suggestion.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
It seems that all three current choices for SOCD resolution allow tricks that are stupidly difficult on a controller that doesn't allow SOCD.
None allows glitches in games that don't properly handle SOCD.
Priority allows frame perfect reversals easily, which is often used to keep dash momentum when reversing.
forbid has it's own tricks, which i will list some of.
- easy taps. press forward, tap back. voila! instant dash.
- silly fast shoryukens.
- a bajillion other SOCD shortcuts that the hitbox website advertises.
I propose a SOCD resolution method that combines priority and forbid at the same time.
If you press opposite directions, it goes to neutral, but the one that was pressed first is disabled until it's released, just like with priority.
This removes all the stupid SOCD cleaner tricks when not using a controller that does it in hardware. :)
Contributor guide
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
Start by locating BizHawk's existing SOCD resolution options and the input-handling entry point that applies them. Compare their current behavior with the proposed combined mode, then define tests or reproducible input sequences showing that opposing directions become neutral and the first direction remains disabled until release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100