Troubleshooting

Use this page for practical first-pass triage.

XML Problems

if a game config fails to load, inspect Panel/Panel/modules/config_games/schema_server_config.xml
run the XML validation script before assuming the runtime parser is wrong
compare the failing template with a known-good current template such as Arma 3 or Garry's Mod
verify element order as well as tag names

Workshop Problems

if Workshop config copy validation fails, verify the source identifier is only a safe XML filename from the Workshop config set
if the module complains about a missing config file, verify path normalization and that the file remains inside the expected game_configs directory
if blank File Path still triggers config-file editing against a game home path, that is a bug
if Workshop behavior differs between games, compare both the dedicated Workshop XML profile and the related game template's workshop_support block

Installation Problems

run check.php and clear every blocker before retrying install.php
verify required PHP extensions, PEAR, and shell utilities are installed
verify writable directories and includes/config.inc.php
verify Apache rewrite support if Apache is the active web server

Remote And Agent Problems

confirm the remote agent is reachable and registered correctly
confirm the panel-side remote library can perform the expected action
confirm the requested operation still belongs to the currently supported module workflow

Legacy Behavior Questions

If current behavior is unclear, older OGP behavior may still explain why a workflow exists, but current GSP source and current GSP templates should be treated as authoritative.