Skip to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Please Implement More Interfaces!

Featured Replies

XRudumentaryInformation that has getID() and getName() methods that return their respective values. This is to be extended onto the interface of XObjectDefinition, XNPCDefinition, XGroundItem and XPlayerDefinition, and any other interface that require either/both information.

 

Why? I'm trying to make a generic-orientated getter class that provides functions such as: getNearest(RS2Object, NPC, GroundItem or Player). The problem is, there's 4 different interfaces defining similar attributes, but having methods kept isolated from an otherwise-should-be common source. Why have 4 different getName() methods in 4 different interfaces when you can add a 5th interface and extend those attributes through? It would be seriously convenient since I won't have to handle casting each input to their specific type before I can actually get the getID() and getName() values. Not to forget; it could be applied to the Item class. This could make debugging a lot simpler--if you're debugging entity/item names/ids.

 

Currently, my generic-orientated class accepts Entity inherited instances only, but I still need to analyse the instance of each Entity and cast it to their respective types to get access to the #getID() functions.

 

If some information can't be provided from the attributes, i.e., Player doesn't have a getID() function, be creative! Return the player's PID and treat it like the ID.

___________________________________________________

 

Last one (though not an interface request):

 

Please add setters for Position's coordinates. Don't make the x, y, z values constant. Make them manipulable.

 

Add a translate(x, y, z) and translate(x, y) methods to Position. These would directly manipulate the instance's coordinates.

 

Add a derive(x, y, z) and derive(x, y) methods to Position. These would return a new instance of what translate would return.

 

It would be great if Position is dynamic.

 

___________________________________________________

 

Thank you,

 

LiveRare

Edited by liverare

Guest
This topic is now closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.