Please include this into the API:

 

Findable is an interface that extends the following:

• Identifiable is an interface that contains #getId() : int
• Nameable is an interface that contains #getName() : String

 

How it works:

New Entity getter methods support 'Findable...' parameter. The method first checks to see if entity's id equals Identifiable#getId(), but if the value equals -1, it then checks specifically for Nameable#getName().

 

Amended to enable name-specific searching. This would be used to find clue scrolls since they're numerous. It can also be used for entities you cannot have the ids for, e.g., objects and NPCs. Another bonus to this is that non-usable names can be used alternatively for the #getName() method (e.g., "Grimy ranarr"), to make it easier to profile enum records without worrying Namable is going to be checked.

 

Why?

Convenient namespaces, that's why. Enums can implement interfaces, and this would allow getter methods to call something like getClosest(Loot.DRAGON_CHAINBODY) instead of the existing way getClosest(Loot.DRAGON_CHAINBODY.getId()).

Edited December 27, 201411 yr by liverare

nice suggestion

quick small change

Alek what you can do is create the findable interface with the two methods. Then have the Identifiable interface extends the findable interface. The reason why you should do it is in op. Also it's all cool and stuff using filters, but using interfaces are easier.

Edited January 13, 201511 yr by josedpay

This sounds extremely useful.

This is a pretty good idea; I'll keep this open until I put something together. Don't expect something soon, but it's definitely on "the list".