You should consider using alias to "hook" those functions instead of overwriting them.
e.g.
#alias the original functionclass<<self;aliasload_game_lglobalsaveload_game;end#override the functiondefself.load_game#call the original functionload_game_lglobalsave#do custom stuffLGlobalSave.loadifLGlobalSave::LOAD_ON_LOADend
The advantage is that if another script also hooks the same functions, it may be possible for the two scripts to co-exist.
Otherwise looks good, I can see a few uses for this script like saving options, achievements etc.
author=coelocanth You should consider using alias to "hook" those functions instead of overwriting them.
e.g.
#alias the original functionclass<<self;aliasload_game_lglobalsaveload_game;end#override the functiondefself.load_game#call the original functionload_game_lglobalsave#do custom stuffLGlobalSave.loadifLGlobalSave::LOAD_ON_LOADend
The advantage is that if another script also hooks the same functions, it may be possible for the two scripts to co-exist.
Otherwise looks good, I can see a few uses for this script like saving options, achievements etc.
Thank you. Its the first script i've written and i'm not very familiar with Ruby.
Ill try aliasing them.
Is it possible to have one file activate a switch, which then in another file it opens a door that was locked before? If so, can I get an explanation on how, I really want to use this if I can.