godotengine / godotengine/godot
Automatic build profile generation disables `InputMap` class
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
Tested versions
Reproducible in: 4.3-dev-4, 4.2 branch, 4.2.1-sable
System information
Godot v4.2.1.stable - Debian GNU/Linux testing (gcc12) - Wayland - GLES3 (Compatibility)
Issue description
Automatic build profile generation disables InputMap class. Which should persist almost always especially when user definded custom actions. It can be difficult to determine if user use the action because it can require script parsing (which is also isn't possible for native extensions...) but if user defined custom action it should be easy to detect it
Because of #89477 it looks like is a very systematic problem. I guess it only makes shallow check of used nodes by just traversing all the scenes graphs and doesn't look anywhere else.... ¯\_(ツ)_/¯
Steps to reproduce
- Create a new project
- Crete one scene (maybe not necessary)
Project->Customize Engine Build Configuration...->Detect from ProjectSave As- Open the saved profile with editor and search for
InputMapinside disabled_classes
Minimal reproduction project (MRP)
N/A
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
Reproduce the issue through Project > Customize Engine Build Configuration > Detect from Project, then save the profile and inspect disabled_classes for InputMap. Trace the automatic profile generation from that workflow and verify that InputMap remains enabled, including when the project defines custom actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100