[BUG] SCRIPT ERROR: Parse Error: Could not resolve external class member "settings".

[ikostan]

Technical Summary:

The game fails to boot in the browser due to a GDScript compilation error in input_remap_button.gd at line 121. The compiler cannot resolve the member settings. This suggests a regression from PR #431 where the reference to the settings provider was either renamed, moved, or the Autoload was not properly updated to reflect the new Resource-based architecture.

Godot Version: (e.g., 4.5 stable)

OS: (e.g., Windows 10 64-bit)

Game Version: v0.9.3

Steps to Reproduce:

#1

1. Start the game.
2. Check browser console.

#2

1. Start the game
2. Open "Key Mapping Options"
3. Select "Keyboard"
4. Verify "menu next" and "menu prev" values

Expected Behavior:

1. No console errors.
2. "menu next": TAB and "menu prev": SHIFT+TAB

Actual Behavior:

1. SCRIPT ERROR: Parse Error: Could not resolve external class member "settings".
   at: GDScript::reload (res://scripts/input_remap_button.gd:121)
2. Unbound values for "menu next" and "menu prev"

Screenshots (if "menu next" and "menu prev" applicable):

Screen #1:

Screen #2:

Additional Context:

What happened:

In input_remap_button.gd at line 121, you are trying to access a property or variable named settings on another object/class, and Godot can't find it. Because input_remap_button.gd failed to compile, it triggered a chain reaction:

• key_mapping.gd failed to compile (because it depends on the button script).
• The ResourceLoader failed to instantiate classes (the Cannot get class '' error).

How to fix:

• Open res://scripts/input_remap_button.gd.
• Go to line 121.
• Check how you are referencing settings.
  • If settings is supposed to be a Singleton (Autoload), ensure it is still named "settings" in your Project Settings -> Autoload tab.
    *If you are accessing it via a variable (e.g., some_object.settings), ensure that some_object is properly typed and that the settings member actually exists in that class.

[ikostan]

1. The Root Cause (The "Smoking Gun")

The most important part of the bug description is the Parse Error. Your logs explicitly state:

• File: res://scripts/input_remap_button.gd
• Line: 121
• Error: Could not resolve external class member "settings"

2. The Dependency Chain

The bug description should note that this is not just a localized error. Because input_remap_button.gd fails to compile:

• res://scripts/key_mapping.gd also fails (it depends on the button script).
• The ResourceLoader eventually returns a null object because the underlying classes are invalid.

3. Proposed Fix/Changes Needed

• Autoload Verification: Ensure there is a Singleton named settings (all lowercase, matching the error) in your Project Settings.
• Type Hinting: If settings is being accessed through a variable, ensure that variable is properly cast or typed so the compiler knows it contains a settings member.
• Resource Compatibility: Since this started after the Resource implementation PR, check if settings was converted from a Node-based Autoload to a Resource-based one. If it was, the way you access it (e.g., Settings.settings vs just Settings) might have changed.

[ikostan]

Based on the logs and files, moving those resources to res://config_resources/ and breaking that circular dependency between the Globals and the GameSettingsResource was the key to stabilizing the engine's compilation process.

By resolving the naming conflict between the folder and the Autoload, we've ensured that Godot can clearly distinguish between the static Settings singleton and the actual filesystem paths.

Summary of the Resolution:

• Namespace Clarity: Renaming the folder to res://config_resources/ stopped the collision with the Settings Autoload.
• Broken Circularity: Removing the Globals logging call from the Resource script allows the resource to compile independently.
• Safe Loading: Updating globals.gd to use the correct path ensured that the @export variable actually finds its data.