jtalier
commented
2 years ago I labeled this new member because there are aspects of this project that would be good to talk about/ get help with from new members. That being said this problem gets a bit into the weeds on the scheme so would not be my first pick
This is straight nightmare fuel. The commanding user can create a campaign/ test and write notes. The server gets all this info but the clients are not updated with that info. Right now the client handles the campaign time, test time, displaying notes, etc. If we want multiple clients to all see the same data for the campaign time/ tests/ notes then that functionality will have to be switched over to the server. We could maybeeeeee leave it client side and then add a few things to the client packet that update the non commanding packets but that feels messy. It makes more sense for the campaign to be handled by the server. Notes will be a whole other big problem for the connections scheme. Currently the server only sends back a header + data packet that has all the data the client needs to display about the client. If we want to show notes, well that is user info that is unknown. We can't send a massive packet with all the notes so will need to implement a way for the client to receive commands from the server. Ahhhhhhhhhhhhhhhh :((((