SRL Archive - RS3 Outdated / Broken Scripts

Just letting everyone know that MSI will be going through a cleaning up process, as SRL 5 becomes more of a reality MSI needs to shift with it.

MSI is Simba only, and MSI is SRL's Community Script.

MSI is a place where all the best contributions could end up in use (eg Gaussian Mouse).

As I said, MSI is in process of switching to SRL 5. SRL 5 is currently between completly hidden doors up at Devs, but it is sipping into MSI already.

SRL 5 is not completed, and so the devs will not be releasing uncomplete work.

SRL 5's aim is to utilize Simba's full power, and the Devs themselves (me included) are still learning from the Simba Devs.

All this to say that MSI will release a new version, v2, after SRL 5 is completed.

SRL 5 Repos: https://github.com/SRL/SRL-5

~RM

Double post:

Please someone get me the MSI Maps pictures in a user-friendly way, and I think we should post the most popular scripts records on here, as well as have a link to the repos, a link to the proggies thread, and links to anything else that might be useful.

As I've said before, I'm on break so I ain't moving a finger.

Err.. SRL5 is not behind closed doors..

https://github.com/SRL/SRL-5

From: Nava2
Err.. SRL5 is not behind closed doors..

https://github.com/SRL/SRL-5

It's not like it's on the forums either

When was this discussed among us Scripting Leaders and most importantly, with Cohen?

Us scripting leaders? U haven't done shit for MSI ever since you became Dev, so who are you to talk about 'us' ?

Sorry, just the truth bro.

From: Sir R. M8gic1an
Us scripting leaders? U haven't done shit for MSI ever since you became Dev, so who are you to talk about 'us' ?

Sorry, just the truth bro.

True, I haven't written much code but I have been following. I comment changes people do or are about to do.
That still doesn't mean that I don't have a say in big decisions, especially when talking about a whole new version 2.

Note the

and most importantly, with Cohen?

Since he is the MSI Leader and I haven't seen a single thread about this in the SL/PM forums.

From: marpis
True, I haven't written much code but I have been following. I comment changes people do or are about to do.
That still doesn't mean that I don't have a say in big decisions, especially when talking about a whole new version 2.

Note the

Since he is the MSI Leader and I haven't seen a single thread about this in the SL/PM forums.

Well since I was Founder of Phoenix probably means that this conversation is in PMs between me and Coh3n.

I didn't know you had been following. For MSI v2 I'll have to make an SLs & Contributors only forum, but it's too early for that :)

~RM

From: Sir R. M8gic1an
Well since I was Founder of Phoenix probably means that this conversation is in PMs between me and Coh3n.

I didn't know you had been following. For MSI v2 I'll have to make an SLs & Contributors only forum, but it's too early for that :)

~RM

by saying "us scripting leaders" I was trying to emphasise there are other, eventhough more minor, people too who should be listened.
This whole v2 game 100% out of the blue, what difference will it make? What new features? Why call it version 2?
Please make a thread about this to:
http://villavu.com/forum/forumdisplay.php?f=272

What the..?

Since when did we agree on this?
E: Or even plan this at all?

Hmm, V2.

MSI is not even finish yet?? and "we" (as i speak for the rest of MSI users) are already moving on to something that nooone has heard about?

Sounds completely bogus on my end that MSI is already becoming V2 when V1 is still having bugs/issues with.

Is SRL5 really going to make v2 better? Or is MSI once again going to have to go through a beta phase.(again)

This is to early of a shift.

I say MSI V2 or w/e you wanna call it, keep it to your self. Include functions/procedures w/e you have to do, because if you merge SRL5 into MSI without knowing whats going to happen as well as 24/7 testing… the Devs WILL have there hands full and its just going to become a bigger list just like the one we have now.

Thats just my 2 1/2 cents.

From: Squancy
Hmm, V2.

MSI is not even finish yet?? and "we" (as i speak for the rest of MSI users) are already moving on to something that nooone has heard about?

Sounds completely bogus on my end that MSI is already becoming V2 when V1 is still having bugs/issues with.

Is SRL5 really going to make v2 better? Or is MSI once again going to have to go through a beta phase.(again)

This is to early of a shift.

