Tour doesn't work on .NET edition of Godot.

[OmnesPotens]

Indexes for the run_bar_buttons used in the tour should start at run_bar_buttons[1] (the button in the '1' index is for the play button now).

The buttons should look like this:

	var run_bar_buttons = run_bar.find_children("", "Button", true, false)
	run_bar_play_button = run_bar_buttons[1]
	run_bar_pause_button = run_bar_buttons[2]
	run_bar_stop_button = run_bar_buttons[3]
	run_bar_debug_button = run_bar_buttons[4]

[NathanLovato]

Are you using the .NET version of Godot? If so, as mentioned in the README, the tour only works on the Standard version of Godot currently. The buttons should work fine if you use this version.

Note that if someone wants to contribute support for both the .NET and Standard versions of Godot to the framework ( https://github.com/gdquest/godot-tours ) we'll gladly take it. We just won't support it ourselves yet. We're rather waiting for Godot to get a universal editor instead of having two different editions.

[OmnesPotens]

Huh, that's odd. I am using the .NET version of Godot, however I had downloaded and installed the .exe manually. I was able to run the tour but the run_bar_buttons were not indexed properly. After fixing that I was able to proceed beyond the first step.

Out of curiosity, I opted to reinstall the .NET version via Scoop. After reinstalling, attempting to run the tour results in the tour "Updating Scenes..." before crashing.

Edit: I installed the standard version of Godot via Scoop (so godot and godot-mono, aka the standard and .NET versions of Godot are installed side-by-side) and was able to run "mono" godot (godot-mono) > edit the project > run the tour > proceed with the tour using my changes to the run_bar_buttons indexing. So the project is being run by the .NET version of Godot, but is functional

[OmnesPotens]

I suspect there are some libraries/dependencies included with the standard version of Godot, which godot-tours relies on and these libraries/dependencies do not exist in the .NET version of Godot.

[NathanLovato]

I don't think that's the issue. It's most likely just that some parts of the editor UI are slightly different and we'd need to distinguish the versions and have different code to find relevant pieces of UI. Currently, we just don't have the bandwidth to test and maintain an extra edition of Godot each time we make updates to the tour system.

[OmnesPotens]

I understand that there are bandwidth limitations as well as differences in architecture that make supporting standard Godot and .NET Godot variants difficult. I just wanted to show that so long as both versions are installed I am able to run the tour just fine