From a1e716b60a7cca9306ff6deef108b807517df366 Mon Sep 17 00:00:00 2001 From: san7890 Date: Tue, 2 Aug 2022 07:31:38 -0600 Subject: [PATCH] Blargedy Blarg Blarg Blarg - Word Filter Error Fix (#68905) Blargedy Blarg Blarg Blarg - Word Filter Fix Hey there, Apparently, even after five days of thinking about the JSON_DECODE issue we had going from rust-g 1.0.1 to 1.0.2, I forgot to check our own code. I think I fudged something where I was using the global proc instead of the actual RUSTG define, so you would always get back an encoded JSON array, which would result in passing a null for content (based on what was seen on production), etc. The failure condition we were seeing is that no matter how perfect the word filter was, you would still crash to get this issue: With a few "null spaces" after that message. So, I'm pretty sure this is the issue since I'm not seeing anything in my config_error.log with this change added. Whoops. --- code/controllers/configuration/configuration.dm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/controllers/configuration/configuration.dm b/code/controllers/configuration/configuration.dm index ea6bcdfb6f8..33aeef41ebd 100644 --- a/code/controllers/configuration/configuration.dm +++ b/code/controllers/configuration/configuration.dm @@ -379,7 +379,7 @@ Example config: return log_config("Loading config file word_filter.toml...") - var/list/result = rustg_read_toml_file("[directory]/word_filter.toml") + var/list/result = rustg_raw_read_toml_file("[directory]/word_filter.toml") if(!result["success"]) var/message = "The word filter is not configured correctly! [result["content"]]" log_config(message)