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.
This commit is contained in:
Jonas Kulla 2014-10-22 04:12:21 +02:00
parent 8e1852a281
commit af8f3a36d2
1 changed files with 1 additions and 1 deletions

View File

@ -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);