SRL Archive - Discussions & Debates

Hey guys. As many of you may know, I'm working on an updated for oldschool. After discussing some things on the irc channel, I need some information. I'm going to start writing the srl reflection include, and I want to know, is it going to be a full include, or will it only have the things that it's difficult to do in colour. Leave a vote and a comment.

Well the include is already written and still exists on Github, actually only a little modification is needed to adjust it for OSRS. With that aside, but Pyroryan and I agree the available reflection include should be quite limited to prevent the obvious from happening. IMO only our player data & map data would need to be hooked. Anything else shouldn't be an issue via color.

From: Flight
Well the include is already written and still exists on Github, actually only a little modification is needed to adjust it for OSRS. With that aside, but Pyroryan and I agree the available reflection include should be quite limited to prevent the obvious from happening. IMO only our player data & map data would need to be hooked. Anything else shouldn't be an issue via color.

Why limit it though.. If reflection can do everything already and with ease, why limit the include to only two-three hooks. There's already injection bots that aren't limited. Limiting the include would be a bad idea.

I say make it unlimited and those who don't want to use the whole include can just use colour if they wish.

Full include FTW

I voted for Full include, there are somethings that are just better be done with Reflection than color/ocr.

Won't mean people will stop using Color, it would just makes the script run better.

i only need a few things: some npc information, player information, random events and walking.

From: Flight
Well the include is already written and still exists on Github, actually only a little modification is needed to adjust it for OSRS. With that aside, but Pyroryan and I agree the available reflection include should be quite limited to prevent the obvious from happening. IMO only our player data & map data would need to be hooked. Anything else shouldn't be an issue via color.

Well, what I meant by 'write' the include is package the hook paths for it into a file, and fix up a patch for it.
If it is just part of an include, I can get some hooks out pretty soon.

I agree with @Brandon. There's no advantage to restricting what can be done with reflection. I'd be surprised if loads of new scripts don't get released when a fully fledged reflection include is up and running. I'd expect more scripts, which would mean more activity. Surely that's a good thing? You could release an initial slimmed down version to do, as you said, what's difficult in colour and release the rest in an update at a later date? Just an idea.

From: Rich
I agree with @Brandon. There's no advantage to restricting what can be done with reflection. I'd be surprised if loads of new scripts don't get released when a fully fledged reflection include is up and running. I'd expect more scripts, which would mean more activity. Surely that's a good thing? You could release an initial slimmed down version to do, as you said, what's difficult in colour and release the rest in an update at a later date? Just an idea.

That's what I was thinking, I'll start off with what I have, then add more as it goes along.

From: Rich
I agree with @Brandon. There's no advantage to restricting what can be done with reflection. I'd be surprised if loads of new scripts don't get released when a fully fledged reflection include is up and running. I'd expect more scripts, which would mean more activity. Surely that's a good thing? You could release an initial slimmed down version to do, as you said, what's difficult in colour and release the rest in an update at a later date? Just an idea.

Add another +1

Now the problem that arises with a 'full' include is the conflict with silly functions that are already in SRL.
For example, a problem in the past with this was R_WaitOnWindow or something of that nature. SRL already has a very simple function that does that.
IMO, there's no reason to bloat the include by adding non-reflection specific functions.

Whatchu guys think?

From: noidea
Now the problem that arises with a 'full' include is the conflict with silly functions that are already in SRL.
For example, a problem in the past with this was R_WaitOnWindow or something of that nature. SRL already has a very simple function that does that.
IMO, there's no reason to bloat the include by adding non-reflection specific functions.

Whatchu guys think?

Agreed, stuff like close window gametab is logged in etc etc :s