Editing Locally
Last updated
Last updated
Live config changes can be made locally for development purposes.
When you run with Play-In-Editor, live config settings will be generated for your game session, which can be navigated to from the editor pop-up on the bottom right corner of your screen.
Clicking Open opens an explorer window containing json files of your available live config settings.
Open these files on your text editor of choice and view/amend your settings as necessary. Once the file is saved, your setting changes should be picked up by the PIE client/server within seconds.
Note that any changes you made will not persist between PIE sessions. A new set of config files would be generated every time a new PIE session is started. If you'd like to make changes to your setting that persists, refer to Overriding Defaults. It is highly recommended that you test any changes made to Live Config (i.e. either afterAdding New Settings or Overriding Defaults) on PIE before deploying your world. Any errors on your Live Config setup will result in the following failure pop-up to appear instead, and you can refer to your Editor logs to debug the issue.
When playing in editor, or using non-shipping builds, you can press the ` key to open the console.
From here, the JunoGameData.GetValue [CONFIG_NAME] [VALUE_NAME] allows you to return the current live config value for a given flag. This can be useful to e.g. verify what live config is currently being used, if experimenting with different values.
NOTE that the jlc.[CONFIG_NAME].[VALUE_NAME] console commands are now deprecated, and do not live-update, so may not be an accurate reflection of the game state.
