- Thread Author
- #1
Certain method calls are known to be unacceptably slow, if you encounter any that are not on the list and don't themselves invoke methods in the list than please post notifying me.
- GameObjects.getLoaded() - Significantly faster than it used to be
- GameObjects.getLoadedOn and getLoadedWithin can be used to search a smaller area which is significantly faster. GameObject queries automatically search the smaller area when a coordinate or area is passed in for the search parameter.
- Specifying a type when querying for GameObjects is also a way to drastically speed up a query. It's a much faster check than name and/or actions because it doesn't require loading any definitions.
- Interfaces.getLoaded()
- Specifying the container can vastly reduce the amount of calls that need to be made. This optimization is automatically applied to queries.
- ActionBarQueryBuilder.names(name).results()
- Queries interfaces way more than necessary to get the name of the action in the slot
- House#isInside - Only OSRS is slow
- Relies on a GameObjectQuery for portals on OSRS
Last edited: