SRL Archive - SRL Updates & Announcements

Convert your scripts by January 1st, 2012!

So the long awaited SRL5 is here, but not like you're expecting. Our original plans kind of fell through due to several problems that I won't get into, but the main was lack of development. So what we've done is copy SRL4, add documentation, and remove any SCAR support. I imagine some of your are disappointed and we apologize for that. Our plans are to apply our original ideas of SRL5 to SRL6 (which likely won't be for a very long time, unfortunately). There will still be several bug fixes and function additions to SRL5, so don't worry about that. :)

Unfortunately, there are a few things that will break your scripts:

• All SCAR file extensions have been changed to Simba (.scar -> .simba)
• The stats.scar file has been changed to globalstats.simba and moved to srl/core/
• Stats is now included with SRL so you do not need to include globalstats.simba in your script
• SetAngle and ClickNorth now take integer parameters (fixed a small bug). You now call them like this:

SetAngle(SRL_ANGLE_HIGH);
ClickNorth(SRL_ANGLE_NONE); // SRL_ANGLE_NONE will negate the 1-2s wait in SetAngle
SetAngle(SRL_ANGLE_LOW);

• You have to define SRL5 at the top of you script, and use IFDEF's where applicable throughout your script. For example:

program new;
{$DEFINE SRL5} // comment to use SRL4

{$IFDEF SRL5}
  {$i srl/srl.simba}
{$ELSE}
  {$i srl/srl.scar}
{$ENDIF}

begin
  clearDebug();
  setupSRL();

  {$IFDEF SRL5}
  clickNorth(SRL_ANGLE_NONE};
  {$ELSE}
  clickNorth(true);
  {$ENDIF}
end.

• SRL5 now uses Gaussian randomness inside its mousing functions. This means that it will now "aim" towards the center of the random box. The parameters are the same, and nothing changes in the scripting interface. For more information on this, please see: docs.

MSI is completely compatible with SRL5 and 4, so if you wish you can download SRL5 and you'll be good to go.

Getting SRL5:

• Disable the SRL Updater.
• Download SRL5 to Simba/Includes/ (or use Git Clone)
• Rename your OLD SRL folder to "SRL-4", and rename the new SRL-5 folder to "SRL"
• Done!

SRL5's documentation can be found here. There are most likely some parts that were overlooked, so don't be afraid to let us know. The repository can be found here.

SRL-5 will replace SRL-4 in the updater as soon as possible after January 1st, 2012, so convert your scripts now!

Enjoy,
The SRL Development Team

(*
InPin
~~~~~

.. code-block:: pascal

    function Inpin(Pin: string): Boolean;

Enters bank pin. Will try 3 times, returns true if bank is opened.

.. note::

    Author: ZephyrsFury and Nava2
    Last Modified: Unknown

Example:

.. code-block:: pascal

    if PinScreen then
    InPin('1234');
*)

{*******************************************************************************
function InPin(Pin: String): Boolean;
by: ZephyrsFury and Nava2
Description: Enters bank pin. Will try 3 times, returns true if bank is opened.
*******************************************************************************}

I wanna stab my eyeballs.

The new headers can be parsed by sphinx to auto-generate docs…plus its been kind of default for SRL5 for a while(we used this in reflection as well).

From: mormonman
The new headers can be parsed by sphinx to auto-generate docs…plus its been kind of default for SRL5 for a while(we used this in reflection as well).

How hard would it be to parse the old headers? Or create some other headers that don't cause my eyes to bleed?

Cracking me up here wyn10 LOL!
So basically, we have to chance and adjust all of our shiz to compile properly, and get no new benefits?

LOLZ JK GUISE! <3 Great job, I know you all work hard!

Awesome, I'll play around with it this weekend, will have free time actually!

I like the new headers more.

Will start converting today. Congratulations on the much anticipated release! :thumbsup:

Edit:
Could we possibly get summoning.simba implanted in SRL/SRL/skill/? Some people are having difficulty installing it themselves even after the short tutorial I made. I don't see why we couldn't just include it in SRL.

Edit2:
Either I'm doing something wrong or this isn't complete. I'll wait until more information is posted.

I really have no idea why this is being released instead of adding documentation into SRL4?…

But neat. I agree with wyn for sure though.

I like the new way :D, nice work guys.

For wyn10 complaining.. http://docs.villavu.com/srl-5/

Does that make your eyes feel better? :)

