Migration path
Start by mapping existing OGP concepts to GSP: panel, agents, remote servers, game templates, modules, files, users, and Workshop content. Then verify current GSP behavior where the fork notes identify differences.
About the OGP fork
The project keeps attribution clear while documenting which inherited behaviors still apply and which GSP-specific paths should guide new installations and migrations.
GSP inherits the panel-and-agent architecture, module-based panel layout, XML-driven game templates, installer metadata, command templates, and server lifecycle concepts that made OGP familiar to operators.
Start by mapping existing OGP concepts to GSP: panel, agents, remote servers, game templates, modules, files, users, and Workshop content. Then verify current GSP behavior where the fork notes identify differences.
The local wiki still calls for deeper review of older XML tag compatibility, module-level divergence, and database-level differences that may be intentional or historical.