The long dead amongus has restarted!
This is a framework for you:
https://snap.berkeley.edu/snap/snap.html#present:Username=18001767679&ProjectName=amongus%20framework
Members:
- 18001767679
- programmer_user
- tussiez for backend or joking
- sir_kitten
- earthrulerr
- bubgamer07_bungamer0
- helicoptur
- mr_owlssssnap2
Getting pixels from the server and drawing them onscreen seems awfully slow, not to mention impractical and confusing.
Doing that will avoid a bunch of probelms like collision dtection faults and raycasting
Oh i mean BIG pixels not the pixels physically
Minecraft piston style
You should use MQTT even if your using big pixels.
HTTP:
Where is player XY position? Server: 123,456
Where is player XY position? Server: 123,456
Where is player XY position? Server: 123,458
Where is player XY position? Server: 123,458
Where is player XY position? Server: 123,459
MQTT:
Established connection
Server: XY Changed, 123, 456
Server: XY Changed, 123, 458
Server: XY Changed, 123, 459
So i am going to use websocket
and it looks like that mqtt is the same as websocket
ps:the map wouldn't have over a hundred x degrees so no 123,456 thing
I will need to transfer the whole grid(that is all of the information except tasks and roles)
Not exactly. I think you should use MQTT.
okay
ps:looks like you learned a lot in the past year
You know you can...bump...the topic?
yeah, bumping means to post on an old topic so it's bumped up to the front page, hence the name
oh, I meant to put an exclamation mark there. Was on mobile
Welp, project restart also failed.
And a restart of this restart would probably also fail.
whoops
my collaborations always fail.
no one pull request