Preparing a Paid Product Support Ticket

This guide walks through Preparing a Paid Product Support Ticket from preparation through verification, with a rollback path and the checks that matter in a real paid scripts environment.

Before installing

Download the version you are licensed to use, preserve the original archive, back up your current configuration, and identify resources this product replaces.

Install

Upload the complete resource, read the shipped config, add dependencies first, configure required ACEs/integrations, then add the resource to startup in the documented order.

Configure deliberately

Change one feature group at a time. Keep internal department/tag identifiers consistent across Kruiger products. Keep webhook/database/API credentials private.

Acceptance test

Test every documented command/control, authorized and unauthorized permissions, reconnect behavior, multi-player synchronization and a full cold boot.

Updating

Never overwrite your working config blindly. Diff the new default configuration against your version and migrate settings into the new schema.

Document status

Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.