satisfactorymodding / satisfactorymodding/SatisfactoryModLoader
Improved Wwise and version control handling
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 344
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
https://discord.com/channels/555424930502541343/562722670974599227/1345423198128312323
Per-mod Wwise project?
We want to be able to provide stubs of the base game Wwise events, but without making tons of conflicts on peoples' projects when we push new stubs
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
Start with the linked Discord discussion, then locate the current handling of Wwise projects and base-game event stubs in the repository. Define how per-mod projects should receive new stubs without version-control conflicts; done requires an agreed design and verified behavior for updates across existing mod projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, unreal-engine
- Domain
- game-dev, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100