SRL Archive - Reflection Discussion

I was thinking, could we do something like, have an Item type with Name, UnnotedID, NotedID in it, and while scripts run they check for a un-recorded items, and update the record. They could check the runescape wiki to see if its notable, if not it sets NotedID as -1 else it sets as UnnotedID+1, which should be accurate.

It holds as an ini and when it gets an update, it sends to our server for confimation and updating.

"It holds as an ini and when it gets an update, it sends to our server for confimation and updating."

why make a new server when you can use the wiki as the server? ;)

Protip:
Noted ID of Item = Not noted ID of Item + 1

we have something we can use, and I'm pretty sure that the runescape wiki doesn't store the item IDs.

The GE does, for all trade-able items.

It could be built. What would be the purpose of this? Would it only include tradable items?

I see no point, now that I re-read the post. All tradable items, as I mentioned, are in the GE DB, with IDs.

Unless I'm misunderstanding something?

From: i luffs yeww
I see no point, now that I re-read the post. All tradable items, as I mentioned, are in the GE DB, with IDs.

Unless I'm misunderstanding something?

Maybe build in requirements for wearing equipment. I just don't see why this would be necessary.

To be honest, I think you guys are making reflection way too simple for people to use. Overloading it with things like this just makes everyone end up being ass lazy. Reflection would be complete imho if it just handled tile walking, position locating, object/npc finding, and animations. Also interfaces, but really anything that needs an interface to be found (i.e. withdrawing things from bank) should just be done with color.

From: TomTuff
To be honest, I think you guys are making reflection way too simple for people to use. Overloading it with things like this just makes everyone end up being ass lazy. Reflection would be complete imho if it just handled tile walking, position locating, object/npc finding, and animations. Also interfaces, but really anything that needs an interface to be found (i.e. withdrawing things from bank) should just be done with color.

I don't think reflection could be complete without interfaces since it has wide applications, including handling the inventory. Item finding in the inventory could be compared to object/npc finding.
If anyone wants to build something into the core of reflection, I'm fine with it. Doesn't really matter to me if something becomes too easy. People will always find new ways to expand their knowledge and come up with new challenges. Today's difficult should become tomorrow's easy. Otherwise, are we just doing more of the same and failing to advance ourselves? My view is that whatever method is available, should be used until a decent compromise is reached. Reflection currently isn't top-notch reliable because of the lack of people capable of updating hooks. So in my view, the compromise is a hybrid with one system serving as a backup/tool for the other.
As for your laziness argument: its not technically laziness. Its using the tools available to us to accomplish the task. Otherwise, I could say that we shouldn't be using pascal, java, C++, etc. because thats the lazy way out. Why don't we go back to programming in machine code so we're no longer "lazy"?
I'm not saying don't go for the challenge or for the experience. By all means, go for it. But, each method, whether reflection or color, should be the best it can be.

2 reasons, it can automatically update itself, and it can include non-tradeable items, including burnt fish.