SRL Archive - S.M.A.R.T. Questions and Answers.

I've read numerous posts on the forums claiming that SMART was detectable by Jagex, but Jagex just hasn't tried detecting it yet.

1) Would we be able to notice if Jagex tried to detect SMART?
2) Would bypassing the detection be possible?

Im not 100% sure but i dont think Jagex can detect Smart as it doesnt inject into Runescape in anyway.

Its just like Swiftkit.

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

I read that thread and many others that claimed that it can be detected, but isn't currently detected.

We don't really know if they are currently detecting it or not. It's a catch 22.

Yeah they are saying it's POSSIBLE for Jagex to detect it since we are loading it in an old/improper way.

A fix is actually already made thanks to brandon's hard wrk, Simone just needs to accept the request so it can be added to SRL, I have it :).


Overall I think all is fine, but better safe than sorry!!!

You'll know if there is a mass ban :P

You'll know if you get a mass ban happening on this site.. and Mormanman also helped a ton with that fix. Ben simplified some stuff. So shout out to them too. Just gotta wait on someone to review and push it :S

Time to play the waiting game.

It's not about just reviewing it and merging it, it's about the impact it will have once it's merged ;)

From: Kyle Undefined
It's not about just reviewing it and merging it, it's about the impact it will have once it's merged ;)

It was made so not much/anything needs to really be changed.
Just a line or two if anything.
Except it's not 100% done just yet, paintsmart doesn't work yet all the way.

It's pretty nice :D RemoteSmart FTW.

From: Kyle Undefined
It's not about just reviewing it and merging it, it's about the impact it will have once it's merged ;)

Yes removing the Smart_Server and stuff will impact many scripts and cause noobs to post all over the place asking how to fix it but leaving it there is useless.. Leaving support for the versions lower than 7.1 is much harder to maintain.

It's only 4 lines to remove but I see where you're coming from then again:

Saving Parameters then loading them from a file, keeping track of a timer for the 6hr limit in which a parameter may or may not expire, keeping track of a current parameter so that smart does not close when play is pressed again, etc..

Whereas the new version just passes it directly, once, and that's it. I honestly don't mind leaving the old way in there. Mormanman doesn't want it and I'm pretty certain Ben would prefer just calling get params and passing it instead of keeping track but I don't mind.

Either way if I leave the old one in there, something has to give.

It'd be {$DEFINE SMART} for LibSmart32 vs. {$DEFINE SMARTREMOTE} for LibSmartRemote32 whereas it can be removed and just be {$DEFINE SMART} for the latest.

Anyway if no one wants smart_server and stuff removed then I still have a backup of the previous push so I can just replace it if needed. Don't have to write anything new.

the way i see it is many people bot on the mains with smart (including myself) and no bans if your going to brake the rules expect a ban 2 when doing so!

From: Brandon
Yes removing the Smart_Server and stuff will impact many scripts and cause noobs to post all over the place asking how to fix it but leaving it there is useless.. Leaving support for the versions lower than 7.1 is much harder to maintain.

It's only 4 lines to remove but I see where you're coming from then again:

Saving Parameters then loading them from a file, keeping track of a timer for the 6hr limit in which a parameter may or may not expire, keeping track of a current parameter so that smart does not close when play is pressed again, etc..

Whereas the new version just passes it directly, once, and that's it. I honestly don't mind leaving the old way in there. Mormanman doesn't want it and I'm pretty certain Ben would prefer just calling get params and passing it instead of keeping track but I don't mind.

Either way if I leave the old one in there, something has to give.

It'd be {$DEFINE SMART} for LibSmart32 vs. {$DEFINE SMARTREMOTE} for LibSmartRemote32 whereas it can be removed and just be {$DEFINE SMART} for the latest.

Anyway if no one wants smart_server and stuff removed then I still have a backup of the previous push so I can just replace it if needed. Don't have to write anything new.

I agree, the implementation you have come up with is perfect and I really do like it. It's needed, but will break almost every script out at the moment :p I guess sometimes you have to break things in order to lookout what's best for a person (In this case the community and their accounts).

I have no problem merging this as is, was just pointing what I know will happen once it is :p Seeing as I'm a "new" developer, I don't want to break stuff so soon, so that's my hesitation on the matter.

Another dev can merge it, or someone higher up can tell me to merge it and I'll do it instantly. As long as we are all on board of the changes and the impacts of it :)