Skip to main content
INTRACT

Server Deployment Methods

INTRACT supports multiple deployment workflows depending on how hands-on a server owner wants to be with customization approvals and server management.

Manual Deployment

Manual Deployment is designed for servers that want full control over clothing ingestion, pack structure, and deployment workflows.

This mode is ideal for communities with:

  • Existing clothing pipelines
  • Internal development teams
  • Custom pack management systems
  • Strict approval requirements

How Manual Deployment Works

Step 1 — Server Packs Remain Unlocked. The server owner chooses not to lock their Pack(s). This allows the server to manually manage Pack structure, asset organization, clothing slot allocation, and naming conventions outside of the automated INTRACT deployment pipeline.

Step 2 — Players Submit Customizations. Players purchase customizable clothing through Tebex and create their designs inside the INTRACT editor. Submitted customizations enter the server's review queue.

Step 3 — Staff Review Submissions. Server staff manually approve / reject submissions, review moderation history, and inspect uploaded and AI-generated assets.

Step 4 — INTRACT Generates The Texture. Once approved, INTRACT generates the finalized player customization texture as a YTD file. The server owner can then download the generated texture directly from the platform.

Step 5 — Server Owner Builds The Pack. At this point, the server owner handles Pack rebuilding, YMT management, YTD insertion, file naming, clothing slot organization, and server deployment. INTRACT is no longer responsible for Pack management during this workflow.

Access To The Pack System During Manual Deployment

Even while using Manual Deployment, server owners still maintain access to the INTRACT Pack system. This allows communities to:

  • Build Packs manually today
  • Transition into automated workflows later
  • Prepare Packs for future deployment automation

Once a server owner decides to lock their Pack(s), those Packs become eligible for the INTRACT automated deployment pipeline.

Important Notes

In Manual Deployment mode:

  • INTRACT does not automatically rebuild Packs
  • INTRACT does not automatically deploy assets
  • INTRACT does not manage final clothing slot assignment

This workflow is intended for servers that prefer to maintain direct control over their clothing infrastructure.

Automated Deployment

Automated Deployment is designed for servers that want a scalable, low-maintenance customization pipeline with minimal manual asset management.

Ideal for:

  • Larger GTA RP communities
  • High-volume customization servers
  • Teams looking to reduce operational overhead
  • Servers scaling player-generated cosmetic systems

How Automated Deployment Works

Step 1 — Players Submit Customizations directly through the INTRACT editor after purchasing through Tebex.

Step 2 — AI Moderation Reviews Assets. Uploaded and AI-generated images are automatically reviewed for NSFW content, hate symbols, copyrighted logos, real-world brands, and offensive imagery. Only approved assets continue.

Step 3 — Approved Assets Are Processed. INTRACT automatically processes the customization into the server's managed Pack system: YMT structuring, YTD organization, clothing asset formatting, gender separation, Pack maintenance.

Step 4 — Server Connection Setup. To enable Automated Deployment, the server owner connects their server to INTRACT using:

  • Server IP address
  • Secure API secret key

This lets INTRACT securely communicate with and maintain the server's clothing Packs.

Step 5 — Automatic Pack Delivery. INTRACT automatically delivers and maintains incoming clothing Packs directly on the server. The platform handles Pack structure, asset organization, YMT formatting, incoming customization updates, and clothing asset synchronization.

Automated Pack Management

With Automated Deployment enabled, INTRACT becomes the system responsible for managing and tracking the server's Pack structure. It automatically structures YMT files, organizes clothing assets, maintains Pack formatting, tracks Pack contents, and handles incoming customization updates.

Important Sync Warning

When using Automated Deployment, INTRACT must remain the source of truth for the Pack(s) it manages. If a server owner manually inserts new model files, additional YTDs, external clothing assets, or untracked Pack modifications directly into an INTRACT-managed Pack, the platform will not be aware of those changes.

This can cause Packs to become out of sync, structurally inconsistent, or unstable during future updates.

Recommended Best Practice

Servers using Automated Deployment should avoid manually modifying INTRACT-managed Packs, Pack file structures, asset allocations, or clothing slot organization outside of the INTRACT platform.

Why Servers Use Automated Deployment

Reduce manual workload, scale customization systems, simplify Pack maintenance, reduce clothing management complexity, and support larger volumes of player-created cosmetics with significantly less operational overhead.

Hybrid Deployment

Hybrid Deployment combines elements of both Manual and Automated workflows for servers that want flexibility in how they moderate submissions, manage Packs, deploy assets, and control synchronization.

Scenario 1 — Manual Approval + Automated Deployment (Locked Packs)

  • Server staff manually approve or reject player submissions
  • Locked Pack(s) are managed by INTRACT
  • Approved assets are automatically deployed into the server

Best for servers that want human moderation oversight, still want automated deployment, need scalable customization pipelines, and want minimal Pack management overhead.

Scenario 2 — Automated Moderation + Manual Pack Building (Unlocked Packs)

  • AI moderation handles approvals
  • INTRACT generates finalized YTD textures
  • The server owner manually builds and deploys Packs

In this workflow, YDD files are not provided — Packs must be locked before YDD support becomes available. INTRACT does not automatically deploy the Pack.

Best for servers that want to manually assign assets to players, already maintain custom Pack workflows, need direct control over deployment timing, and prefer manual slot organization.

Scenario 3 — Fully Managed Packs + Manual ZIP Deployment (Locked Packs)

  • INTRACT fully manages the Pack(s)
  • Automated moderation is enabled
  • Server / INTRACT sync is not established

Instead of direct deployment, the server owner manually downloads Pack ZIP files for deployment.

How it works: INTRACT continuously maintains the Pack contents (YMT, YTD, YDD, formatting, sync). The server owner can download the latest Packs as ZIP files at any time directly from the platform, then manually upload to the server, replace previous Pack versions, and handle restart / redeployment workflows.

Best for servers that want INTRACT-managed Packs, prefer manual deployment control, do not want direct server synchronization enabled, and need downloadable Pack snapshots.

Why Servers Use Hybrid Deployment

Hybrid Deployment gives communities flexibility to gradually adopt automation while maintaining operational control where needed — mixing manual and automated workflows, reducing workload incrementally, maintaining moderation oversight, and transitioning toward scalable deployment systems over time without being locked into a single operational model.