From af8f3a36d26532d18015a849b7add6256e602a49 Mon Sep 17 00:00:00 2001
From: Jonas Kulla <Nyocurio@gmail.com>
Date: Wed, 22 Oct 2014 04:12:21 +0200
Subject: [PATCH] MRI: Move former 'System' module into 'MKXP' module

This breaks script compatibility.

'System' is way too generic of a name to reserve for mkxp use,
and I have already seen at least one occurance in the wild of
it being used by user scripts.

Ideally, all mkxp RGSS extensions would be moved under this
module, but I feel like the core modules (Input, Graphics etc)
are more safe as users are hesitant to directly extend these.
---
 binding-mri/binding-mri.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/binding-mri/binding-mri.cpp b/binding-mri/binding-mri.cpp
index e8c957a..39cc2b6 100644
--- a/binding-mri/binding-mri.cpp
+++ b/binding-mri/binding-mri.cpp
@@ -139,7 +139,7 @@ static void mriBindingInit()
 	else
 		assert(!"unreachable");
 
-	VALUE mod = rb_define_module("System");
+	VALUE mod = rb_define_module("MKXP");
 	_rb_define_module_function(mod, "data_directory", mkxpDataDirectory);
 	_rb_define_module_function(mod, "puts", mkxpPuts);
 	_rb_define_module_function(mod, "raw_key_states", mkxpRawKeyStates);