Ahelps should be logged to the database. Right now, the only option for logging is the discord relay. This isn't ideal for many reasons including searchability. The issues can be mitigated by using admin logs, but I don't think that's an ideal solution.
Included data
List of everything that, ideally, would be stored:
For each message:
the message
the sender
their admin status (adminned, not adminned)
their controlled entity (Either an entity UID, or nothing if they're in the lobby)
the time it was sent
For each ahelp exchange:
Round number
Who is being ahelped
Additional optional information, which may be ideal to derive from other sources:
The status of the round during each message (lobby, round, post-round)
The online status of the person being ahelped at each message
The online status of each participant
Possible schema
This doesn't include the online status of each participant, and it may have issues, I haven't done anything with databases recently. This might also benefit from additional tables, maybe an entityID to prototype/name thing
Ahelps should be logged to the database. Right now, the only option for logging is the discord relay. This isn't ideal for many reasons including searchability. The issues can be mitigated by using admin logs, but I don't think that's an ideal solution.
Included data
List of everything that, ideally, would be stored:
Possible schema
This doesn't include the online status of each participant, and it may have issues, I haven't done anything with databases recently. This might also benefit from additional tables, maybe an entityID to prototype/name thing