godotengine / godotengine/godot

@icon annotation for custom resources not working with custom extensions

Open
#94,964 2 comments 1 reaction 0 assignees View on GitHub
bug confirmed topic:core topic:editor topic:gdextension topic:gdscript
Dominant language
C++
Stars
117k
Forks
26.8k
PR merge metrics
PR metrics pending

Description

### Tested versions

- 4.3 rc1 (Windows 11)

### System information

Godot v4.3.rc1 - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Ti (NVIDIA; 32.0.15.6070) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)

### Issue description

When using @ icon annotation to set an icon for a custom resource, it does not show in the editor's filesystem if the resource has a custom extension (not .tres)

### Steps to reproduce

1. Open MRP.
2. Open FileSystem.
3. Open the res_1.new file.
4. Notice the icon loads correctly in the inspector, but not the FileSystem.

I attached a screenshot too.
![image](https://github.com/user-attachments/assets/6f5fa18d-ecfd-407f-b59e-9a12542aa222)

### Minimal reproduction project (MRP)

[icon-extension-mrp.zip](https://github.com/user-attachments/files/16433782/icon-extension-mrp.zip)

Contributor guide

Open the contributing guide

Research direction

Open the attached icon-extension-mrp.zip and reproduce the mismatch by checking res_1.new in the editor's FileSystem and Inspector. Start by tracing how the FileSystem displays custom resource icons versus how the Inspector resolves the @icon annotation. Done means the annotated icon appears for custom-resource files with non-.tres extensions, while existing Inspector behavior remains correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
godot
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.