Calinou
commented
2 years ago Problem 3: only gdscript and shaders are supported. This seems to be a general limitation by Godot, as many games also come with .json, .csv or other files (e.g. translations) but I am unable to search across them.
You can change the file extensions that can be searched in the Project Settings.
To avoid the need for this setting, I suppose we could make Godot search in all resource files that are not binary (and exclude .tscn), but detecting this can take some work.
bend-n
EricEzaM
bitbrain
Describe the project you are working on
I am working on an Untitled Single-Player 2D RPG where an adventurer explores a giant mountain area (project name: cave). The game consists of procedurally generated levels and custom built levels. All ported over to Godot 4.0! It comes with a lot of files that I am going to search (and replace) across when required:
This became especially apparent when upgrading to Godot 4.
Describe the problem or limitation you are having in your project
After working on my game for almost 2.5 years I have a lot of files. Searching across all the files becomes cumbersome as it involves the following steps:
click on the Script tab (search not available in 2D/3D node view)
Press CTRL+SHIFT+F to open the "Search in files..." dialog and enter search term with a typo
It shows 0 results and I have to repeat the process
There are three problems for me with this approach:
Problem 1: too many steps to search what I want. When I am currently in a node somewhere I always have to click into the Script tab first to search across files.
Problem 2: search is not responsive enough. In IDEs such as IntelliJ it is possible to search and get "realtime" results for occurences. In Godot it is quite cumbersome to search because on typos or further searches I have to repeat the above steps.
Problem 3: only gdscript and shaders are supported. This seems to be a general limitation by Godot, as many games also come with .json, .csv or other files (e.g. translations) but I am unable to search across them.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
From anywhere within Godot Engine, pressing CTRL+SHIFT+R to open a dialog like this:
Once the user starts typing a scrollable list of results appears. Clicking on any result will switch the Godot view to the Script tab and open the file and jump to the affected line.
Optionally, the user can select a file mask (perhaps dropdown or cleartext, e.g. *.txt) to search across other files.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Not really. This is a usability feature that would save myself a lot of frustration long-term.
Is there a reason why this should be core and not an add-on in the asset library?
Most of the functionality described here is already Core but not streamlined from a UX perspective. This proposal aims to change that. The only optional functionality could be the filemask as non-Godot files are currently not really supported within the Godot editor.