Noob question: SDK and non sdk compatibility

[Daxis]

Okay, I can't script, I'm just trying to figure something out.

I heard, probably incorrectly, that SDK doesn't use aliasing or something, completely writes over them, that's why scripts that use aliasing doesn't work. Isn't there some way that you simply create a script that rewrites everything again while retain SDK features, leave a section for non SDK scripts, then activate SDK again?

Example:

==RMXP scripts==
==SDK==
==SDK scripts==
==SDK/non SDK compatibility script start==
==Non SDK scripts==
==SDK/non SDK compatibility script end==
Main

This is probably a waste of forum space, right?

 

[Brewmeister]

Not really a waste. Many people have struggled with implementing both SDK & non-SDK scripts in their game.

the problem with your concept is the SDK steps on (overwrites) many of the default methods above it.
If your compatibility scipt then overwrites those methods again, the SDK scripts above it would now call the non-SDK methods.

You could completely re-write the SDK so that all the methods are 'overloading' the default methods, forcing backward compatibility.
Lot's of work (I think).

Or, rewrite the SDK so it's completely autonomous, for example using sdk_method_name to define all methods, and changing the calls in the SDK scripts to call the SDK version, allowing non-SDK scripts to revert back to the default methods.

Unless you're really ambitious, I would suggest either modifying your SDK scripts to non-SDK, or modifying your non-SDK scripts to SDK, whichever you have the least of.

Maybe Seph, or someone with more intimate SDK knowledge will chime in here & set us both straight.

Be Well