Itemgrid suggestions

[kaithar]

I apologise for the vague title, I'm not sure what better to call this. I have two questions/suggestions:

1. Objects displayed on an item grid don't appear to have any mouseover or automatic overlay text added. All I'm getting is the image specified in my items.json. What I'd like is to be able to associate some text to differentiate between items in a group (where keys are for, for example). Currently I'm working around this with lua calls like this:

Tracker:FindObjectForCode("specialstage1key"):SetOverlay("Sp1")
Tracker:FindObjectForCode("specialstage2key"):SetOverlay("Sp2")
Tracker:FindObjectForCode("specialstage3key"):SetOverlay("Sp3")

That kludge kinda works but I'm polluting the log with output that seems to be core:

update state of 15: "Special Stage 1 Key"
update state of 16: "Special Stage 2 Key"
update state of 17: "Special Stage 3 Key"

2. It would be nice to have an itemgrid equivalent for location checks, or even better be able to combine them. Part of my victory conditions for this pack are collecting a set of specific checks, I don't really want to add dummy items just to track that they've been completed.

3. Similarly, it would be nice to have a way to display how many of a group has been collected. I think the suggested way to do this currently would be to have a static fake item and use lua to update the count on it?

[black-sliver]

1. should be displayed in the top-right corner? - 1.1. you shouldn't really care about that kind of log messages.
2. using items for "any kind of state" is intended. "More complex locations" are typically also hosted items rather than regular locations.
3. probably, yeah/

[kaithar]

1. ah, I see it now... I was expecting it to popup like the location ones and hadn't noticed because I had the items down in the very bottom-left
2. I could in theory add a "you beat the boss" item but since it's a location with an item it seems like I'd have to jump through hoops to get two items attached to a single check. Doesn't feel like that's how the generation logic is designed to behave?