API Missing Features:

 

1. Area constructor that supports boundery Postions.

 

  ex:

Public Area(Position sw, Position ne) {//set variables here}

 

2. Add the following methods to the NPC, Player, GroundItem, RS2Object:

 

  Position getPosition() {//stuff} //returns the current position of the current object

  boolean isOnScreen() {//stuff} //returns true if the object is on the screen

  boolean interact(String action, String option) {//stuff} /*move the mouse to the object, if the action and option are the first on the menu, left click, otherwise right click and select the action and option*/

 

3. It would be extremely helpful to be able to get the boundry points or four corners of a Position(or Tile). This would be useful in determining if a Position is completely on screen.

 

4. I also think it would be more organised if you create seperate classes for some of the Script methods.

 

  Some examples of these classes would be:

  NPCs

  Players

  GroundItems

  Calculations

 

5. I think you should consider a more object oriented aproach. For example: It would be more organized if NPC, GroundItem and Player classes had more methods in them, so we wouldn't have to use so many methods located in Script.

 

I'm a java programmer with script/API wrriting experience and would be willing to help add these things and more if you would like.

 

 

 

 

boolean isOnScreen() {//stuff} //returns true if the object is on the screen

 

 

  This really needs to be added, would make checks so much easier.

 

thats and path walking. (traversing) & (reverse.traverse)

 

isOnScreen is fine.

 

Area would need more than 2 ints, I'd suggest infinite, so just keep adding positions and drawing the line through that, sorta how PB had it, it really was flawless.

isOnscreen is needed  would make it easier for us to check things

areas can be made easily

i think admins said they are going to sort the api in later version

I'm wondering where you have been looking but so far most of what you summed up is available.

API Missing Features:

 

1. Area constructor that supports boundery Postions.

 

  ex:

Public Area(Position sw, Position ne) {//set variables here}

 

It does have this support, however area's were forgotten and not updated last time. WIll happen this time, it's a 2 minute job.

 

2. Add the following methods to the NPC, Player, GroundItem, RS2Object:

 

  Position getPosition() {//stuff} //returns the current position of the current object

  boolean isOnScreen() {//stuff} //returns true if the object is on the screen

  boolean interact(String action, String option) {//stuff} /*move the mouse to the object, if the action and option are the first on the menu, left click, otherwise right click and select the action and option*/

 

getPosition and interact methods exist for all entities. Perhaps you should give yourself some lessons on inheritance before your next suggestions thread. isOnScreen is something I can add for sure, again a 2 minute job.

 

3. It would be extremely helpful to be able to get the boundry points or four corners of a Position(or Tile). This would be useful in determining if a Position is completely on screen.

I can add a ready to go method for this in the Position class, however getting the screen positions for those things was already possible using the utility package. But sure, we can add this, again a 2 minute job.

 

4. I also think it would be more organised if you create seperate classes for some of the Script methods.

 

  Some examples of these classes would be:

  NPCs

  Players

  GroundItems

  Calculations

Most of the methods in method provider are also available from within their respective classes, like they should. However we're not removing the old ones in method provider because it would break many scripts.

 

nice to see Maxi & Co reading up on suggestions, half way to a solid admin team right there.