- Joined
- Oct 12, 2015
- Messages
- 3,792
- Thread Author
- #1
Client
Environment Reloading
GrandExchange
OSRS
Quests
ItemDefinition
Environment Reloading
- RuneMate now has the ability to close and restart the RuneScape client, re-bind to it and resume your active bot.
- For the meantime, this feature is only fully supported on Windows, and is still experimental on Linux and OSX.
- This is available via Environment.restart() and should not be heavily used by Bot Authors.
- This feature is enabled by default when the RuneScape session has ended, for example after 23 hours of having an RS3 client open.
- This feature will not require users to input settings etc and it should not affect the execution of a running bot, as the same bot instance is used.
- Whilst the client is reloading the bot will appear to be "paused", but will actually be in a new AbstractBot.State, RESTARTING.
- Bot Authors now have the ability to toggle SDK mode from within the client.
- This can only happen whilst no active bot is running.
- Bot Authors can access this new feature via the Preferences/Settings page.
- To clarify, the -sdk launch argument is still valid.
- Fixed an NPE which would occur when closing the client pre-login.
GrandExchange
- New GrandExchange API.
- This API allows Bot Authors to query the Grand Exchange from anywhere in the game.
- This is supported by various hooks which were previously unexposed.
- This expanded API also allows for the placing of offers via the Grand Exchange interfaces.
- A new QueryBuilder has been added for this, the GrandExchangeQueryBuilder.
- A new EventListener has been added for this, the GrandExchangeListener.
- The InterfaceCloser will still try to close the Grand Exchange interface, so be sure to disable that temporarily if you wish to use the interface.
- Fixed a bug when interacting with vertices which required a form of dialog.
- We've began prototyping new traversal methods for use in the default web, including spell teleports for both OSRS and RS3 - this is supported by improved detection for current Quest state.
- Based on PlayerSense, some accounts will toggle run before/after taking a step.
- Fixed a critical typo in WorldHop.to(int).
- Cleaned up the code in both RS3 and OSRS specific elements to make it return true or false more consistently with the rest of the API.
- We've added a new functional interface which determines what action is to be taken on a failed RuneScape login attempt - FailedLoginHandler.
- By default, the bot will stop (unless the failure was the session ending, in which case it will restart the RuneScape client [see above]).
- This can be set by bot authors via GameEvents.LoginManager.setFailedLoginHandler(FailedLoginHandler)
- Fixed a bug which caused the Holiday event window to be missed by the Interface Closer.
- Improve Collision Flag caching for both game types.
- Expanded use of PlayerSense in the API.
- Implemented int getMapFunction(), the circular icons displayed on the (mini)map as an indicator/landmark.
- Implemented int getMapScene(), the images displayed on the (mini)map for objects such as trees, rocks and bushes.
- Implemented boolean impenetrable(), which determines whether or not projectiles can bypass/go through the object to reach their target.
- Implemented boolean isInteractable()
OSRS
Quests
- Fixed a potential NPE in Quest#getStatus()
- Collision flags are now manually generated instead of relying on the hook.
- No longer selects tournament or deadman worlds.
- Screen.capture() will now correctly return the game frame in it's current state regardless of the number of clients opened/minimized.
ItemDefinition
- Added ItemDefinition#getWornActions()
- This SpriteItemQueryBuilder for Equipment will now search using the above actions.
- Extended the delay when hopping to ensure that WorldHop.to() more reliably returns true when hopping.
