SRL Archive - General

I was just thinking.

Not too long ago I made a post in mods', about every rank needing more benefits. Right now juniors get all the scripts and there is no (script) incentive to move up the ranks.

This is because juniors are the main testers, and people want feedback on their scripts.

Well, MSI can overcome that.

As MSI gets more and more scripts, and more and more skills and etc,
we get loads of feedback.

And we don't need people to be using a specific script, because our functions are generalized.

If you failed at mining coal in the lumby swamps, you'll also fail at mining coal in the guild.

Our feedback is interchangeable.

Furthermore, we can release scripts in under 10 lines with the script record.


We can choose who we release which scripts to.
Let's face it, if people want to make their own paths and stuff they can, but most likely they won't.

So if we choose to release MSI Guild Miner and MSI Guild Fisher to members only, all of a sudden members will have two of the best scripts available only to them,
and everyone will know about it.

We can give SRL Members something special to have on their own.


Of course we can also give the script record to big autoers who run msi like squancy. That wouldn't hurt us at all, infact it'd most likely do us good.


But yeh. With MSI we can easily make unique scripts available to unique people.

What do you guys think of this?

~RM

I like it, except it's pretty easy to leak a script record.

I highly doubt anyone would, but you never know.

Great idea! :)
Will courage more people to learn how to script for sure

Only problem is… How would we go around doing something like this?

Script Manager could be implemented to ship out text files with the records in them.. Would work :)

OR you just have a script shipped that includes all the player info etc and you just run from the file with the record.

I like it.

As long as we enforce leaking script records the same as leaking scripts, I don't think we will have any problems.

"So if we choose to release MSI Guild Miner and MSI Guild Fisher to members only,"
This would make me sadface

"Of course we can also give the script record to big autoers who run msi like squancy. That wouldn't hurt us at all, infact it'd most likely do us good."

Happyface?


—

Regardless, I like the idea, despite not being a 1337 member who makes full scripts
Gives people incentive to make great scripts and help the community.

Release to MSI Devs/SLs? Then again, I'm pretty sure I'm the only Junior member SL….

From: nickrules
"So if we choose to release MSI Guild Miner and MSI Guild Fisher to members only,"
This would make me sadface

"Of course we can also give the script record to big autoers who run msi like squancy. That wouldn't hurt us at all, infact it'd most likely do us good."

Happyface?


—

Regardless, I like the idea, despite not being a 1337 member who makes full scripts
Gives people incentive to make great scripts and help the community.

Release to MSI Devs/SLs? Then again, I'm pretty sure I'm the only Junior member SL….

Your not a Jr. Member? and your not an SL..?

From: NCDS
Your not a Jr. Member? and your not an SL..?

Im not a junior member? when did this happen?

From: nickrules
Im not a junior member? when did this happen?

Oh, wow. You didn't notice you got auto-memberized? :D
You're one of the few persons that this has happened with :)

From: Zyt3x
Oh, wow. You didn't notice you got auto-memberized? :D
You're one of the few persons that this has happened with :)

Hence the yellow name..

and the member forums… but we're going out of topic :p

~RM

From: NCDS
Hence the yellow name..

Duh, I know that.. What are you getting at?

On-topic: I think the second option Nava2 posted would be the best method.
The bad thing about this, is that if a record has ever been leaked, then it'll probably work even after numerous runescape updates due to MSI being so stable and clean… So once (if ever) the records is leaked, it would be the end of members only MSI scripts…

From: Zyt3x
Duh, I know that.. What are you getting at?

I was more so adding to your post, but addressing nick ;)

From: Zyt3x

On-topic: I think the second option Nava2 posted would be the best method.
The bad thing about this, is that if a record has ever been leaked, then it'll probably work even after numerous runescape updates due to MSI being so stable and clean… So once (if ever) the records is leaked, it would be the end of members only MSI scripts…

Other things would be needed for the scripts other than just the script records though. For example, Guild Miner/ fisher is going to require obstacle handling. I believe, with the method RM is using the obstacles will require they're own records generally as well.

Anyone that knows how/where to put records in MSI is or could be a members anyways I would imagine.

I'm sure there are a number of possible ways to prevent any leaking, but it's time to eat now :)

Okay guys, I have managed to finish a working Guild Miner. The obstacle handling works flawlessly with color, but I've added that extra reflection check that we've been discussing. If you look at the code, the reflection actually made it a lot longer and more complicated. :p Color was the one that took up only a few lines. The only thing it needs is a way to detect if someone else is mining or not.

Do we still want to release to Members+? I'll make the full release probably sometime in the next couple days, after I can test some more and figure out how to detect if the rock is already being mined.

Also, we should still add Guild Miner to the Miner's Supported Locations thread and just say it's available to SRL Members+. Maybe MSI's Member+ scripts will give someone some incentive to learn to script. :)

Last thing, I'm thinking that everything for the Guild Miner will be committed except the actual script record. That includes all the obstacle handling routines (which we'll need for other obstacles anyway).

What do you guys think?

Scripts will get leaked regardless…

Commit everything except for the actual TScript I'd say :)

