SRL Archive - General

Sort of continuing on from Coh3n's post about closing development; I think it would be wise to come up with a plan, or guideline perhaps of where MSI is headed. So you all know where I'm coming from; In my opinion MSI should become sort of a 'default' script collection that is shipped with SRL.

I think we've pretty well agreed that a downsize of some sort is in order, not that it's ideal, but it does seem necessary at this time. The next question is; what do we get rid of?

I propose we cut back to cover the "main" skills (ie. Mining, WC, fishing, magic, and maybe cooking). Then with those skills we only hold support for a few of the more popular locations. As for magic, I say we just keep our alcher and leave it at that. The decrease in locations alone would make MSI much more low maintenance.


This thread is merely for brainstorming purposes; when we actually go through with the downsizing I would like to make MSI as dependent on SRL6 as possible.

Thoughts?

so, you'd have /core, /skill, /misc, /msi? That way you can first keep it sorta seperate.

From: WT-Fakawi
so, you'd have /core, /skill, /misc, /msi? That way you can first keep it sorta seperate.

Or it MSI could go in /Simba/Scripts/. I'm really not overly concerned what the actually path ends up being, just trying to through out some thoughts and spark a discussion. :)

Mining, WCing, and Fishing keep for sure. Alching maybe, but I think it should be simplified so it's setup strictly for an alcher. Cooking could be removed if SPS still doesn't work well in Al-Kharid.

As for locations, we just need to look at them and keep a couple for each skill.

Couple more things I thought about:

1. Convert the downsized version of MSI to Lape (we can get a working version of SRL-6 at the same time by just adding the functions used in MSI).
2. Can probably remove the MSI_Players array and use SRL's players[].
3. Obstacles? Should be removed or no? I think they should be kept.
4. Objects converted to smartcolors.
5. Remove form.
6. Simplify progress report (have "Loads banked" instead of each rock type).
7. Can remove all DTMs and just use ExistsItem, or not even keep track of items. Let's assume the user setup the script properly (player has right tool, etc.).
8. I think the less maintenance the better.

Thoughts?

Form's are not currently support in Lape much to my Sadness(nielsie said he try and port them in later.) But the big issue with the form was it got crazy over developed. If the Form is kept small and basic it shouldn't be hard to maintain once made. This shouldn't be to hard seeing as with downsizing MSI you'll take out a lot of the Content from the form. Keeping it all to common areas then limits how many locations you'd need on it with less locations you could have basic location detection built in. Thus shrinking the form again.

From: Coh3n
Couple more things I thought about:

1. Convert the downsized version of MSI to Lape (we can get a working version of SRL-6 at the same time by just adding the functions used in MSI).
2. Can probably remove the MSI_Players array and use SRL's players[].
3. Obstacles? Should be removed or no? I think they should be kept.
4. Objects converted to smartcolors.
5. Remove form.
6. Simplify progress report (have "Loads banked" instead of each rock type).
7. Can remove all DTMs and just use ExistsItem, or not even keep track of items. Let's assume the user setup the script properly (player has right tool, etc.).
8. I think the less maintenance the better.

Thoughts?

1. absolutely
2. absolutely
3. yes, keep them as I'm sure the system will still be used.
4. absolutely
5. absolutely
6. absolutely
7. We will still need failsafes in place to ensure all is well, but I support this.
8. absolutely

From: BraK
Form's are not currently support in Lape much to my Sadness(nielsie said he try and port them in later.) But the big issue with the form was it got crazy over developed. If the Form is kept small and basic it shouldn't be hard to maintain once made. This shouldn't be to hard seeing as with downsizing MSI you'll take out a lot of the Content from the form. Keeping it all to common areas then limits how many locations you'd need on it with less locations you could have basic location detection built in. Thus shrinking the form again.

Yeah, that's why I said to remove it, because Lape doesn't support forms. I started, and got pretty far, on a new MSI form, so if Lape does get form support, we can just work off that.

@NCDS: I don't think we'll need a failsafe system, unless we actually need to identify the items. If the user sets up the script properly, we won't ever need to recognize items. That's the beautiful thing. If they don't set it up right, it's their problem.

From: Coh3n

@NCDS: I don't think we'll need a failsafe system, unless we actually need to identify the items. If the user sets up the script properly, we won't ever need to recognize items. That's the beautiful thing. If they don't set it up right, it's their problem.

That's the failsafe I meant. :p

If the user doesn't have all the necessary 'tools' we don't want the script to go ahead and run anyways, do we?

Well, yeah, screw it.

From: NCDS
That's the failsafe I meant. :p

If the user doesn't have all the necessary 'tools' we don't want the script to go ahead and run anyways, do we?

Well, yeah, screw it.

Oh, well obviously we can check if an item exists in say the weapon slot, or first inventory slot. That's only one line of code. We could do that, or just assume the user isn't stupid. :p But that extra check won't hurt.

I might start on this fairly soon depending on how my schedule is this weekend. I'll probably start by creating a new branch for MSI, and saving a .zip of the current MSI so we always have a copy. Then we can start coinciding the development of this MSI with SRL-6 (all on github of course).

From: Coh3n
Oh, well obviously we can check if an item exists in say the weapon slot, or first inventory slot. That's only one line of code. We could do that, or just assume the user isn't stupid. :p But that extra check won't hurt.

I might start on this fairly soon depending on how my schedule is this weekend. I'll probably start by creating a new branch for MSI, and saving a .zip of the current MSI so we always have a copy. Then we can start coinciding the development of this MSI with SRL-6 (all on github of course).

Sounds good. Weekends suck for me ( I work 12 hours on friday, saturday and sunday), but mon. tues. and weds. I have a decent bit of time usually.

Cool. I'm really getting frustrated with this SPS map thing, so I may just leave it for now.