Support begins before the ticket

Find the rightnext step.

The OutlawCoreStudios Support Center brings launch guidance, service explanations, migration preparation, common answers, and direct contact routes into one place.

Choose the correct route

Help without the department maze.

Use the route that matches where you are in the process. This keeps technical questions, sales planning, and custom project requests from being mixed together.

01

Pre-sales & hosting fit

Questions about game selection, memory, storage, migrations, web plans, expected workloads, or whether a service is a practical match.

Build a hosting request →
02

General company contact

Partnership questions, account concerns, accessibility feedback, policy questions, or other non-project communication.

Open the contact form →
03

Studio project planning

Website design, graphics, FiveM resources, Minecraft plugins or mods, dashboards, integrations, and multi-service builds.

Build a guided project brief →
04

Existing client support

Service-linked tickets, billing history, attachments, priorities, and technical escalation will live inside the dedicated client platform.

Open the client portal →
Before contacting support

Bring context, not credentials.

Useful context helps us understand the issue or request quickly. Sensitive access information should never be placed into a public form.

  • Service or project type and the affected game, site, or platform
  • Exact version, framework, loader, or control panel when relevant
  • The action taken and the result you expected
  • Error messages with secrets, tokens, and private addresses removed
  • Approximate time the issue occurred and whether it can be repeated
Security rule

Never submit passwords, API keys, private tokens, recovery codes, database credentials, or license keys through a public form.

Secure access should only be arranged after the request is accepted and the correct authenticated process is available.

Read the privacy policy →
Popular guidance

Answers built around actual launch work.

Start with these practical resources, then move into the complete knowledge base for more detail.

View all articles
Game Hosting5 min read

How to choose a starting RAM amount for a game server

A practical way to estimate memory without treating player count as the only performance factor.

Read article
FiveM6 min read

Preparing a FiveM server for migration

Organize resources, database exports, configuration files, and licensing details before a host move.

Read article
Minecraft5 min read

Moving a Minecraft world, plugin server, or modpack

What to collect before transferring an existing Minecraft environment to a new service.

Read article
Hosting Basics4 min read

Understanding backups, snapshots, and restore points

Why backup count, retention, frequency, and off-server copies matter more than a single checkbox.

Read article
Public support expectations

What this website can—and cannot—do yet.

Available now

Public guides, configuration planning, quote intake, contact requests, status visibility, policies, and direct pre-launch communication.

Coming with the portal

Authenticated tickets, customer identity, service selection, priorities, replies, attachments, billing context, staff assignment, and complete history.

Emergency handling

No public form should be treated as an emergency alert channel. Active-service incident procedures will be defined when production hosting enters service.

Still planning?

Build the request with us.

Use the advanced hosting configurators or the guided project planner to give the team enough context for a meaningful response.