If anyone leaks the script they'll be banned. That's how it used to work, that's how it'll work now.

And yeah, I'd say release it to SRL Members + :)

And good job on getting the guild miner done!

~RM

From: Sir R. Magician
Commit everything except for the actual TScript I'd say :)

If anyone leaks the script they'll be banned. That's how it used to work, that's how it'll work now.

And yeah, I'd say release it to SRL Members + :)

And good job on getting the guild miner done!

~RM

Sounds good, and everything is committed so far. I got my army running last night and I've managed to find and fix (still testing some) several bugs, so that's good. If not today, I'll make the full release tomorrow as I'd still like to do some testing. :)

I agree with RM's post.

As far as checking if the rock is already being mined or not, we could try searching a 20x20px box around the rock the script is about to click and see if PixelShift > WhateverNumberWorks. Just a quick idea.

Looks like we're just ignoring Wizzup?'s post…

Is there a way to incorporate this into the Script Manager to make it unable to leak but still able to use for only SRL Members+?
I am thinking about Username and Password for those who wants higher rank scripts…

From: Zyt3x
Looks like we're just ignoring Wizzup?'s post…

Is there a way to incorporate this into the Script Manager to make it unable to leak but still able to use for only SRL Members+?
I am thinking about Username and Password for those who wants higher rank scripts…

As soon as it is installed someone can simply pastebin it, no?

From: Wizzup?
As soon as it is installed someone can simply pastebin it, no?

Yeah, I were thinking about closed source, but I'm not sure if I like that idea either…

LEAK = BAN.

Simple as that.

And all we have to do to avoid the leak is change the script constant. Any leechers who then try to use it without changing the record (which is likely to happen) would fail.

It will get leaked sooner or later, most likely. But then again it doesn't matter all that much; It's not like we're making money out of it or anything.

SCRIPT_MINER_GUILD
SCRIPT_SRL_MGUILD
SCRIPT_MGUILD
SCRIPT_MGUILD_SRL

just change those around. When the script manager does come around we'll be able to see if SRL Member - are using the script.

And then we can do something about it ;)

~RM

From: Sir R. Magician
LEAK = BAN.

Simple as that.

And all we have to do to avoid the leak is change the script constant. Any leechers who then try to use it without changing the record (which is likely to happen) would fail.

It will get leaked sooner or later, most likely. But then again it doesn't matter all that much; It's not like we're making money out of it or anything.

SCRIPT_MINER_GUILD
SCRIPT_SRL_MGUILD
SCRIPT_MGUILD
SCRIPT_MGUILD_SRL

just change those around. When the script manager does come around we'll be able to see if SRL Member - are using the script.

And then we can do something about it ;)

~RM

I like that idea, but until script manager comes out, perhaps we could use stats to see who is using it one way or another?

From: NCDS
I like that idea, but until script manager comes out, perhaps we could use stats to see who is using it one way or another?

If you wish to.

But I wouldn't put my username down if I was using a leaked script ;)

Leaking is not really a problem here.

We find out it was leaked -> we change constant.
As simple as that ;)

If the person is still using an old constant, stop their script, and tell them their constant is outdated and to check the SRL Members thread.

That'll keep people busy enough until the script manager;
Leaks are natural, leaks happen.

There's no 100% way of doing it, so let's just trust the members ;)

~RM

From: Sir R. Magician

There's no 100% way of doing it, so let's just trust the members ;)

~RM

Yeah, I guess that should be reasonable to ask their trust. :)

Alright :)

Members could also have more things than a script too; better anti-ban… auto responders for those who like that… there's a lot of possibilities

From: Zyt3x
Alright :)

Members could also have more things than a script too; better anti-ban… auto responders for those who like that… there's a lot of possibilities

Yeah, we're only really limited by our own imaginations. :)

http://villavu.com/forum/showthread.php?t=60497

Alrighty, I thought of a way of adding members scripts which would work nicely (I think…)

If MSI had 2 SVNs, one with everything, and the other containing Members_Scripts.Simba

Then a simple {$define memberScripts} in runme would deal with member scripts. Then load scripts from both scripts.simba and members_scripts.simba if its not commented out.

Alternately, we could check if the file exists, and if so, include it…


TL;DR
2 svns, one with a everything and one with JUST members_scripts.simba. Members get the SVN link, non-members would only be provided with the normal link.

From: nickrules
Alrighty, I thought of a way of adding members scripts which would work nicely (I think…)

If MSI had 2 SVNs, one with everything, and the other containing Members_Scripts.Simba

Then a simple {$define memberScripts} in runme would deal with member scripts. Then load scripts from both scripts.simba and members_scripts.simba if its not commented out.

Alternately, we could check if the file exists, and if so, include it…


TL;DR
2 svns, one with a everything and one with JUST members_scripts.simba. Members get the SVN link, non-members would only be provided with the normal link.

It would be easier to leak that way… One link is all they need, and they'll have the script for ever, if we do it like now (release the record / change some bits around for each time we see a leak) then the script would have to be leaked over and over in order for non srl members to use it