I'm sorry to be a downer, but how does this warrant a full version step. From what I can tell, the changes are not on that sort of scale.
Thanks for the work you all have put into this.

From: Nava2
For wyn10 complaining.. http://docs.villavu.com/srl-5/

Does that make your eyes feel better? :)

It's neat and all but I don't know why sphinx's source couldn't be modified to understand the old headers? Or why stuff is using integers now? They are just more confusing to new scripters. But nice work anyways everyone who contributed.

From: Harry
It's neat and all but I don't know why sphinx's source couldn't be modified to understand the old headers? Or why stuff is using integers now? They are just more confusing to new scripters. But nice work anyways everyone who contributed.

I guess its because theres more info in the new headers than there was in the old ones. And if you add more info to the old ones, it'll make it ugly too.

From: Flight
Will start converting today. Congratulations on the much anticipated release! :thumbsup:

Edit:
Could we possibly get summoning.simba implanted in SRL/SRL/skill/? Some people are having difficulty installing it themselves even after the short tutorial I made. I don't see why we couldn't just include it in SRL.

Edit2:
Either I'm doing something wrong or this isn't complete. I'll wait until more information is posted.

What's the problem?

From: noidea
I'm sorry to be a downer, but how does this warrant a full version step. From what I can tell, the changes are not on that sort of scale.
Thanks for the work you all have put into this.

The main reason being it no longer works with SCAR. SRL4 is still SCAR compatible, while SRL5 is not.

Just a note, SRL 4 will never be SCAR compatible again.

From: Coh3n
What's the problem?

The main reason being it no longer works with SCAR. SRL4 is still SCAR compatible, while SRL5 is not.

If that's the main reason, I completely disagree. Yes it is a significant change, but not worth the step from 4 to 5. A "4.5" or some sort of notation after 4 would be more realistic. I'm sorry to highjack a celebration-y type thread though. I just feel like more thought and community input should have gone into this.

From: noidea
If that's the main reason, I completely disagree. Yes it is a significant change, but not worth the step from 4 to 5. A "4.5" or some sort of notation after 4 would be more realistic. I'm sorry to highjack a celebration-y type thread though. I just feel like more thought and community input should have gone into this.

I really don't see what the big deal is. It's just a number.

From: Coh3n
I really don't see what the big deal is. It's just a number.

If that's the way you look at it.

From: noidea
If that's the way you look at it.

What's that supposed to mean? It's not like I was the only one to make this decision, it was discussed with the active developers.

From: Coh3n
What's that supposed to mean? It's not like I was the only one to make this decision, it was discussed with the active developers.

If its only a number, then it obviously wasn't discussed enough.

From: noidea
If that's the way you look at it.

http://www.itworld.com/software/169503/new-linux-30-kernel-same-old-kernel

From: Coh3n
What's that supposed to mean? It's not like I was the only one to make this decision, it was discussed with the active developers.

All I see are butchered methods and no scar extension.

I can't see how this can be srl 5.

From: Nava2
For wyn10 complaining.. http://docs.villavu.com/srl-5/

Does that make your eyes feel better? :)

So opening a website so I can properly read it is any better?

From: Nava2
http://www.itworld.com/software/169503/new-linux-30-kernel-same-old-kernel

Release date + having regular time based releases affected there versioning. As far as I can tell SRL does not have a regular release cycle.

From: wyn10
All I see are butchered methods and no scar extension.

I can't see how this can be srl 5.

Butchered methods? I hardly think so. I assume you're still talking about the documentation/headers. SCAR extension? We have Simba now, there's no reason to keep support for a program that is no longer a part of SRL.

From: wyn10
All I see are butchered methods and no scar extension.

I can't see how this can be srl 5.



So opening a website so I can properly read it is any better?

Well, it is. We, the development team, decided this was the best route and was necessary.

We made this decision in hopes that you, the community, would appreciate it. There are significant changes, most of which are transparent to the users.

Yes, the version number is a big change, get over it.

As to the documentation, this is here to stay. Once you get over the fact that its larger, its quite nice to read. Its more obvious and is *very* flexible.

Lastly, something not mentioned, we moved to git. This was a very popular decision, and something that was not the most straight forward for us to learn (coming from SVN). We wanted a more community based version control system, and now we have it.

From: Coh3n
Butchered methods? I hardly think so. I assume you're still talking about the documentation/headers. SCAR extension? We have Simba now, there's no reason to keep support for a program that is no longer a part of SRL.

