Jump to content

Updating & Rolling Back OpenMod Plugins


- Alex -

Recommended Posts

  • Community Leader

  • Member ID:  1
  • Group:  Community Leader
  • Followers:  11
  • Topic Count:  211
  • Topics Per Day:  0.06
  • Content Count:  508
  • Content Per Day:  0.15
  • Reputation:   36
  • Achievement Points:  4808
  • Solved Content:  0
  • Days Won:  36
  • Joined:  07/11/17
  • Status:  Online
  • Last Seen:  
  • Device:  Windows

Updating & Rolling Back OpenMod Plugins
Production-Safe Upgrade Workflow
GGU Public Technical Knowledge Base

Public Knowledge Base:
This article is written for both GGU administrators and the wider server-hosting community. General instructions are platform-neutral where possible; GGU-specific practices are identified separately.

 

Applies To

  • OpenMod administrators

 

Prerequisites

  • A currently working plugin installation
  • Access to backup/restore mechanisms

 

What You’ll Accomplish

Upgrade OpenMod plugins with a known rollback path and validate the full runtime state.

 

Why Rollback Planning Matters

Plugin updates can change binaries, configuration, dependencies, database schemas, or persisted data. A safe update has a known recovery point before the first production change is made.

 

Before Updating

  • Record the currently deployed plugin version.
  • Back up plugin configuration.
  • Back up plugin-owned data/database where applicable.
  • Read release notes.
  • Confirm dependency changes.
  • Know where the previous binary/package can be restored from.

 

Update

  1. Install/replace the new version.
  2. Reload OpenMod as required.
  3. Watch the complete load sequence.
  4. Verify the plugin's main commands/features.
  5. Verify permissions.
  6. Verify persisted data.
  7. Keep the old version until the new one is accepted.

 

Rollback Decision

Rollback when the update creates a production-impacting failure that cannot be safely corrected in the maintenance window. Do not continue stacking speculative changes merely because an update is 'supposed' to work.

 

Rollback Limits

Important:
If an update performed an irreversible or forward-only database/data migration, restoring only the previous DLL may make the situation worse. Restore compatible data/configuration as well.

 

GGU Implementation Notes

GGU should prefer versioned release artifacts from Gitea/CI so the exact prior build is recoverable. Record the deployed version and rollback point with material production changes.

 

Upstream References

 

Golden Gamers United — Public Technical Knowledge Base
General guidance first. GGU implementation details second.

Alex Thunderhunter

Alex — Founder & Systems Architect

Building the community, one server at a time.

Community Leader
Link to comment
Share on other sites


  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.