SRL Archive - Reflection Development

Hey,
All the different kinds of objects and animations got different ID's. Currently, every scripter has to grab those himself and if they change all the scripts need to be updated (not that they change that often, but I think it's too boring to grab all the ID's by hand :p).
So how about one big constant include?
Example:

//Reflection ID Include

//Objects
//Woodcutting
const
  ref_obj_YEW_TREE = 1309;
  ref_obj_YEW_STUMP= 7402;
//Mining
*insert here*

//Animations
//Skilling
  ref_anim_CUTTING =  867;

//Items
  ref_item_Knife = 946;

Just a suggestion, but it looks cool to my eyes :p

From: Markus
Hey,
All the different kinds of objects and animations got different ID's. Currently, every scripter has to grab those himself and if they change all the scripts need to be updated (not that they change that often, but I think it's too boring to grab all the ID's by hand :p).
So how about one big constant include?
Example:

//Reflection ID Include

//Objects
//Woodcutting
const
  ref_obj_YEW_TREE = 1309;
  ref_obj_YEW_STUMP= 7402;
//Mining
*insert here*

//Animations
//Skilling
  ref_anim_CUTTING =  867;

//Items
  ref_item_Knife = 946;

Just a suggestion, but it looks cool to my eyes :p

that would be huge, and as you said, if they change they would need updating, just the same as this.

-Boom

If we can somehow get a raw list of everything and their IDs from the client we can then parse that and make this file automatically. I don't know if we would be able to differentiate the type though (as far as item, animation, etc.), but you know.

I was talking to pyroryan a day or two ago, and he told me he could dump the price of every item in the GE without owning one via java. Perhaps a similar process could be done for objects, item, animation, and object IDs, and then parse the dumped file with some PHP code.

doesn't rsbot have a list of all(most) id of objects/npcs/animations, and i remember someone posted a txt file with all of the info.

See here:
https://github.com/SRL/srl-reflection/tree/master/Development

Wtf? Is that generated automatically after every update? If so, I'll make a parser to put it all in a file like the one above. Or perhaps separated for more speed.

From: Dynamite
See here:
https://github.com/SRL/srl-reflection/tree/master/Development

Woah…

Also: 'Willow Tree', 'Willow Tree', 'Willow Tree', 'Willow Tree', 'Willow Tree', 'Willow Tree', 'Willow Tree', 'Willow Tree'.. There's sure a lot of different willow trees in-game :p
I'd hate to have to update every single one of them manually if I had written a script…

Well iirc, there are a few types (like different looks?) of Willow trees and then * by the number of them because of just the trunks. However, there may be only one willow trunk object..

Can you imagine the size of that include?

Yes that was one thing..maybe a database online and then just retrieve what you want..? Cache it maybe? I dunno :p.

I doubt its worth it. There are so many Id's for the willow tree that most are location specific. So, you either have a tree finding function wasting time looking for trees in another city(even worse if you have it designed to walk to them), or you have to check the IDs yourself from your location. There tends to only be a few IDs per scripts used anyway. I like the idea, but I feel like it might not be worth the time and the results will be not where we want them to be.

E: Replace willow tree with whatever you want.

Then don't have id of objects that have multiple objects like willow trees in this case, and yeah, there isn't many ID's in a script so we could just use the online one to lookup, instead of grabbing it ourselves.

Looking through every single object and animation in RS and then recording them would take a really, really long time. By the time the entire file has been updated, a new update will have occurred and the process will have to be started again. Its better if individual scripters update their own scripts.

From: Echo_
Looking through every single object and animation in RS and then recording them would take a really, really long time. By the time the entire file has been updated, a new update will have occurred and the process will have to be started again. Its better if individual scripters update their own scripts.

They are actually cached. That is how the person on rsbot generated all of those id's.