While browsing SRL 4…. looks like someone butchered in simba compatibility…and now the scar stuff was removed…So ya it just looks butchered.

From: wyn10
While browsing SRL 4…. looks like someone butchered in simba compatibility…and now the scar stuff was removed…So ya it just looks butchered.

Yes, simba capability was butchered in. You are correct, in SRL5 I see no such thing. Everything was done for a reason.

From: Nava2
Yes, simba capability was butchered in. You are correct, in SRL5 I see no such thing. Everything was done for a reason.

I don't understand what you just said.

From: wyn10
I don't understand what you just said.

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

Try it and see.

SRL 5 was designed for SIMBA specifically. SRL4 was a constant battle to maintain cross compatibility. Now with removing SCAR support we were able to "cut out the fat" and optimize the include. This optimization constisted of many things including new commenting system, new versioning system and an altered layout for the include itself. That is on top of code optimizations.

If you want to see all the work done look at the GIT logs. We don't have time to hold hands and walk everyone through every change that was made. We felt it was big enough changes for a new version number. A lot of discussion went into this. So please don't complain about version numbering and just appreciate the hard work our devs put into this.

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

Try it and see.

Ya defines are gone…but the code used is still the same.

I personally like the change, good step moving forward! :)

From: wyn10
Ya defines are gone…but the code used is still the same.

Yeah…?

Did you think we were going to completely rewrite all the code from scratch?

From: wyn10
Ya defines are gone…but the code used is still the same.

From: Coh3n
Yeah…?

Did you think we were going to completely rewrite all the code from scratch?

You hardly see huge code rewrites of working code when versioning it. Most of the time it's tweaks and optimization's that needed to be done (Which is what appears to have been done).

Now, that doesn't mean that's never the case, but why rewrite something that already works with optimization?

From: Coh3n
Yeah…?

Did you think we were going to completely rewrite all the code from scratch?

Yeah that's kinda what you need to do for a major release to get true Simba compatibility…..

From: wyn10
Yeah that's kinda what you need to do for a major release to get true Simba compatibility…..

That's not true at all. The SCAR version that was supported used the same interpreter as Simba, so 98% of the code worked with both programs. There was only a few small changes.

From: wyn10
Yeah that's kinda what you need to do for a major release to get true Simba compatibility…..

Correct me if I'm wrong, but isn't it just what the files were named? ".scar" to ".simba" to make SRL5 Simba only? Since they're both Pascal based, the code should work no matter what version number you assign it.

From: Coh3n
That's not true at all. The SCAR version that was supported used the same interpreter as Simba, so 98% of the code worked with both programs. There was only a few small changes.

Well you guys can think whatever you want I guess; if someone though went through and added hundreds of IFDEFS just to get it compiled, I'd call that butchering.

From: wyn10
Well you guys can think whatever you want I guess; if someone though went through and added hundreds of IFDEFS just to get it compiled, I'd call that butchering.

And you're free to think what you want. ;)

Well, the reason why people are trippin' is because before, when we used to introduce new SRL revisions, something big is in there. I remember 13-15 pages under the release threads lol.

We didn't really have what we had today, where whenever something is broken, someone fixes it and posts. We usually fixed up everything and made a whole new SRL with major additions to the include. After a major Jagex update, we would sometimes wait weeks for a new SRL.

Yeah I remember those time clearly lol. We used to all flock to tutorial Island and make threads on: "how to install SRL 3" "SETTING UP SCAR TO WORK WITH THE NEW SRL" "How to make so and so with the new SRL !!@!". Ah good days… Ah ha haa.

Never the less good job. But I think yall shoulda waited to release SRL 5.

Maybe once Marpis finishes SPS2.0, include it in there.
Lots of good stuff around the forums that can be formally implanted into SRL.

Good job guys i am happy about the release.

sure its not quite what you guys wanted but its a start and a damn good one.

As for people complaining about a version number get over it, SRL 5 is a step forward and should be named that, we have moved away from SCAR support which if you didnt know is a big step, people will now know they cant use SRL 5 with SCAR and simply use SRL 4 so its very informative.

When i make my scripts i always increment my version number by 0.05 regardless of what i do and the reason why i did that is because its up to me what number i give it, eve if i change i line of code i will increment it.

So my point is its up to the developers what version number they give it and if they want it to be 5 then its 5, so deal with it.

sorry for the rage but arguing over a number when we can update and get SRL back up and running/improved is stupid.

So keep up the good work Dev Team.

