SRL Archive - MSI Suggestions

Script Wise Structure:
[INDENT]/MSI/
[INDENT]Setup.scar
Globals.scar
Colors.scar
Debug.scar
Walking.scar
Skills.scar
Mainloop.scar
RunMe.scar[/INDENT]

/MSI/Skills/
[INDENT]All functions related to a certain skill are to be put in here[/INDENT]

All those in /Skills/ will be included in Setup.scar[/INDENT]

Setup.scar
Include SRL.
Include Debug.scar , Walking.scar , /skils/ folder, SkillX.scar .
All constants that are used in more than one file should be placed here.
Should have a SetupMSI procedure inside.

Debug.scar
Will receive information from variables and constants already included in Setup.scar ;
Will use a custom type to store as much information as possible about each player without affecting script management.
Progress Report and Player Report will be done here.
A Simple proggie and player report could be done with SRL's reports.scar, and a full detail proggie could be saved to file.
procedure MSIDebug should also be in here.

Walking.scar
All walks will be simple.
Bank - > Place, Place - > Bank, no Place - > Place.
Constants will be used for Cities and for places (inside the cities)
Any object interacting (opening doors, etc) and walking off the Main Map (dungeon walk, inside essence mine, etc) will be handled in the seperate skill files.
Recentering funcs/procs should be in here as well.
Should also be able to detect location where it currently is.
If lost should be able to go to closest location.

SkillX.scar
Skill's mainloops.
eg. Procedure Loop_Mine(UntilLevel, Time: integer);


Mainloop.scar
Include Setup.scar .
This is where all the AI choosing of what to do will be.

RunMe.scar
Include Mainloop.scar .
Will be the file where you press play and then watch in amazement.

SRLPlayerForm
(at least to start with) will be used for the script, so the user does not have to figure out where the hell to go.


—
Ok, these are the things I had on my mind. PMs will soon enough let us know what City and skills we'll be doing, but we can already start planning the core out. Any ideas / additions to this?

From: Rasta Magician

RunMe.scar
Include Mainloop.scar .
Will be the file where you press play and then watch in amazement.

It will truly be astonishing…
____________________________________________

Why "SkillX" instead of "Skill", cause "Skill" is in SRL? If so, "Skills" looks better in my opinion, but it's up to you. ;)

Doesn't SRL's reports.scar include anything you want? Or at least can easily be added? So we don't really have to have a custom one, do we?

Do you think we should have a script in /MSI/SkillX, All.scar for example. One that includes functions that are used in more than on skill, such as object interacting.

I think that's it, thanks,

Coh3n

Files should be included in this order to not need forwarding:

- Globals.scar
- - Colors.scar (or ItemInfo.scar)
- - Banking.scar
- - Debug.scar
- - Walking.scar
- - /skills/ 
- - - Skills.scar
- - - - Mainloop.scar
- - - - - RunMe.scar

The more '-' means they are dependant of one or several of the files with less '-'.

~RM

From: Rasta Magician
Files should be included in this order to not need forwarding:

- Globals.scar
- - Colors.scar (or ItemInfo.scar)
- - Banking.scar
- - Debug.scar
- - Walking.scar
- - /skills/ 
- - - Skills.scar
- - - - Mainloop.scar
- - - - - RunMe.scar

The more '-' means they are dependant of one or several of the files with less '-'.

~RM

:D You used my Skills suggestion. Um, the RunMe, did you say that was the file that the user would just run, and then everything would be done for them?

o.k now are we going to be in charge of certain includes because I think that would be a good idea.

From: Blumblebee
o.k now are we going to be in charge of certain includes because I think that would be a good idea.

Like a different SL for each include you mean?

From: Coh3n
Like a different SL for each include you mean?

yes. examples I'm stronger with color than I am with reflection. I can do both but I would prefer handling Color related sequences. Thus I would like to be in charge of setting up Colors.scar and other color related includes. Someone more dominate with reflection should be in charge of walking.scar or something too. Just a thought though, I think it would help organization even more and get MSI rolling faster.

I agree with Blumblebee. It only seems logical that you would work with what you are good at, right?

thinking some more,
Colors.scar -> ItemInfo.scar
Also, this file will probably be huge once our script reaches it's peak, because it'll basically have to load info for all the items for all the skills. So we add….
Objects.scar
This file will deal with all of the finding stuff on ms/inv/etc

Also, I am writing up a thread with what is more or less needed in each file and then we can each choose one file and plan it out.

- Globals.scar
- - ItemInfo.scar
- - - Objects.scar
- - - - Banking.scar
- - - - Debug.scar
- - - - Walking.scar
- - - - /skills/ 
- - - - - Skills.scar
- - - - - - Mainloop.scar
- - - - - - - RunMe.scar

~RM

//SRL Includes
//{.include srl/srl/misc/smart.scar}  --> disabled for now, not to be a pain in the ass while deving
{.include srl/srl.scar}
{.include srl/srl/reflection/reflection.scar}
{.include srl/srl/misc/Reports.scar}

//MSI Script
{.include srl/srl/MSI/Globals.scar}
{.include srl/srl/MSI/Debug.scar}
{.include srl/srl/MSI/ItemInfo.scar
{.include srl/srl/MSI/Objects.scar}
{.include srl/srl/MSI/Banking.scar}
{.include srl/srl/MSI/Walking.scar}

//MSI Skill Files
//{.include srl/srl/MSI/Skills/

//MSI Skill Loops, AI and Mainloop
{.include srl/srl/MSI/Skills.scar}
{.include srl/srl/MSI/MainLoop.scar}

I moved Debug.scar further up. Will be useful so use MSIDebug throughout the other files.

~RM

um and i really hate the use of SVN, so I think we should develope a simple include downloader or something so people dont have to go through the trouble of downloading the SVN. With that said it means someone will have to be constantly updating a downloader and the includes will go through revisions much like SRL.

From: Blumblebee
um and i really hate the use of SVN, so I think we should develope a simple include downloader or something so people dont have to go through the trouble of downloading the SVN. With that said it means someone will have to be constantly updating a downloader and the includes will go through revisions much like SRL.

I really don't think this needs to be on our priority list, and considering that you will be committing, i guess you'll just have to deal with it for now. Also, you haven't yet posted in the MSI SVN username/pw thread so i can add you to the list.

We can, later on, make MSI update itself rather than people doing 'svn update' on their MSI folder, but this really is no priority.

~RM

From: Rasta Magician
I really don't think this needs to be on our priority list, and considering that you will be committing, i guess you'll just have to deal with it for now. Also, you haven't yet posted in the MSI SVN username/pw thread so i can add you to the list.

We can, later on, make MSI update itself rather than people doing 'svn update' on their MSI folder, but this really is no priority.

~RM

alright, just an observation more than anything.