This guide documents running a Rust server on GameHostCloud from deployment through wipe day. Map size and seed are chosen before launch because changing either forces a map wipe; a worldsize of 3000 to 3500 suits most populations, and larger maps mainly increase RAM use and load times. The modding framework is installed from the Plugins tab, using either Oxide/uMod for the largest plugin ecosystem or Carbon for better performance, never both at once, with plugin configuration files stored under the oxide config directory and editable in the File Manager. Key server variables include maxplayers, worldsize, seed, saveinterval, decay scale and the PvE toggle. Rust uses UDP 28015 for the game, UDP 28016 for queries and TCP 28016 for WebRCON, and the browser console is a full WebRCON client. Wipes are scheduled from the dashboard, with forced map wipes on the first Thursday of each month following the Facepunch update cycle. Performance guidance covers memory sizing, entity-spawning plugins, save interval tuning and reading server overload warnings. Troubleshooting covers server browser visibility, Steam authentication kicks, Oxide plugin compile errors and post-wipe load spikes.