The incredibly improved documentation, complete with example code!, is reason enough to release our work, especially now. It is something everybody with community-feel can work on and help us improve the readability and quality of our include. Yes it may look akward compared to the old formatting, but in fact it is the other way around. The old formatting had no meaning whatsoever, just made-up /***** etc. The new formatting has meaning. Besides, the real nuisance is completely on the devs side, because we are we ones that need to code into this. The average user hardly ever looks into SRL, and you will get used to the new look quickly enough.

I really don't see all the fuzz. Besides, SRL has been solid for 6 years! The include is "finished", not much work needs be done in order to keep it running. Also, remember where we came from. SRL Updates appear nowadays almost always within a couple of hours aot. days or even weeks not even so long ago.

So yeah, different it is, but it has much more meaning this way. Help us build it!

Besides: Thread title says Beta, no?:D

Good job on the beta release!

It's a shame to see SCAR phased out, but seeing as Simba is now king at Villavu, it was the right thing to do.

If you're not happy with this, or you would still like to work with SCAR, then you can always go help Wanted out with OSI at Freddy1990's Forums, I'm sure he'll be happy with some extra help on his project. :)

From: wyn10
Well you guys can think whatever you want I guess; if someone though went through and added hundreds of IFDEFS just to get it compiled, I'd call that butchering.

Butchering is what happened to SRL 4 months ago: we were adding a lot of IFDEF's initially for support for Simba and it became messier over time. scar apparently has/had no interest of keeping up with Simba and compatibility is more of an issue that it was initially.

From: noidea
If that's the main reason, I completely disagree. Yes it is a significant change, but not worth the step from 4 to 5. A "4.5" or some sort of notation after 4 would be more realistic. I'm sorry to highjack a celebration-y type thread though. I just feel like more thought and community input should have gone into this.

Tell that to the obnoxious developer who has since left. There have been so many threads about this it's nearly worth crying over the stupidity. Luckily, we're rid of that now.

From: wyn10
Yeah that's kinda what you need to do for a major release to get true Simba compatibility…..

There's more to it than just define removal. The documentation is a great step forward and will only improve. SRL 5 will offer a stable base while we work towards SRL 6. It's also now officially git and no longer svn, so everyone can easily commit/file pull requests. The removal of scar compat / naming conventions was a logical step because it's weird that everyone uses simba to macro with srl, but it's still all named for scar. Compatibility was also holding us back a lot. Simba can do a lot of things scar can't and not being able to deploy that properly is just because we should remain compatible with a product no one here uses is stupid. You'd eventually end up with a Simba SRL that has more more (or different) functionality from the scar srl version, which obviously makes no sense. IFDEF's are stupid and should only be used where necessary. Most of the SRL core functions were very messy because of all the IFDEF's. You don't have to agree, but this is how it'll be. Feel free to work on improving SRL 5 and making our lifes here even better.

The version number bump was simply required because this is a great step forward. Let me ask you, how many people actually know this SRL was SRL version 4? Not many, after all - you don't notice it in the include statement, you don't notice it in the extension updater, you don't notice it … just about anywhere. You only know at some point SRL 5 and SRL 6 are coming.

Stop whining about the version bump and focus on the good and important things.

tl;dr: there is a lot of big stuff in there, just not in the usual fashion.

From: Flight
Will start converting today. Congratulations on the much anticipated release! :thumbsup:

Edit:
Could we possibly get summoning.simba implanted in SRL/SRL/skill/? Some people are having difficulty installing it themselves even after the short tutorial I made. I don't see why we couldn't just include it in SRL.

Edit2:
Either I'm doing something wrong or this isn't complete. I'll wait until more information is posted.

You could file a pull request at github? :)

Yeah I'm not signed up for Github or anything like that. I'm just the small-time scripter. :p I was hoping something that simple could get approved and someone on the dev team could add it into SRL.

From: Flight
Yeah I'm not signed up for Github or anything like that. I'm just the small-time scripter. :p I was hoping something that simple could get approved and someone on the dev team could add it into SRL.

GitHub it's so easy to use even a BraK could do it. :) Try it out I know you'll love using it.

From: Flight
Yeah I'm not signed up for Github or anything like that. I'm just the small-time scripter. :p I was hoping something that simple could get approved and someone on the dev team could add it into SRL.

I'll assure you that unless you have absolutely no knowledge of git - then the first time takes some time - you will actually save time by making a pull request. We can easily merge your changes and you won't see your thread sitting on the forum for days. ;)

From: Coh3n
That's not true at all. The SCAR version that was supported used the same interpreter as Simba, so 98% of the code worked with both programs. There was only a few small changes.

I believe the reason for that was because Simba ripped pretty much everything that was in SCAR, just saying… ;)

Glad to see you guys are finally going your own way, now I can finally justify not returning here. Good luck in your endeavours :)

From: Freddy1990
I believe the reason for that was because Simba ripped pretty much everything that was in SCAR, just saying… ;)

Not ripped. Seeing as SCAR was closed source, copy/pasting would be impossible.

From: Freddy1990
I believe the reason for that was because Simba ripped pretty much everything that was in SCAR, just saying… ;)

Glad to see you guys are finally going your own way, now I can finally justify not returning here. Good luck in your endeavours :)

I believe reimplemented is the proper word. We cannot rip something that is closed source. Or is WineHQ ripping off Windows?
I've asked you countless of times to release the source code so others could work on it - and you didn't. Simba is the result of that, you should just live with that (and you are, so that's cool).

I think we did a pretty good job with it, too. Regardless, I suggest that you continue this discussion elsewhere (or not at all) because this is off topic.

@Coh3n:
You mentioned in the OP to include {$IFDEF SRL5}, where exactly should we use this within a script? Apologies for the stupid question, I've clearly not done this before. :(

From: Flight
@Coh3n:
You mentioned in the OP to include {$IFDEF SRL5}, where exactly should we use this within a script? Apologies for the stupid question, I've clearly not done this before. :(

You could do something like:

{$IFDEF SRL5}
{$I SRL/SRL.simba}
{$ELSE}
{$I SRL/SRL.scar}
{$ENDIF}

And repeat that where required.

Good job, everyone.

When SRL5 is put in to the updater, will we have to learn new standards? I remember reading somewhere that new standards and a few other things were under discussion once SRL5 would be released to the general public.

Could people please test this branch in particular: https://github.com/SRL/SRL-5/tree/gauss

It does break compatibility.

E: I have fixed it to not break anything.. if I could get it to commit properly. :<

Rewrote the first post.

Update your scripts ASAP!

Thanks, converting my scripts now!

I will start converting. ZMI will be SRL5, and I'm guessing a lot of people are gonna want it so I hope that will help.

Flight you can have it for both just add in a {Def} at the begin where you include the script. something like this.

{$IFDEF SRL5}
  {$i SRL/SRL.simba}
  {$i SRL/SRL/MISC/Debug.simba}
{$ELSE}
  {$i SRL/SRL.scar}
  {$i SRL/SRL/MISC/Debug.scar}
{$ENDIF}  

Yes, but having it mandatory is a good motivator.

'GetCurrentTab' is broken. :/

The immense usage if $IFDEF might clog our scripts up. How about they are included in the SRL5 functions themselves, so if SRL5 is defined it runs normally but if not then it redirects to SRL4 functions?
Makes more sense to me, primarily to reduce script clutter.

From: Bad Processor
The immense usage if $IFDEF might clog our scripts up. How about they are included in the SRL5 functions themselves, so if SRL5 is defined it runs normally but if not then it redirects to SRL4 functions?
Makes more sense to me, primarily to reduce script clutter.

Well, it would indeed make sense not to support SRL 4. Only for your current scripts.

From: Flight
Yes, but having it mandatory is a good motivator.

'GetCurrentTab' is broken. :/

Yeah I saw that… I fixed it in mine. I'm starting to run it and actually make it a usable include. There's currently a major delay in FindNormalRandoms too.

From: Narcle
Yeah I saw that… I fixed it in mine. I'm starting to run it and actually make it a usable include. There's currently a major delay in FindNormalRandoms too.

I'll have a look at that after work. I'm pretty sure I know what it is, though I thought it had already been addressed.

Can't wait! Will MSI have to be updated too?

From: Kyle Undefined
Can't wait! Will MSI have to be updated too?

Already updated (See the define in Runme.simba)

From: NCDS
I'll have a look at that after work. I'm pretty sure I know what it is, though I thought it had already been addressed.

I already fixed it. Just have to push it, making bunch of changes actually using it to bot.

From: Zyt3x
Already updated (See the define in Runme.simba)

Shaweet! :D That's one less thing to worry about.

From: Narcle
Yeah I saw that… I fixed it in mine. I'm starting to run it and actually make it a usable include. There's currently a major delay in FindNormalRandoms too.

I tracked everything back down to GetCurrentTab. Antirandoms are detected via the inventory gametab so that'd be the reason. I also previously did a test to see the speed of how long it took just to search for randoms, over 15 seconds. :/ Anyways yeah I just used the old SRL4 GetCurrentTab, works just fine.

From: Flight
I tracked everything back down to GetCurrentTab. Antirandoms are detected via the inventory gametab so that'd be the reason. I also previously did a test to see the speed of how long it took just to search for randoms, over 15 seconds. :/ Anyways yeah I just used the old SRL4 GetCurrentTab, works just fine.

Yeah I figured that out.
Already pushed a commit.

Why does smart restart every time I run an srl 5 script?

From: ggzz
Why does smart restart every time I run an srl 5 script?

The server world is probably changing.

SMART_Server := ;

From: Narcle
The server world is probably changing.

SMART_Server := ;

I have those:

  Smart_Server := 72;
  Smart_Members := True;
  Smart_Signed := True;
  Smart_SuperDetail := False;
  SmartSetupEx(Smart_Server, Smart_Members, Smart_Signed, Smart_SuperDetail);

I had to use SmartSetupEx in order for it to not switch worlds or else every time I press play, it closes smart and re-opens one. I have no clue why but that SetupEx works perfectly for me.

Thanks though.

@ggzz: How did you include SMART at the top? It doesn't restart for me..

Smart variables must be set before SetupSRL; is called.

Ok it looked like this before I solved it:

  {$Define SRL5}
  {$define SMART}
  {$Define CRASHSMART}
  {$i srl/srl.simba}
  {$i SRL/SRL/misc/paintsmart.simba}

//codes here.. blah blah functions.. blah blah procedures..

begin
  Smart_Server := 72;
  Smart_Members := True;
  Smart_Signed := True;
  Smart_SuperDetail := False;
  SmartSetupEx(Smart_Server, Smart_Members, Smart_Signed, Smart_SuperDetail);   //was restarting before i added this..

  setupSRL();

  DeclarePlayers; 
end.

Might just be me though :S dunno why but I'll just use that smartsetupex.. it's no biggie.

May have something to do with crash SMART. I know that part was removed from SRL5.

After updating, whenever I try to compile a script this comes up:

[Error] C:\Simba\Includes\SRL/SRL/misc/smart.simba(16:34): Semicolon (';') expected at line 15
Compiling failed.

Yeah, a dev wrote a stray mouse in that file.

SmartHoldMousePlus(x,y,1) mouse

Just remove that extra "mouse" for now.

sooo… When will this be replacing SRL 4 in the updater?

From: Harry
Yeah, a dev wrote a stray mouse in that file.


Just remove that extra "mouse" for now.

It's fixed, that was my bad.

From: legoace
sooo… When will this be replacing SRL 4 in the updater?

Wizzup? said soon.

Congrats on the release!
Glad that SRL is moving away from SCAR and is putting everything into simba.

Something that most people havent said, that they should be saying is;
THANK YOU to everyone that contributed to the release!

i changed to it then changed cuz SMART didnt work! then i released that i put the

{$define SMART}

before everything >.< will reinstall it and try it again :D

So I don't get it… if we are using MSI do we need to download this or not?

From: Jordan155
So I don't get it… if we are using MSI do we need to download this or not?

You don't need to download this at all. It has been added to the updater, so just update SRL in simba and youll be set

From: [Nathan]
You don't need to download this at all. It has been added to the updater, so just update SRL in simba and youll be set

That is what I did and now I am getting this error:

Exception in Script: Unable to find file 'srl/srl.scar' used from 'C:\Simba\Includes\MSI/MSI/Core/Setup.simba'

I have tried updating everything and even overridden and forced updates on everything and I am still getting this error.

Any ideas?

From: Jordan155
That is what I did and now I am getting this error:

Exception in Script: Unable to find file 'srl/srl.scar' used from 'C:\Simba\Includes\MSI/MSI/Core/Setup.simba'

I have tried updating everything and even overridden and forced updates on everything and I am still getting this error.

Any ideas?

It's fixed in the latest version of MSI.

Getting SRL5:
Disable the SRL Updater.
Download SRL5 to Simba/Includes/ (or use Git Clone)
Rename your OLD SRL folder to "SRL-4", and rename the new SRL-5 folder to "SRL"
Done!


How do you do that?!

You don't need to do that anymore as SRL5 has been pushed to the official SRL revisions.
Just run the normal updater in Simba and you'll be fine.