SRL Archive - Senior News and General

Sorry to dump this question so bluntly here and maybe you have gone through this before (couldnt find it) but: why isn't MSI incorporated into SRL? Much of the MSI functionality fits in perfectly into the SRL/skill section. Feels odd and unnecessary complex?

MSI is mainly a script; Which makes it a high-level include. According to (if I'm not mistaken), The Claw, the devs had in the past been against such a high level of include. I imagine because it would make things 'too easy'. However, Boreas has proposed barebones, with basis on MSI.

If MSI got added into SRL, you could easily write a hybrid script in under twenty lines.

There are some imcompatabilities (if that is a word?) between MSI and using it as an include, as far as I'm aware. These are few and could be made non-existent by further layering MSI.

Barebones by Boreas was a project that would make scripting easier. MSI could possibly used for this. It could also be included in SRL to provide everyone with at least one good working script.

There *could* be a difficulty in MSI SLs committing to the SRL Repos, but most likely than not there is some way around that.

If the responsive comes out of this positive, a thread should be made in MSI, to be sure MSI can accommodate this, for if MSI can't then it would be better to find an alternative way of doing it. Perhaps even a different team of people who would be in charge of barebones, although it'd use MSI.

~RM

GetMSI.simba

^Run it, and it'll successfully download the updated version of MSI, svn(not the SRL one), Check for updates before runtime..

But MSI IS in SRL! It's just set up a way where you don't have to compile it and load it if you don't want to.

From: IceFire908
But MSI IS in SRL! It's just set up a way where you don't have to compile it and load it if you don't want to.

Going by that logic so is Reflection, no? Technically they are both 'in' SRL, but only because the user downloaded and put them there.

From: NCDS
Going by that logic so is Reflection, no? Technically they are both 'in' SRL, but only because the user downloaded and put them there.

Yes exactly.

If it's not in srl-opendev, it's not in SRL.

From: Wizzup?
If it's not in srl-opendev, it's not in SRL.

This was my original understanding.

Perhaps a thread should be posted in the MSI SL&PM boards to decide if people want to go through and make it compatible as an include?

Would almost make sense to have another folder for it I think - SRL/MSI. Could be the dev maintained scripts we've been talking about, and would be good to include something people can run "straight out of the box". And with git we could make the MSI devs have commit acccess to SRL/MSI and not the rest of the include yea?

I'd rather see SRL's antirandoms working like they used to and not an overly huge include which is unnecessary to say the least. Things are fine the way they are, the problem is that everyone wants to constantly drastically change everything. Leave it the way it is long enough for real progress to be made before you start reinventing the wheel. It's distractions like these and others that are huger setbacks than a lot of people realize.

MSI is not like SRL. SRL's goal is to provide everyone with a quality means of standardization in every script all things runescape. You don't want to use a script at all if Joe Blow is using his own custom mouse function that uses MoveMouseSmooth. Not very many people are going to know how to make a mouse that uses biezer splines to imitate humans, much less learn how just so they can make a quality woodchopper. Imagine, as an individual, writing absolutely everything in a script that you would need by yourself to have the things you would in a modern day script. It would be so ridiculous that no one could it… especially not efficiently. You'd have massive messy scripts that have tons of redundant code literally copied and pasted hundreds of times in different scripts. This is SRL's function, to make individual scripting reasonable.

MSI doesn't aim towards this same goal. MSI wants a super-duper-all-in-one-do-everything-there-ever-is-or-will-be mass compilation of scripts. Certainly you see the problem integrating MSI into SRL itself, it's completely impractical.

If anything SRL needs less code in it, do away with the skill/ folder, do away with most of the misc, hell get rid of some of the core even. A complex system isn't necessarily the best one.

What is the end goal of combining the two anyways? What already exists is a leechers heaven for all things easy. You check a few boxes and your reflection, SRL, simba, and MSI all automatically download and update. The repositories are neat and organized, combining them would undoubtedly cause nothing but chaos and a headache for those trying to solve it.

Which is why you would have it in a seperate folder. Maybe in SRL/MSI, not SRL/SRL/MSI, it doesnt really matter. Yep its becoming a leechers heaven and thats the way it should continue, theres no need to make things harder than they need to be. Theres no drawbacks to including a MSI-contributor maintained do-everything script that makes scripting even easier, and makes running scripts even easier. I don't think we want to integrate SRL with MSI as such, just including them together would be simple and beneficial. Although if MSI is already automatically installed/updated with the installer like you are saying, I guess theres no real reason other than for aesthetics and simplicity…which are valid reasons imo.

Antirandoms are still as important as ever, I guess thats why we have MSI-Contributors and SRL-Developers.

MSI does not come with Simba's default installation (yet).

From: Icefire980

MSI doesn't aim towards this same goal. MSI wants a super-duper-all-in-one-do-everything-there-ever-is-or-will-be mass compilation of scripts.

<3

And as Icefire puts it, maybe it's best to keep MSI out of SRL. As long as MSI is easily accessible it will bring the same benefits it would from being incorporated into SRL, but it'll avoid a massive headache.

And this leaves me at the same point I've been for a while. I wish someone took up the barebones idea.

~RM

I agree with Icefire to some extend; it's just that Fakawi once dreamed SRL to be so high level that one could literally just type CutWood('draynor', 'willow'); with just SRL. But yeah, I think the way it is currently set up is pretty neat.

From: Wizzup?
I agree with Icefire to some extend; it's just that Fakawi once dreamed SRL to be so high level that one could literally just type CutWood('draynor', 'willow'); with just SRL. But yeah, I think the way it is currently set up is pretty neat.

Don't say I am starting to look like Squigglyo?

From: Wizzup?
I agree with Icefire to some extend; it's just that Fakawi once dreamed SRL to be so high level that one could literally just type CutWood('draynor', 'willow'); with just SRL. But yeah, I think the way it is currently set up is pretty neat.

Thats the logical extension of where we're going. If we could have multiple SMARTs per script then we could just have 1 single script from which ALL autoing on ALL characters could be organised from. Variables and Strings in Player Setup to determine what action and where, reflection webwalk to allow you to choose multiple locations and actions per character, and multiple smarts to determine armies. For example you could have 3 characters running in rotation on 1 SMART at lumby chickens, 1 character on another SMART sudokuing, then 4 characters on rotation on another SMART alternating rounds between mining copper, then mining tin, then woodcutting a load of oaks at varrock. All from the one script, with minimal setup - just a few words in each characters "DeclarePlayers" setup. Even without multiple SMARTS you could get armies of players each doing different things - player 1 woodcut at edgeville, player 2 mine at mining guild, etc.

MSI can already do the part without multiple smarts.

To be honest, including MSI in SRL would make it overly large. Don't fix what isn't broken.

MSI IS a part of SRL anyway, as a community project, it has an extension which can be distributed with Simba, and if someone does go ahead with barebones, SRL as an entity will get to the point of CutWood(CITY_DRAYNOR, TREE_WILLOW);

~RM

From: The Claw
For example you could have 3 characters running in rotation on 1 SMART at lumby chickens, 1 character on another SMART sudokuing, then 4 characters on rotation on another SMART alternating rounds between mining copper, then mining tin, then woodcutting a load of oaks at varrock. All from the one script, with minimal setup - just a few words in each characters "DeclarePlayers" setup. Even without multiple SMARTS you could get armies of players each doing different things - player 1 woodcut at edgeville, player 2 mine at mining guild, etc.

That's exactly what MSI is, only on a Player rotation with a single SMART.

From: Sir R. Magician
Don't fix what isn't broken.

You took the words right out of my mouth. It's working fine as it is. There are no functional benefits to including it in SRL. The change isn't worth the time it would take the devs to integrate it.

MSI uses SRL, however SRL doesn't use MSI - it makes sense for the two to be in separate repos. It gives a good separation between the two. (And makes it impossible/impractical for SRL to call MSI functions. How would you feel if a change in MSI broke SRL?)

At the same time though, an official MSI.sex would be nice. The one Miles wrote seems to work alright, but it'd be nice if it were included with simba?