Suggestion Allow authors to supply their own raw entities into a querybuilder

Discussion in 'Client & Site Suggestions' started by SlashnHax, May 10, 2016.

  1. Would be nice if we could supply a callable that's used in the getRaw method.
    Qosmiof2 and Savior like this.
  2. We'd better tag in an Exec for this one.

    @SlashnHax get it added!
    Qosmiof2 and Savior like this.
  3. I would if I could :p
  4. Scrub. His name is @Vaped not @cloud
  5. I repeat, will the real cloud please stand up!
  6. Did some tests, Npcs.getLoaded() takes like 8ms, GameObjects takes like 30-40. I guess it would still help as you can pass in your already filtered sets :p
  7. Why would you first filter it though
  8. I don't know, possibly a cached set from a previous call? My initial request was because I assumed that getLoaded() took a while, but it really doesn't seem to take that long at all. I guess if you had a task tree where the lower tasks could utilize a set created by an upper task it would be a good idea, although idk how many people here use task trees, it seems like a lot of people usually only go one task deep
  9. I use task trees pretty frequently. And it would indeed be nice to have. The reason I think a custom raw() population would be powerful is that you can join two sets of say LocatableEntities from Npcs.getLoaded() and GameObjects.getLoaded(), and query/sort them both at once.
  10. I guess with your own custom LocatableEntityQueryBuilder you could. You could probably even create your own wrapper that wraps common methods between the two types to extend the functionality beyond that of LocatableEntity, that would be an interesting thing to see :p
  11. Support.
    SlashnHax likes this.

Share This Page