bcirpggithubmirror/Phase2/Godot ===(Game Code)===/MergedDemo/Doug/bcirpg_mergedDemo_20220911A/README.txt
MacDugRPG 2f51e2228a Continued module updates:
The following changes are included in this update:
	-TestingFiles subdirectory replaced with the _userFiles subdirectory. As discussed in meeting, this is to house what's been previously moved to OS-dependent user directory.
	-user paths are removed for a the res://_userFiles location throughout.
	-options are now being both dynamically loaded and linking from the JSON.
	-The test JSON adds several (silly) options to test having more than 3 and larger test outputs.
	-Attempted to incorporate Luke's updates from today in this update.
	-NOTE: cleanup/refactor is definitely needed, but got this working today. The CommandProcessor, for example can likely be removed in the next update
2022-09-11 16:34:30 -04:00

46 lines
1.6 KiB
Plaintext

****************************
README.TXT:
****************************
Author: Doug McCord
Date: 27-Feb-2022
****************************
Intro notes:
This menu was stripped down from the bigger game and settings testing
I was doing -- so there's a decent chance yet of something broken --
please let me know if you encounter anything that's not linking up as
desired. Currently there are temp destinations loaded for each of the
menu options -- these are saved as scenes in the screens folder.
Currently almost all the buttons are instances of the same source
button object -- linked to their destination using the 'Next Scene Path'
available in the inspector.
****************************
Project file structure:
Surface Layer:
Default Godot files remain at this level
_toArchive:
Directory to serve as reference-only; precursor to trash
assets:
Images, fonts, themes and styles (TRES text resource data files). Note that all fonts and styles are defined in
the following themes: ui_controlNode_light_theme.tres and ui_controlNode_dark_theme.tres. Any style changes
should be made in those theme files to assure propagation throughout.
gamePlay:
Scenes and scripts specific to the gameplay section
globalScripts:
For project-wide use, or scripts that are not either:
A. attached to a template scene, intended to go with all instances of that, or
B. unique, scene-specific scripts.
screens:
Planned to include both .tscn scene files and their associated scripts.
userInterface: (note misnomer for text-based game)
Re-useable UI elements and their scripts, such as change-scene, input-response