search

AsherGlick / Burrito

An overlay tool for Guild Wars 2 that works on linux
GNU General Public License v2.0
80 stars 19 forks source link

Area Datatype #10

Open AsherGlick opened 3 years ago

AsherGlick commented 3 years ago

Areas would be the third datatype on top of Icons and Routes. They are a similar type to Routes but function as enclosed spaces instead of just lines.

This idea was conserved early in the burrito design but thus far the only use cases are for Guacamole (#2) or for being able to have a color-fill in the minimap.

coderedart commented 3 years ago

was wondering, but can we use the existing trigger_radius of icons/poi as a simple area type? info range and info attributes already act as such, where if you enter within a certain radius, you trigger the info text attribute.

the only reason to have a Area datatype would be to contain non-circular regions like non-uniform polygons. and why would we need such a data type in the first place? to represent heart npc's quest borders?

AsherGlick commented 3 years ago

This is definitely a possibility if it turns out having support for arbitrary polygons is not worthwhile. That being said I have a small idea of something around hearts where when you walk into a heart a 2D popup appears to tell you what to do in that heart. Not sure if that is the best way to tell people how to do hearts and I was planning on looking at augtyr's heart guides to see if their setup was a better overall idea.

If there is nothing that makes sense for areas beyond "close to this position" then it makes sense to implement trigger radius instead.

coderedart commented 3 years ago

I think tekkit shows a icon with sort of a guide. But I doubt area will be that much more effective than that

AsherGlick commented 3 years ago

I know position is used in determining when the Sabatha encounter starts, but that is on a pretty narrow bridge so a radius would still probably suffice.

Now that I am sitting on it a little more it probably makes sense to implement trigger_radius as a separate but similar thing from areas, and then leave areas in limbo until a valid use case for them arises. I will update the language spec in #2 .

dlamkins commented 3 years ago

Coderedart is correct that multiple packs do currently implement it just that way via radius around the heart with the info attribute showing text while in-range. Tekkit's isn't, but ReActif and Teh's trails definitely do.

As an aside, you can use our pack reports to see what attributes are most commonly used by some of the public marker packs. https://mp-repo.blishhud.com/