Features :
The SDK is a rewrite of many of the default classes, a module with scripting tools and a set of scripting standards. The SDK is aimed at the compatible issues of many scripts fighting over the same methods of the default classes. The SDK breaks up these methods into many other methods targeted directly at one function. The hope is that by breaking up these methods you limit the need to over write then whole method and can Alias just the area or function you want to add to or edit.
The SDK should NOT be edited and redistribute without contacting a member of the SDK Team. Edits to the SDK may cause massive capability errors and would defeat what we are trying to do here.
When you post a script you should state if it's SDK compatible and what version it's compatible with. A member of the SDK Team will review it and flag it to receive a SDK logo signifying that it is indeed SDK compatible. Questions regarding the SDK or making scripts SDK compatible should be directed to a SDK team Member.
SDK scripts are in NO way better then non SDK scripts. A higher level of time and effort has however been invested into them by the scripter to hopefully limit compatibly issues.
The SDK has changed a lot in this upgrade. The first change is the separation of the SDK. The SDK has been separated into 4 parts now, allowing users and scripters more options.
Part I is for everyone. Adding the SDK Part I will not destroy your project. Instead, Part I is focused on the SDK module and the additional SDK::Scene_Base class (see below). Part I also includes standard fixes such as the script call freeze and a help prevention of windows trying to dispose multiple times. There is also a method created to test if a page's conditions have been fully reached.
After Part I, you only need to include the parts for scripts that require additional parts. If a script requires Part II, but not III or IV, you do not need to put them in your project. Same goes for Part III. However, if a script Requires Part IV, you must also have the Part III, as Part IV uses methods created in Part III. It is advised to just have all parts, but not recommended unless otherwise specified.
Part II is specified for the Game, Sprite & Spriteset classes. Part III is the conversion of all Scene classes to use the SDK::Scene_Base class. Part IV is the re modification of how commands work. The target here : adding commands in scenes made easy.
The SDK::Scene_Base class can and should be used as the parent class of all classes. It : provides a structure to the main method ; auto-update and dispose objects. To read more about it, check the SDK Documentation.
Part IV's separation of scene command input uses a sub-module in the SDK, Scene_Commands. All scenes should have a sub-module for anything that uses Window_Command, or Window_HorizCommand. It is not required, just highly recommended.
The Upgrade Patch: The upgrade patch is an attempt to help people switch from the 1.5 version to the 2.0 with a limit on the troubles. It is not required, but will not affect you game at all. Nothing is guaranteed to make every 1.5 script work with the 2.0, but it is an attempt.
Near Fantastica
Fuso
Wachunga
Prexus
Trickster
SephirothSpawn
What is the SDK?
Dose this goes above main?
When you are installing the SDK place it above the all your other scripts but below the default scripts.
Will my old scripts still work?
If your scripts work now then they should work after you install the SDK although that is not 100% tested
---
Do the following :
- Open the 'The RMXP SDK Complete.txt' document
- Copy and paste all the text in the document in your script editor above all other scripts.
- Edit this line : Include_SDK_Parts = [2, 3, 4, 5] to include what parts of the SDK you with to include, with the part 5 being the path.
Scripts :
The Complete SDK
And in individual segments:
Everyone please only post in this thread if you need help, have a question, or suggestion on SDK, If you have a question about one or more of the scripts Near's Test Bed then use the RGSS Support Forum