Anyone feel free to add their ideas in replies
Bot API:
- Access to tip jar tip events (amount + User object)
- Access to info about Spectators in room through get_room_users. The GetRoomUsersResponse object having an additional “spectators” variable likely with this structure: list[User] would be ideal
- The on_message function giving a User object rather than just user_id would be good if possible
- Change room info, name/directory/access etc. through API
Web API:
- Adding a ‘hashtag’ parameter to get_posts so we can see only posts from x hashtag
- Event data API: Get info on all events, past scores / ranks if possible for crews/users. Most importantly ticket score/rank info on the currently active event
- A get_crews + get_crew which returns a list of crews/info on a single crew respectively
Bugs:
- Bots being unsearchable in-game after updating their username/bio
- Issue where for some users opening a conversation with a bot (for the first time) spams the user with “Conversation not found” and doesn’t let them DM - unfortunately don’t have knowledge on how to repeat this bug consistently
- Teleporting updating the visible position for all users who aren’t in the room when it happens. Sometimes if a user is teleported, and then someone joins a room, their visible position is not consistent with everyone else who was in room when it happened
Finally could we get an idea (as much as allowed) of the structure of what data HR keeps that could be accessible through webAPI? Might give more ideas of what we could build/do in the future, thankyou!