satisfactorymodding / satisfactorymodding/SatisfactoryModLoader
No error message produced when 2 chat commands are registered with the same `CommandName`
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 344
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
To reproduce, have the same mod register 2 chat commands with the same CommandName, ex. respawn. logs will look like this:
[2025.11.03-22.35.08:016][ 0]LogChatCommand: Display: Registered chat command CoffeeCupStudiosMod01:beadmin
[2025.11.03-22.35.08:016][ 0]LogChatCommand: Display: Registered chat command CoffeeCupStudiosMod01:kickme
[2025.11.03-22.35.08:016][ 0]LogChatCommand: Display: Registered chat command CoffeeCupStudiosMod01:safezone
[2025.11.03-22.35.08:016][ 0]LogChatCommand: Display: Registered chat command CoffeeCupStudiosMod01:cart
[2025.11.03-22.35.08:016][ 0]LogChatCommand: Display: Registered chat command CoffeeCupStudiosMod01:kick
[2025.11.03-22.35.08:016][ 0]LogChatCommand: Display: Registered chat command CoffeeCupStudiosMod01:respawn
Only 1 of the commands will be registered.
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 from the chat command registration path and reproduce the duplicate CommandName case using the respawn example. Trace why only one command is registered and verify that duplicate registrations now produce an error log while preserving the existing registration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, unreal-engine
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100