Wouldn't need a separate SVN for one file. We can just upload the file on the thread.

Defines is a good idea to include it:

{$IFDEF MEMBERS}
  {$i MSI/Members.simba}
{$ENDIF}

From: Zyt3x
It would be easier to leak that way… One link is all they need, and they'll have the script for ever, if we do it like now (release the record / change some bits around for each time we see a leak) then the script would have to be leaked over and over in order for non srl members to use it

This makes me very sadface. Because the concept of manual downloading bothers me. I'll just think thoughtly thoughts and try to think of something…

Something made in delphi/c++?

Okay so I got around to typing up a long post detailing my thoughts on this situation, but accidentally xed out. So here is the basic idea:

Does anyone remember when Nielsie came out with his Tutorial Island Runner? It had two versions; the SRL Member version, and the non SRL Member version. It had these cool little features in it that made it hard to crack. There were basically limits on how many accounts you could do in the limited version, and unlimited in the Members version. Now, the cracking probably wasn't hard for SRL Members +, but it was made in a way that was hard for anyone with limited knowledge in scripting to figure it out.

He did all this inside one script. MSI has an entire include. The basic goal is to make it reallllly inconvenient for a Jr Member to try and figure out how to upgrade his include to allow him to have Members only scripts. It could require lots of knowledge of the MSI system (if done right) as well as lots of scripting knowledge in itself. By the time the person knew enough to crack the include for themselves, they'd have enough scripting skill to be a Member (in theory).

To counteract any member uploading their entire include (unlikely but maybe) there could be systems limiting the use of the Members things, or a user/pass system which connected to a website (I'm sure that SRL Members trust MSI to connect to a website) which would prevent the use of those who aren't white listed.

I'm just throwing out ideas right now, maybe some of these have been mentioned, who knows.

From: 3Garrett3
Okay so I got around to typing up a long post detailing my thoughts on this situation, but accidentally xed out. So here is the basic idea:

Does anyone remember when Nielsie came out with his Tutorial Island Runner? It had two versions; the SRL Member version, and the non SRL Member version. It had these cool little features in it that made it hard to crack. There were basically limits on how many accounts you could do in the limited version, and unlimited in the Members version. Now, the cracking probably wasn't hard for SRL Members +, but it was made in a way that was hard for anyone with limited knowledge in scripting to figure it out.

He did all this inside one script. MSI has an entire include. The basic goal is to make it reallllly inconvenient for a Jr Member to try and figure out how to upgrade his include to allow him to have Members only scripts. It could require lots of knowledge of the MSI system (if done right) as well as lots of scripting knowledge in itself. By the time the person knew enough to crack the include for themselves, they'd have enough scripting skill to be a Member (in theory).

To counteract any member uploading their entire include (unlikely but maybe) there could be systems limiting the use of the Members things, or a user/pass system which connected to a website (I'm sure that SRL Members trust MSI to connect to a website) which would prevent the use of those who aren't white listed.

I'm just throwing out ideas right now, maybe some of these have been mentioned, who knows.

Hahahaha, that's a really fucking cool idea :p

~RM

Thats a great idea.

My idea was to
1)Have the user enter their username and password for SRL
2)Open a webclient (the way simba does it. Nothing visual. Just a behind-the-scenes sorta thing).
3)Log in to SRL, then visit a thread, which would be placed in the members-only section.

NOTE: If the user is NOT a member, it will automatically redirect to the 'not a member' page, and if they are, it visits the thread (duh)

4)Grab the HTML
5)Search for a specific line of text
6)If the text isn't found, the members_scripts file wont be downloaded. And, of course, if it is, it will be.

Not too complicated (i hope :o). The real trick would be having people trust it.


Alternate would be a simple user/password system on a website. Problem is, we would need a list of the SRL members/people would have to apply to get in. Above method is the same, without a new account (or website)

From: nickrules
Thats a great idea.

My idea was to
1)Have the user enter their username and password for SRL
2)Open a webclient (the way simba does it. Nothing visual. Just a behind-the-scenes sorta thing).
3)Log in to SRL, then visit a thread, which would be placed in the members-only section.

NOTE: If the user is NOT a member, it will automatically redirect to the 'not a member' page, and if they are, it visits the thread (duh)

4)Grab the HTML
5)Search for a specific line of text
6)If the text isn't found, the members_scripts file wont be downloaded. And, of course, if it is, it will be.

Not too complicated (i hope :o). The real trick would be having people trust it.


Alternate would be a simple user/password system on a website. Problem is, we would need a list of the SRL members/people would have to apply to get in. Above method is the same, without a new account (or website)

That was somewhat I was thinking about too, although all you have to do is to login to check the authority and then check the memberlist (which is public too.. http://villavu.com/forum/memberlist.php?&order=asc&sort=posts) for the name and get the color of the person. If the color is something other than jr-green, registered-green or banned-blue then the person is SRL Member +

Wasn't aware of this :o

I suppose it could work. Couldn't we also just check the persons….

Actually, looking now, it has a members online list [on the front page you see when you log in]. We could just check for the persons username and color in that.