I say MSI V2 or w/e you wanna call it, keep it to your self. Include functions/procedures w/e you have to do, because if you merge SRL5 into MSI without knowing whats going to happen as well as 24/7 testing… the Devs WILL have there hands full and its just going to become a bigger list just like the one we have now.

Thats just my 2 1/2 cents.

80% agree with that, 100% with marpis.
Not that my opinion here amounts for much, because I've done "shit" for MSI as you put it to marps

I must say that I feel bad for all the hostility that has been on this thread, and in general from and to RM.

RM you really should take the break, get your head straight and think why we are the best community. This is tearing us apart, little by little.

I agree in the fact that I was going through code and updating it/cleaning it up last night, and will continue to do so today, then commit. Though, I don't see what a 'v2' will accomplish.

Honestly, besides our messy parts, I would say SRL 5 is beginning to look more like MSI rather than MSI needing to look more like SRL 5.

No matter what we do, I see no reason to release as a version 2, or discuss this publicly until we have something to show with it.

Also, considering I generally work on MSI on a daily basis, I would like to be informed of these things if that's not too much to ask. Seems like Coh3n would have mentioned this to me considering we talk most every night.

I have no clue why this was posted. I think for one it should have been discussed with 'all' MSI SL's. I also think this should be in the MSI section :)

Ok I'll be honest. Both me and Coh3n know exactly was is going on at Dev level and how that wil affect MSI.

And usually I come up with the ideas and then check with Coh3n.

MSI v2.0 is something we've talked about a looooong time ago. And now I'm just posting this here, cus that lets the general public know about it.

For SLs you're finding out now too, except probably NCDS has thought about v2 before, or maybe talked about improvements and changes with Coh3n.

The fact that this thread is here means that something about MSI will definitely be more public, otherwise it wouldn't be this publicly announced!

I'll just say that MSI might be looking at a small restructure in terms of who contributes how etc. I'm not giving away the details, otherwise it's no fun for me, just work.

And if I give people the details that means I'd have to write them down, which would be work for me.

And I've been saying already, I'm on break. Just preparing the grounds for when I do come back

~RM

I'm sorry, RM, but I have no recollection of ever discussion something like this with you. =\ I also haven't really followed anything in the dev section, so I apologize if you said something there. NCDS, this will be why you haven't heard of it either.

I'm not really sure what the point of having a v2, considering everything is done through SVN anyway, which no matter what, people will have the latest version. To me, it's just something you add to the name that doesn't really mean a while lot. :unsure:

I think future plans like this should be discussed in the SL section. I'll make a thread now.

IMO, you MSI Devs/SLs/Contributors/whatever can call it V2 internally when backend stuff changes if you want, but don't call it V2 externally unless either users get new features (and I don't mean like a sandwich making robot now makes more types of sandwiches, I mean now also makes breakfast/dinner), or if script records from V1 are incompatible with V2.

From: Boreas
IMO, you MSI Devs/SLs/Contributors/whatever can call it V2 internally when backend stuff changes if you want, but don't call it V2 externally unless either users get new features (and I don't mean like a sandwich making robot now makes more types of sandwiches, I mean now also makes breakfast/dinner), or if script records from V1 are incompatible with V2.

This

Calling it MSIv2 will only make confusion

From: Boreas
IMO, you MSI Devs/SLs/Contributors/whatever can call it V2 internally when backend stuff changes if you want, but don't call it V2 externally unless either users get new features (and I don't mean like a sandwich making robot now makes more types of sandwiches, I mean now also makes breakfast/dinner), or if script records from V1 are incompatible with V2.

Makes sense.

Not sure why everyone is getting so butt-hurt over this… (not that I have any say it it, nor do i care what happens) but afaik RM is high as a kite all/most of the time (as are a lot of us here at SRL) So jus let him post some shit lol… Feel free to correct him if he's wrong, but there's no need for all the anger… Keep in mind we write open source codes to auto on Runescape… Things are not that serious here… and if you think they are, you need to take a break and live life away from the computer ;)

Now that I'm done ranting, I'm going to have to agree with the above(s)… No point in V2, but a clean up in MSI would be nice ;)

@Boreas: I'll give you 100m for your sandwich making robot… (200m for V2 if there are no bugs)