Hide/Lock Custom Properties created via Custom Types Editor
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
### Is your feature request related to a problem? Please describe.
In the project I'm a part of, as the programmer, I am responsible for setting up custom types that will be exported into Godot Nodes, for that reason, I need to set up certain custom properties into my custom types that contain information about what script the object should load when converted into Godot node, what node class the object should be converted to ect. And I don't want map designers who don't understand programming or YATI Plugin stuff to break stuff by changing properties they are not supposed to modify.
### Describe the solution you'd like.
Some option that allows me to set these custom properties to "read-only" and maybe hide them from the Custom Properties tab on the map editor.
### Describe alternatives you've considered.
_No response_
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 in the Custom Types Editor and Custom Properties tab, reviewing how custom properties are currently configured and exposed in the map editor. The issue names no files or tests, so first identify the relevant editor entry points and discuss the read-only and hidden behaviors. Done means custom properties can be protected from map designers while remaining usable for Godot Node export.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, godot
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100