An open-world sandbox with no built-in goal: write your game mode in Lua and let your Onset server wait for your community in İstanbul.

Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.







Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Bronze 4GB | Recommended: roleplay and freeroam, most serversOfficial minimum is 100 MB of RAM; this plan carries large roleplay frameworks too. | 4 vCore Ryzen 9950X · 4 GB DDR5 6000MHz · 50 GB NVMe SSD Samsung 990 PRO | ₺240.00/mo |
| Silver 6GB | Very heavy package stacksHeadroom for big communities running dozens of packages and lots of NPCs for days on end. | 4 vCore Ryzen 9950X · 6 GB DDR5 6000MHz · 60 GB NVMe SSD Samsung 990 PRO | ₺345.00/mo |
| Gold 8GB | Not needed for OnsetMore memory won't speed up a slow Lua script; optimize the package code first. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | Not recommended for OnsetAn Onset server uses only a small fraction of this capacity. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | Not recommended for OnsetThis memory sits idle; the bottleneck is always script CPU time. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | Not recommended for OnsetSix vCores on paper, but Lua scripts run mostly on a single core. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | Not recommended for OnsetSized for heavily modded survival games; Onset has no use for it. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
On Onset, scripts weigh a server down far more than memory does, so a fast single core, quick storage and direct file access are what count.
Your server-side Lua runs on every event, and a heavy roleplay framework with slow loops turns into lag. The Ryzen 9 9950X's high clock speed absorbs that load.
Each package lives in its own folder with an index.lua or package.json. Upload it to packages and enable it in the config, or drop it in autostart to load on every boot.
server_config.json holds the core settings: server name, maxplayers, password, timeout, iplimit, vac, masterlist, plugins and the package list. Edit it in the file manager and restart.
Player, vehicle, object, NPC, pickup, door and text3d pools each get their own distance and update rate. On busy roleplay maps, this is where you balance bandwidth against smoothness.
When players join, they download client scripts and files from your server's file port. NVMe storage speeds up that first download, and changed files are resent based on their checksum.
Package won't load, or server missing from the list? Reach our Turkish-speaking support team any hour by ticket, live chat, Discord, WhatsApp or phone.
Onset server hosting at TheCrewHost starts at $6.00 a month (₺240.00) and gets you a server installed from Blue Mountains' official OnsetServer application, running on Ryzen 9 9950X hardware with NVMe SSD storage in İstanbul. Onset has no predefined goals: roleplay, cops and robbers or classic freeroam are all things you build with Lua scripting. Upload your packages to the packages folder over SFTP, choose which ones load in server_config.json, and set everything from the player cap to voice chat and entity stream distances in that same file.
Onset is an open-world sandbox from Blue Mountains, built from the ground up for multiplayer and shipped without a built-in objective. Whatever you load onto the server is the game: with Lua scripting functions you can build a roleplay city, a cops-and-robbers chase, racing events or a classic freeroam mode, or run game modes written by the community.
You should know where Onset stands. The game has been in Early Access on Steam since December 2019, and it hasn't had a developer update in several years. It is still sold on Steam, and OnsetServer still installs through SteamCMD with an anonymous login and runs fine, but don't expect new official engine features.
That makes an Onset server a best fit for communities that already know the game and for developers who enjoy writing their own modes in Lua. A frozen engine version also has an upside: no surprise engine update is going to break your roleplay framework. Players need to own Onset on Steam and play on the Windows client.
Very little. Onset's official developer documentation lists the server's minimum requirements as 100 MB of RAM and 50 MB of disk space. Even Bronze 4GB is far more than an empty Onset server needs, and we would rather say that plainly.
Your packages decide memory use. A large roleplay framework that spawns lots of NPCs, vehicles and objects and keeps inventories and an economy in memory will raise it, but it rarely comes close to the limits of Bronze. The real bottleneck is the CPU: inefficient loops and timers that fire too often in your Lua scripts are what wear a server down. Strong single-core speed pays off directly there.
We only recommend Silver 6GB for big roleplay communities running many heavy packages at once and leaving the server up for days between restarts. Gold and above are wasted on Onset; extra memory won't make a slow Lua script faster. Optimizing package code always beats upgrading the plan.
An Onset server is made entirely of packages. Each package sits in its own folder and contains at least an index.lua or a package.json. package.json can list author, version, server_scripts, client_scripts, shared_scripts and files. Shared scripts run on both the server and the client, and you tell the two apart with IsServer() and IsClient().
Upload a package to the packages folder over SFTP or with the file manager, then add it to the packages list in server_config.json. Packages you want running on every boot can simply go into the autostart folder. Frameworks that need a database use the mariadb plugin from the plugins list, which connects to a MariaDB or MySQL database you provide. If you want the database on its own machine, a VDS is a good home for it.
For custom map pieces, models or vehicles, Onset supports loading .pak files on the client with the LoadPak function. Add those files to your package's files list and players download them automatically when they join.
servername is the name in the server list, and it supports tags such as [b], [i], [u] and [c=...] for color. gamemode tells players what happens on your server, and website_url points them to your community page. maxplayers sets the player cap and password sets a password; leave it empty for a public server. With masterlist set to true, the server shows up in the public list.
timeout decides how many milliseconds an unresponsive player gets before being dropped; the docs recommend 10000 to 20000. iplimit caps connections from a single IP, and vac turns on Valve Anti-Cheat. voice switches voice chat on or off, voice_sample_rate picks quality between 8000 and 48000 Hz, and voice_spatialization makes voices fade with distance.
At the end of the file are separate entity pools for players, voice, vehicles, objects, NPCs, pickups, doors and text3d. Each pool's distance and update_rate control how far away those entities are visible and how often they update. In a crowded city, trimming those distances a little eases the load on both the server and your players' connections.
With masterlist enabled, players find your server's name in Onset's server list and join, entering the password if there is one. Onset uses three ports: UDP 7777 for the game, UDP 7776 for server queries and TCP 7775 for client file downloads. The query port is the game port minus one and the file port is the game port minus two; the values assigned to your server are shown in the panel.
On first join, the player's client downloads the client scripts and files from your packages and caches them in %LocalAppData%\Onset\Saved\ServerContent. When a file changes on the server, its checksum changes and only that file is downloaded again. Each package is limited to 1024 client files, and large .pak files make that first join longer.
Because the machine is in İstanbul, roleplayers in Türkiye drive, talk and trade with low latency, and players from Europe and the Middle East join comfortably as well. If players can't see your server in the list, check the masterlist value and look for package errors in the console.
An Onset server is extremely light, and the smallest plan covers most roleplay and freeroam servers. Choose Silver 6GB only if you plan a very heavy package stack.
OnsetServer installs automatically once payment clears. Sign in at gamepanel.hostingmerkezi.net to reach the console, the file manager, backups and your SFTP login.
Fill in servername, gamemode, maxplayers, password and masterlist, then tune voice chat and entity pool distances to the size of your community.
Send package folders to the packages directory over SFTP and add them to the packages list; put the ones that should always run into autostart.
Restart the server and confirm every package loads cleanly. Lua errors show up in the console with their line numbers.
Players find your name in Onset's server list and download package files on first join. Post the server name and rules on Discord.
What people ask before starting an Onset server: the game's current state, packages, ports and how few resources it really needs.
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news