SRL Archive - Discussions & Debates

Hello SRL Community. I supported this community as a developer back when OSR was the only runescape, but I've been having a terrible time trying to understand the new way of doing things, so I'm giving an honest opinion from an old school scripter..

Over three 3rd party program/plugins are required to operate SCAR (re-named to SCAR Divi, re-named to Simba/SMART/Whatever).. Not a good direction to go in.. A single respectable program is sufficient for colour and macro-based application.

I started trying to get simba working a few months ago, the guides were not only out-dated.. The program didn't even work correctly, updating newer SRL/plugin/ext versions with older ones and parts of something called SPS were required to run (although from what I immediately learned in forum posts, SPS is no longer used in the actual program)
When I finally got setupSRL(); script to call, other methods had not been declared and I had to delete large sections of code relating to screen-co-ords or non-existant methods being called from within SRL's core files.. (SMART loaded but did not deliver a single promise of not-using the active mouse, or even working without being disabled)

So anyway, I was using just mouse-methods (thank you benland100) from SRL and I had to use old methods of colour-finding to make any scripts I wanted. It was all working as well as I could hope for a few months, then something was updated.. Now I had to re-install again basically, there are no scripts for this new version (v6 as it's only come out just now) and the simple script I had made before doesn't work now because SMART client was changed and co-ords/colours are all different. (Forcing the end-user to also do a re-write)

You have done to SRL, what runescape did with their terrible updates.. It's all ruined..
The founding fathers of RS cheating certainly did not imagine such a convoluted, complex system which (in frequent updates) renders all scripts made with previous versions completely useless.
Make something which doesn't need to be completely re-written over and over again in the search for a perfect SYNTAX
The greatest programs flaunt their ability to continue working when someone tries to jam the gears.

One piece of advice I would give is that when you change something, leave the old call there.. Or even better, make the old method call the new method. The goal is for every well-written script to continue working for all time. Example below.

MMouse(oldx, oldy, true);
begin
if(true = true)
  begin
    StupidChanges(oldx, oldy, 4x4.TPA, LeftClick.Extended[2,0,0.53]);
  end else
  begin
    StupidChanges(oldx, oldy, 4x4.TPA, RightClick.Extended[1,0,4.89]);
  end;
end;

Anyone at SRL is encouraged to cooperate in order to improve SRL. I feel that is exactly what we've all been thinking when we moved away from SCAR Divi and SRL4. SCAR was too buggy to operate and it's developer too busy to maintain it (and too proud/scared/whatever) to release the source so we started our own program; one that anyone could contribute to. You seem to think SRL is all about botting on RuneScape; well, I like to think SRL is more than that. SRL is a community which focuses on bringing forth the inner programmer in us all. What better way to encourage young beautiful minds other than letting them create something of their own and contribute to a larger cause while making bots for a game we've all played?

SRL has seen better times, yes, I won't argue with that at all; when people lose interest in RuneScape, they might also lose interest in SRL. A lot of the former big names are now gone; they've moved on.
Maybe it's time for you too to do so?

First thing: SCAR wasn't open-sourced anymore, therefore simba arised.

second thing: SPS had a delay in srl6 compatibility, @Olly fixed that now though.
auto-updating should be straightforward, @Coh3n made an excellent step by step setup-guide.

third thing: yes srl6 is different than srl5, nobody likes changes. But not all changes are bad, just getting used to it is the tricky part.
And everybody had to rewrite their scripts, you phrased it so egocentrical.

And yes the activity on srl has been dropping, noticed that when rs3 came out and everybody was waiting for srl6.
But I always liked this community, going back to '06 (big fan:) ) Always a friendly smile around the corner, always a helpful hand nearby.

Actually, Zytex, I cut my teeth on finding other uses for SCAR. I wrote a script which printed a form of sheet music to debug which the script produced randomly.

My problem is that every major problem with SRL and it's dependencies is caused by being so dependent.

A lot of new methods are made and people are just expected to go and learn every new method. I'm sorry but if I'm looking through the SRL include to find skilling or symbol-finding methods, I don't also expect to have to re-learn the fucking Mouse-movement methods and any higher core methods.

Maybe you shouldn't focus on what I said, but my reasons for saying it.

Sjoe, You have some valid points.. I know the need for open source is important to people, but honestly SCAR was pretty perfect as a closed source product.. Also sometimes you can have unwanted results with open source, like jagex insta-banning users of botting programs.
SRL was intended as an "include" with SCAR, an EXTRA, not an invasive group of plugins and programs..

From: KM_01
Also sometimes you can have unwanted results with open source, like jagex insta-banning users of botting programs.

We're not that important in jagex' eyes. They are mainly after powerbot since they make heaps of money thru rsbotting.
You'll see that powerbot has a significant decrease in users because of this, jagex took them down hard.
Atm I'm botting with simba, and it's 'pretty' safe.

Yea, we should probably update the tutorials… @YoHoJo; Go!

From: Zyt3x
Yea, we should probably update the tutorials… @YoHoJo; Go!

atleast delete the outdated ones, I find a bit annoying aswell :(

I can understand what your saying, Like whenever Ive came back (once a year maybe) I re make my scripts in a simpler way, but every time I have came to do that, it takes a bit of work to get the darn thing to compile. Well maybe not too long, like 15-30 minutes of searching around, viewing current working scripts! and learning how they get there script to work. But you need to understand, the include is becoming alot more efficient and due to that comes complexity and changes.

And new is always good, changes things up, makes things more interesting!

Sorry for the disrespect.. It's not very appropriate for these forums, I know the community mentality here is to help each other out.

I guess the purpose of this thread was to vent a little and discuss some important factors of macroing which are being overlooked..

KM,

I can understand your frustration but I find your rant to be a little misguided.

Everything you download from this site is a gift that someone else has freely offered you. Since you didn't pay for it or contribute in any way, you have no basis for complaining. Don't use it if you don't like it. No one is forcing you to accept this generous gift of someone else's time and labor.

I was taught that it's impolite to complain about a gift. My Grandma, God bless her soul, used to give me toys for 7 year olds when I was a late teenager. I would say, "Wow, thanks Grandma. I love you". Then I would give the toy to some kid who would play with it. Should I have said, "Grandma, this is crap. I wouldn't play with this. Keep it, I don't want it"? That would be pretty rude, wouldn't it?

I am very grateful for the free tools I have obtained from this site. I'm productively writing scripts and I have no issues with the hiccups and warts that come with working with a new system. If I want a woodcutting script and no one has updated their old one, I will update it for myself. Or, even better, just write my own. I'm not going to post complaints about how I can't just wander in here and download one.

RS3 and the interface changes managed to break a great percentage of the old library. The people who put in their free labor to create a new library for us made the decision that the old library was a cluttered mess of functions. It was a good opportunity to design a much cleaner implementation. I support this decision. Anyone with a programming background can see that SRL6 is orders of magnitude better in terms of design and implementation.

I agree with the idea you presented. It would be nice to have a compatibility library where many of the old SRL5 functions could be called without modification. This might ease the amount of work needed to get older scripts operating again.

What I disagree with is the impression that someone has slighted you by not providing this. If you're not willing to put your own time and energy into it I don't see why anyone should care if you are unhappy.

There are too many people posting complaints and too few actually participating. The library has been out for a while now but almost no one has updated and re-released their scripts. Wizzup and Olly are the only people I've seen put any time into the codebase, yet I see dozens of member accounts logging into the web site every day.

Perhaps if we can revitalize the spirit of participation we can get a nicer base of tools to work with. I, for one, am planning on sharing my efforts with the community and trying to foster improvement. I encourage others reading this to do the same.

Wow. This thread has struck a nerve with me on several levels. It goes a long way toward expressing my own lack of activity here. What I have to say here is not pointed at any person or group, it is merely my personal observation. So, please don't invite me to leave the community.

I've been a member of this community since May '12. During my initial join, I looked around, read posts, read (and used) other people's scripts, wrote my own (no, nothing was released), and realized that the core code of SCAR / Simba / SRL / etc. was beyond my ability to help with. Not my fault really. I'm in my "Autumn" years, don't have a programming degree, work full time, have a family, etc. While I would like to dig into the code base and see what is really going on, I have neither the time, nor the real inclination, to do so. As such, I am dependent on the efforts and knowledge of others. @bonsai has very eloquently stated that this is a gift and one should be grateful for gifts.

However, with this latest set of changes wrought by the rollout of RS3, I am even less able to keep up with the changes implemented in SRL6 and the rest. From what I see, the changes are good and aimed at cleaning up the old and overlaying a better methodology to scripting. But, there is CURRENTLY a huge lack of support for those changes (this, I know, will change), and, as both @Sjoe and @Zyt3x have pointed out, the mixture of old and new tutorials is dizzyingly confusing. This DOES go a VERY long way toward displacing and discouraging those of us who want to write our own scripts but don't have the time to pour over the new code base.

Please, don't get me wrong. I understand that it will take time to write new tutorials and it will take time, even for those who have degrees and such, to process all the changes that have been put in place. We all have lives outside of RS and this community. But, @KM_01's rant, though somewhat crude and angry, exposes frustrations some of us who do not have the expertise to modify the code base, perhaps more than some of us, feel. In order to

From: bonsai
….revitalize the spirit of participation [so] we can get a nicer base of tools to work with….

folks need to understand that not everyone is capable of modifying the code base and most folks that come here probably aren't capable of modifying even the script files. They attempt to use a script, it fails, they cannot find meaningful support to make it work, they leave. Maybe they check back from time to time, but the community will be anything but revitalized.

I admit that I was a user of 3 scripts. I did not contribute any scripts to the community because I don't have the time to write one that would be sufficiently safe for others to use. I do use my own scripts, however. I search the forum threads diligently for answers. And, if you'd care to look, I've made a contribution or two through comments and help I've given to others. I'm no Great Leader, but I'm not a passive consumer either.

If you really want this community to be revitalized and if you really want it to be a happy, helpful place, then you need to understand what your client base is. You need to know what your membership is actually composed of. I have no idea, but how many folks fall into these three categories: registered users, junior members, members? How many of the members have become members since the release of RS3? Compare that join rate to the rate prior to the re-write of Simba and the rest. My bet is that the conversion rate from junior to full membership has dropped significantly. And that rate will continue to drop until folks can make sense of the tools this community has gifted us with.

This is all a slow process, but I have felt that there is a widening gap between those who know what is going on here and those who do not. Forum threads are mixed with RS3, OSRS, PSRS, old questions, new questions, outdated tutorials, beginnings of new tutorials, ….. It is difficult to navigate around and know what will be helpful and what will not. Personally, I have no interest in OSRS or PSRS, though they are freely mixed with RS3 posts, and if a thread was started prior to September '13, I don't bother to read it because the information will be mostly outdated or contradictory.

How can this be changed? I have no solid ideas. However, I do feel that even as there was a plan to RE-WRITE the old code base, there needs to be a plan to IMPLEMENT the new. Scouring the forums of old, outdated posts (not just scripts) would be very helpful. A comprehensive, centralized thread explaining the changes and what is being done to help folks understand those changes would be helpful. Maintaining a separation of posts based on RS version and use would be helpful. There are any number of things that could be done that would be helpful. But, until folks step up and volunteer to do positive things to help integrate the new way of doing business, frustrations and loss of community will mount.

Well, I think I've said about enough for now. I'm sure some of you will blast me and tell me to leave if I don't like the way things are. If you feel the need to do that, re-read my post and reconsider what I am actually saying. I'm NOT condemning the community. I am certainly not criticizing the devs or those who have put countless hours into making this set of tools such an incredible system. You guys are GREAT. I am saying that with these changes in the code, there needs to be a change in the community that is as holistic as possible. Otherwise, the community will die. And that, in my humble opinion, would be a great shame.

From: KM_01
Hello SRL Community. I supported this community as a developer back when OSR was the only runescape, but I've been having a terrible time trying to understand the new way of doing things, so I'm giving an honest opinion from an old school scripter..

Over three 3rd party program/plugins are required to operate SCAR (re-named to SCAR Divi, re-named to Simba/SMART/Whatever).. Not a good direction to go in.. A single respectable program is sufficient for colour and macro-based application.

I started trying to get simba working a few months ago, the guides were not only out-dated.. The program didn't even work correctly, updating newer SRL/plugin/ext versions with older ones and parts of something called SPS were required to run (although from what I immediately learned in forum posts, SPS is no longer used in the actual program)
When I finally got setupSRL(); script to call, other methods had not been declared and I had to delete large sections of code relating to screen-co-ords or non-existant methods being called from within SRL's core files.. (SMART loaded but did not deliver a single promise of not-using the active mouse, or even working without being disabled)

So anyway, I was using just mouse-methods (thank you benland100) from SRL and I had to use old methods of colour-finding to make any scripts I wanted. It was all working as well as I could hope for a few months, then something was updated.. Now I had to re-install again basically, there are no scripts for this new version (v6 as it's only come out just now) and the simple script I had made before doesn't work now because SMART client was changed and co-ords/colours are all different. (Forcing the end-user to also do a re-write)

You have done to SRL, what runescape did with their terrible updates.. It's all ruined..
The founding fathers of RS cheating certainly did not imagine such a convoluted, complex system which (in frequent updates) renders all scripts made with previous versions completely useless.
Make something which doesn't need to be completely re-written over and over again in the search for a perfect SYNTAX
The greatest programs flaunt their ability to continue working when someone tries to jam the gears.

One piece of advice I would give is that when you change something, leave the old call there.. Or even better, make the old method call the new method. The goal is for every well-written script to continue working for all time. Example below.

MMouse(oldx, oldy, true);
begin
if(true = true)
  begin
    StupidChanges(oldx, oldy, 4x4.TPA, LeftClick.Extended[2,0,0.53]);
  end else
  begin
    StupidChanges(oldx, oldy, 4x4.TPA, RightClick.Extended[1,0,4.89]);
  end;
end;

SCAR is not Simba, Simba is our own open source program where as SCAR is closed source and hardly updated.

You do realize that SRL 6 is a complete rewrite from SRL 5, right? SRL 6 is also written in Lape, which is much better than any of the previous SRL versions. You obviously don't do any real world programming, due to a lot of major version number releases of code bases get rid of methods.

You're comparing SRL to a botting only forum. We are not a botting forum, we are a learning community. We bot because we have a game in common. The language honestly isn't that hard to pick up. It does take some time, but once you know the syntax, you're golden.

Why would you leave the old methods there? Or even make a wrapper for the old one? That's what SRL 5 did, and I'm pretty sure SRL 6 does this in a few places (Haven't looked at it in a long time). All that does is clutter the code base up, and no need to keep depreciated methods when it can be done better.

From: KM_01
Actually, Zytex, I cut my teeth on finding other uses for SCAR. I wrote a script which printed a form of sheet music to debug which the script produced randomly.

My problem is that every major problem with SRL and it's dependencies is caused by being so dependent.

A lot of new methods are made and people are just expected to go and learn every new method. I'm sorry but if I'm looking through the SRL include to find skilling or symbol-finding methods, I don't also expect to have to re-learn the fucking Mouse-movement methods and any higher core methods.

Maybe you shouldn't focus on what I said, but my reasons for saying it.

Sjoe, You have some valid points.. I know the need for open source is important to people, but honestly SCAR was pretty perfect as a closed source product.. Also sometimes you can have unwanted results with open source, like jagex insta-banning users of botting programs.
SRL was intended as an "include" with SCAR, an EXTRA, not an invasive group of plugins and programs..

Really? I've used Simba outside of RS plenty of times. I've made bots to vote in polls, that even had to login and scroll. You can use it for pretty much anything.

SRL is only dependent on botting, but you could also bot RS without SRL.

Yeah, new methods are created, you learn to use them. That's how programming in any language goes, why would you want to keep using old methods when new ones are much better? And if you didn't take the time to learn the differences between SRL 5 and 6, and what all was changed, then all this frustration is on you and nobody else.

SCAR was far from perfect, and was hardly updated. RS was changing, but we couldn't do what we needed because of the limitations of the program.

Please tell me how SRL is still not an include? You can install Simba and never need the use of SRL. SRL is honestly for RS only, and if you want to do things outside of RS, you don't need the SRL Include.

I honestly think you are way off in your thoughts, and nowhere near the actual truth. But that's just my opinion.

Have there been postings deleted from this thread? I have two notifications about replies here and neither is actually here?

From: loragnor
Have there been postings deleted from this thread? I have two notifications about replies here and neither is actually here?

There was 1 post and it was removed by the user.

I completely understand your frustration; thanks for expressing your thoughts. :)

I'm not going to comment on SCAR vs. Simba since it's ancient news, and I had very little to do with the change; I'll focus on your comments about SRL's compatibility with old scripts. Perhaps we should have discussed backwards compatibility a little more, but the move to SRL-6 changed interpreters, which brought with it changes in syntax and features. SRL-5 was a mess - there were countless outdated, broken, and misleading methods. This was a major reason why we decided to delete or rename a lot of them. That along with a completely new structure.

Not to mention with the release of RS3, basically everything in SRL-5 broke. This was our chance to finally evolve and make SRL into something better. Something that isn't limited by screen size, safe mode, or interface layout (it's still limited now, but it won't be in the future). It was turned into something much, much better, even if you don't see it right now.

A big mistake, which I will take full responsibility for is our lack of guidance to script with SRL-6. We have a setup tutorial (which is completely up to date, so I'm not sure what guide you were referring to), and it doesn't require separate downloads. You need to install Simba and enable a couple extensions - that's it. Anyway, we do need a thorough guide on scripting with SRL-6 and Lape. I do plan on updating my Beginner's guide for Lape, and I'd like to write an SRL-6 guide; however, I am very very busy and honestly don't know if I'll have time anytime soon.

So anyway, I understand your frustration, but I believe what we've done is better for SRL. It may not seem like it now, but as long as people still play RS3, we'll have people to script for it.

I believe loragnor covered pretty much everything I was trying to say..

I was trying to set up simba about a month or 2 ago, so I understand how a lot of SRL core features might've been rendered useless by rs3 updates.. But the v5 simba-setup documentation made it really unpleasant to figure out if I'd set up correctly. (In the v6 edits, I think I still saw the same stuff about setting up SPS and extensions (the extensions caused me the most frustration because sometimes the updater wouldn't find any version above 1 for SRL or SPS or the plugins))

I don't need to discuss anything more about SCAR vs. Simba because my only issue with the program itself is the tangled mess of unnecessary extras which waste disk space, they're hard to set up and confuse users.

I've been thumbing throught the v6 features and it all works well, but I guess I was trying to say that it's hard to understand Tpoints and Tbox's if you haven't seen them before.. In about 5 seconds (after a google search) I realised that a Tbox is as easy as

IntToBox(1, 2, 3, 4);

and Tpoints are just

Point(420, 420);

So I was able to easily understand and use the new methods..
Just not sure that you have gone about that the right way.. I appreciate it when things are very straight-foward in programming (it encouraged me to have a crack even though I'm just some normal guy and no super geek).. I like my mouse movements to use X and Y.. If you are going to make "Higher" methods for "Higher" levels of understanding then supersede the methods like (AdvancedMouse(Point(1, 2))), don't mess with the standard methods..
Something else that kinda ties into that too is that you effectively increased the length of script in my re-write of a simple script.
by changing the Dragmouse method from Dragmouse(startx1, starty1, startx2, starty2, endx1, endy1, endx2, endy2) to Dragmouse(Point(1, 2)).
Sure this made things look neat and tidy on your end, but now to do that I have to use a mousebox (converting normal co-ords to a seemingly pointless Tbox) then a dragmouse (doubling the amount of end-user code needed).. It's not much I know.. But this is not inviting to someone who might join the community. It's not user friendly

I will just state now that I respect all the hard work that's been done to still be here after so long, and everyone who is a part of the community. I know that you guys all have skills probably much greater than what I mess around with in my spare time, but I think you should keep priorities in order and don't forget that you have to keep simple things simple, or average people won't realise how easy it is to learn scripting and make an effort to try it out.

Thank you for your explanation, Coh3n..

From: KM_01
I believe loragnor covered pretty much everything I was trying to say..

I was trying to set up simba about a month or 2 ago, so I understand how a lot of SRL core features might've been rendered useless by rs3 updates.. But the v5 simba-setup documentation made it really unpleasant to figure out if I'd set up correctly. (In the v6 edits, I think I still saw the same stuff about setting up SPS and extensions (the extensions caused me the most frustration because sometimes the updater wouldn't find any version above 1 for SRL or SPS or the plugins))

I don't need to discuss anything more about SCAR vs. Simba because my only issue with the program itself is the tangled mess of unnecessary extras which waste disk space, they're hard to set up and confuse users.

I've been thumbing throught the v6 features and it all works well, but I guess I was trying to say that it's hard to understand Tpoints and Tbox's if you haven't seen them before.. In about 5 seconds (after a google search) I realised that a Tbox is as easy as

IntToBox(1, 2, 3, 4);

and Tpoints are just

Point(420, 420);

So I was able to easily understand and use the new methods..
Just not sure that you have gone about that the right way.. I appreciate it when things are very straight-foward in programming (it encouraged me to have a crack even though I'm just some normal guy and no super geek).. I like my mouse movements to use X and Y.. If you are going to make "Higher" methods for "Higher" levels of understanding then supersede the methods like (AdvancedMouse(Point(1, 2))), don't mess with the standard methods..
Something else that kinda ties into that too is that you effectively increased the length of script in my re-write of a simple script.
by changing the Dragmouse method from Dragmouse(startx1, starty1, startx2, starty2, endx1, endy1, endx2, endy2) to Dragmouse(Point(1, 2)).
Sure this made things look neat and tidy on your end, but now to do that I have to use a mousebox (converting normal co-ords to a seemingly pointless Tbox) then a dragmouse (doubling the amount of end-user code needed).. It's not much I know.. But this is not inviting to someone who might join the community. It's not user friendly

I will just state now that I respect all the hard work that's been done to still be here after so long, and everyone who is a part of the community. I know that you guys all have skills probably much greater than what I mess around with in my spare time, but I think you should keep priorities in order and don't forget that you have to keep simple things simple, or average people won't realise how easy it is to learn scripting and make an effort to try it out.

Thank you for your explanation, Coh3n..

We can add overloaded methods in Lape if we wanted. I've thought about this a couple times. So we could have a version of Mouse() that takes a TPoint and a version that takes X/Y coordinates.

I honestly wouldn't mind it, but some people might think that's just cluttering up the include. If the other developers agreed, I wouldn't have a problem with it, especially if it made things easier for the end user.

From: KM_01
Hello SRL Community. I supported this community as a developer back when OSR was the only runescape, but I've been having a terrible time trying to understand the new way of doing things, so I'm giving an honest opinion from an old school scripter..

Over three 3rd party program/plugins are required to operate SCAR (re-named to SCAR Divi, re-named to Simba/SMART/Whatever).. Not a good direction to go in.. A single respectable program is sufficient for colour and macro-based application.

I started trying to get simba working a few months ago, the guides were not only out-dated.. The program didn't even work correctly, updating newer SRL/plugin/ext versions with older ones and parts of something called SPS were required to run (although from what I immediately learned in forum posts, SPS is no longer used in the actual program)
When I finally got setupSRL(); script to call, other methods had not been declared and I had to delete large sections of code relating to screen-co-ords or non-existant methods being called from within SRL's core files.. (SMART loaded but did not deliver a single promise of not-using the active mouse, or even working without being disabled)

So anyway, I was using just mouse-methods (thank you benland100) from SRL and I had to use old methods of colour-finding to make any scripts I wanted. It was all working as well as I could hope for a few months, then something was updated.. Now I had to re-install again basically, there are no scripts for this new version (v6 as it's only come out just now) and the simple script I had made before doesn't work now because SMART client was changed and co-ords/colours are all different. (Forcing the end-user to also do a re-write)

You have done to SRL, what runescape did with their terrible updates.. It's all ruined..
The founding fathers of RS cheating certainly did not imagine such a convoluted, complex system which (in frequent updates) renders all scripts made with previous versions completely useless.
Make something which doesn't need to be completely re-written over and over again in the search for a perfect SYNTAX
The greatest programs flaunt their ability to continue working when someone tries to jam the gears.

One piece of advice I would give is that when you change something, leave the old call there.. Or even better, make the old method call the new method. The goal is for every well-written script to continue working for all time. Example below.

MMouse(oldx, oldy, true);
begin
if(true = true)
  begin
    StupidChanges(oldx, oldy, 4x4.TPA, LeftClick.Extended[2,0,0.53]);
  end else
  begin
    StupidChanges(oldx, oldy, 4x4.TPA, RightClick.Extended[1,0,4.89]);
  end;
end;

Can't talk here but I have to say this

SRL was made a long time ago… runescape has changed.. programming has changed… computers have changed… simba….a lot of things have. SRL needs to start fresh… I see code in there that is being recycled from 7 years ago. Start fresh guys

Peace out

From: Wanted Returns
Can't talk here but I have to say this

SRL was made a long time ago… runescape has changed.. programming has changed… computers have changed… simba….a lot of things have. SRL needs to start fresh… I see code in there that is being recycled from 7 years ago. Start fresh guys

Peace out

Feel free to point out non working code that has been in srl-6 for 7 years,

From: Olly
Feel free to point out non working code that has been in srl-6 for 7 years,

Where did I say 'non working' … sigh… feel free to contact me.

=/

As much as I agree with OP's argument that core API updates must be backward compatible, saying that SRL should do away with 3rd party plugins is nonsense.

From: Zyt3x
Yea, we should probably update the tutorials… @YoHoJo; Go!

Planning on it eventaully. I have an up to date install video for EoC, not sure about the state of the 07 include but I'll be making one for that one there is an (un?)official one that works well/is updated often etc.

From: Sjoe
atleast delete the outdated ones, I find a bit annoying aswell :(

What is annoying?
I added [outdated] to all (only 2 or 3?) of my tutorials which are now out of date, but kept them up for educational purposes.
I think a lot of the tutorial section at SRL is now out of date and a new sub-forum should be created for the outdated (yet still educational) tutorials.

From: YoHoJo
Planning on it eventaully. I have an up to date install video for EoC, not sure about the state of the 07 include but I'll be making one for that one there is an (un?)official one that works well/is updated often etc.


What is annoying?
I added [outdated] to all (only 2 or 3?) of my tutorials which are now out of date, but kept them up for educational purposes.
I think a lot of the tutorial section at SRL is now out of date and a new sub-forum should be created for the outdated (yet still educational) tutorials.

I agree completely with YoHoJo. In fact, when I started with SRL it was his vid tutorials that really got me going. The old tutorials should be kept for programming educational purposes. But we are in dire need of new tutorials. I still consider myself a beginner in programming. I play RS periodically and always come back here to write my scripts. I find it very frustrating that my old scripts are too far gone now (even only after 3 months), and that I do not know enough about LAPE to get started given the limited number of tutorials.

I just hate how every time I stop botting for a while then go to start again theres like 10 different includes i have to download and update then a new smart i have to to download and put in the right folder then there's always a smartparams or something wrong thats giving an error in the smart file that basically makes me give up and not give a shit about srl anymore

and now everythings going to lape which i dont feel like getting used to and everythings different in srl6 so goodbye villavu

From: Nebula
I just hate how every time I stop botting for a while then go to start again theres like 10 different includes i have to download and update then a new smart i have to to download and put in the right folder then there's always a smartparams or something wrong thats giving an error in the smart file that basically makes me give up and not give a shit about srl anymore

and now everythings going to lape which i dont feel like getting used to and everythings different in srl6 so goodbye villavu

:( lape is pretty much the same though.
U can just code pascal style

From: KM_01
I believe loragnor covered pretty much everything I was trying to say..

I was trying to set up simba about a month or 2 ago, so I understand how a lot of SRL core features might've been rendered useless by rs3 updates.. But the v5 simba-setup documentation made it really unpleasant to figure out if I'd set up correctly. (In the v6 edits, I think I still saw the same stuff about setting up SPS and extensions (the extensions caused me the most frustration because sometimes the updater wouldn't find any version above 1 for SRL or SPS or the plugins))

I don't need to discuss anything more about SCAR vs. Simba because my only issue with the program itself is the tangled mess of unnecessary extras which waste disk space, they're hard to set up and confuse users.

I've been thumbing throught the v6 features and it all works well, but I guess I was trying to say that it's hard to understand Tpoints and Tbox's if you haven't seen them before.. In about 5 seconds (after a google search) I realised that a Tbox is as easy as

IntToBox(1, 2, 3, 4);

and Tpoints are just

Point(420, 420);

So I was able to easily understand and use the new methods..
Just not sure that you have gone about that the right way.. I appreciate it when things are very straight-foward in programming (it encouraged me to have a crack even though I'm just some normal guy and no super geek).. I like my mouse movements to use X and Y.. If you are going to make "Higher" methods for "Higher" levels of understanding then supersede the methods like (AdvancedMouse(Point(1, 2))), don't mess with the standard methods..
Something else that kinda ties into that too is that you effectively increased the length of script in my re-write of a simple script.
by changing the Dragmouse method from Dragmouse(startx1, starty1, startx2, starty2, endx1, endy1, endx2, endy2) to Dragmouse(Point(1, 2)).
Sure this made things look neat and tidy on your end, but now to do that I have to use a mousebox (converting normal co-ords to a seemingly pointless Tbox) then a dragmouse (doubling the amount of end-user code needed).. It's not much I know.. But this is not inviting to someone who might join the community. It's not user friendly

I will just state now that I respect all the hard work that's been done to still be here after so long, and everyone who is a part of the community. I know that you guys all have skills probably much greater than what I mess around with in my spare time, but I think you should keep priorities in order and don't forget that you have to keep simple things simple, or average people won't realise how easy it is to learn scripting and make an effort to try it out.

Thank you for your explanation, Coh3n..

From: Coh3n
We can add overloaded methods in Lape if we wanted. I've thought about this a couple times. So we could have a version of Mouse() that takes a TPoint and a version that takes X/Y coordinates.

I honestly wouldn't mind it, but some people might think that's just cluttering up the include. If the other developers agreed, I wouldn't have a problem with it, especially if it made things easier for the end user.

Just gonna note, Lape can also take a static array of two integers as a TPoint. [ Mouse([my_x, my_y], MOUSE_LEFT); ]

Or any record type for that matter, a TBox is just a record with 4 integers, an array of 4 integers can be used.

There is actually no point in the Point and IntToBox methods….

Point(x, y) => [x, y] (they are the same thing, the method actually uses more cpu cycles prob…)
IntToBox(x1, y1, x2, y2) => [x1, y1, x2, y2]