redfluffydragon/dnd-app

dnd-app's Issues

Solution for switching wifi networks/ip addresses

Currently, the magic login relies on localStorage, which means it relies on the app always hosting from the same IP address. The easy solution is that everyone has to remember their username if switching wifi networks.

I think the best (and maybe the only) way to do this is to have to controller website hosted somewhere permanent, and only have the websockets go through the local network. This way the player ID can be saved to localStorage associated with the permanent url, but the websockets are still through the local network, which should be faster.

Pros:

• As long as localStorage isn't cleared, the player ID would be saved no matter what network you're on, allowing the basically magic login to work

Downsides:

• You would have to scan two QR codes, or go to the website and then scan a QR code (or type it in). Either way, this is more seamful.
• Playing offline would require the website to be a PWA, which is kind of annoying.

Port collision

This isn't likely to be a problem, but there is a possibility of port collision. There are basically two solutions I can see: either it auto-detects the collision and switches to a new port, or it offers the option to manually set the port. (Or both)

Fix realtime inputs

With requestAnimationFrame, a more powerful device sends more signals in the same amount of time and with the current setup, it will move faster.