Venix

@peppy since I'm gonna work on the seasons thing now, i wanted to ask, should there be an interOp API endpoint or something to make assigning certain rooms to certain...

Thought you wanted to use it in an external script, that's why i suggested the interOp, did the stance change since and therefore i should make it a website UI...

ok so what i mentioned database-side is mostly explained in the opening post i believe, to put it simple way: - ``Season`` table contains specific spotlights (and in future possibly...

ok, so just to clarify, should i go with ``season_id`` on ``Room`` or with separate ``SeasonRooms`` table to allow one-to-many relationship between rooms and seasons?

> _assuming a new category won't happen_, I also don't follow why this is proposed as a tack-on to Loved instead of Ranked when that's clearly the closer category in...

Sounds about right probably, but keep in mind that we wanted to add the label to older spotlights (pre-lazer era) as well. (this probably could be done as a separate...

i can probably do most of these

I believe people that are actively involved in running well known community projects (such as mentorship, spotlights, big tournaments like corsace for example etc etc) or generally community all-rounders should...

Eph is not around so need ``spotlight=1`` on those as well: ``1713947,554143,1638064,1765453,1650533,1439651,1048608,1575475,1659645,1802506,1355421,1775661,1770207,1616787,1519045,1414012,1763568,1828466,1816401,1597589,1764078,1689443,1769575,1774562,1770054,1704324,1810556,1838172,1568720,1304251,1672239,1641449,1721944,1741321``

Updated the OP with a screenshot. As for translations, it's built into issue tags workflow so is easier to just go that way rather than omitting it, it's only tooltips...