MultiConnectCloud › Server Deployments
5. What you can change later
| Setting | Can change? | How it applies |
|---|---|---|
| Mode | No | Create a new deployment |
| Game servers (Always ready or On demand) | No | Create a new deployment |
| Platform | No | Create a new deployment |
| SDK App | Not on this form | Change the link from the app on SDK Apps. Running servers get the new key on their next redeploy |
| Deployment Name | Yes, with Update | At once |
| Entry Point File, Start Command, Container Port, Protocols, Health Check Path, Environment Variables | Yes, with Update | A redeploy of the same build, with grace for connected players |
| Grace Period, Scale-Down Grace Period | Yes, with Update | At once, with no redeploy |
| Auto Scaling and thresholds | Yes, with Update | At once |
| Webhook | Yes, with Update or on the Webhooks panel | At once |
| Most running at once, Longest a server may run | Yes, with Update | For game servers started from then on. Running ones keep their limit |
| Worker regions and counts | Yes, with Scale | A scale operation |
| Combined regions | Yes, with Scale | A scale operation |
| Master regions | No | Update and Scale show masters read-only. Create a new deployment to run masters elsewhere |
| Plans | Yes, with Update on the Plans panel | A plan change, with grace for connected players |
| Build | Yes, with Update and Upload new build | A redeploy |
If the deployment is stopped or has never finished its first deploy, changed settings are saved and take effect the next time it is deployed.

