From 5d98fc327b24df8534b9beb7a5c7da88b0eb63b7 Mon Sep 17 00:00:00 2001
From: tenten8401 <isaacalich8401@gmail.com>
Date: Mon, 20 Nov 2017 09:47:49 -0500
Subject: [PATCH] Workaround for improper boolean handling

Since laravel only takes 1, 0, true, false, "1", and "0" instead of allowing "true" and "false".
---
 database/seeds/eggs/rust/egg-rust.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database/seeds/eggs/rust/egg-rust.json b/database/seeds/eggs/rust/egg-rust.json
index c3d4901f..074b1442 100644
--- a/database/seeds/eggs/rust/egg-rust.json
+++ b/database/seeds/eggs/rust/egg-rust.json
@@ -36,7 +36,7 @@
             "name": "OxideMod",
             "description": "Set whether you want the server to use and auto update OxideMod or not. Valid options are \"1\" for true and \"0\" for false.",
             "env_variable": "OXIDE",
-            "default_value": "false",
+            "default_value": "0",
             "user_viewable": 1,
             "user_editable": 1,
             "rules": "required|boolean"