mmbuw / massive-mobile-multiplayer Goto Github PK

replace swearwords in names with XXX or similar

• Game: Make field size independent of screen resolution - ball and goals not spawning correctly --> Johannes
• Game: FPS still drops when a player is added to the game (just on Raspberry), check for spot where this happens (input thread already tested -> not responsible) --> Tim
• Frontend: Send a (0,0) position message when "analog stick" is released --> Andi
• Frontend: Interface coloring must happen after the team message is received, currently, there are cases in which the UI wants to check for its color, but it is not yet present --> Andi
• Frontend: Close Connection properly on page change, refresh, etc. such that we do not need to close the browser all the time --> Andi
• Game: Strange behaviour when in multi-player settings one player is leaving, removal not working correctly --> Tim
• Frontend: Controller interface lagging on some mobile devices
• Game: Sometimes a new player is created twice when a new input device is added, weird concurrency issues --> Tim
• Game: When players spawn at the very same location, they directly go to NaN --> Tim
• Game: Score font and indicators are still somehow resolution-dependent
• Frontend: When closing a connection tab properly and opening a new tab, the connection is not working anymore.
• Frontend: After I disconnect once, I can't ever reconnect. Any attempts to log on only redirect to the landing page.

• friction is too intense --> seems like lag
• when the player size was adapted and a new player connects, he/she still gets the default size
• indication on in which direction each team needs to play
• spawing of players in a corner (such that name cannot be read) must be avoided
• reduce high power consumption (or maybe offer a charging station)
• ball slows down too fast --> adapt friction coefficient
• bug report on virtual control stick not being at the finger's location
• bug report that sometimes (0,0) events are not considered --> player keeps moving
• bug report with Opera --> player keeps his/her velocity
• player number seems confusing ("what is that number in my circle?")
• when browser is left and then resumed the connection is lost but controller still open
• the maximum name size should already be applied to the name text field
• color of player names should be black
• native Android browser is not working
• the font on the large beamer is just shown as rectangles --> problem with 1920x1200 screen resolution in seminar rooms --> switch hdmi_group = 2 and hdmi_mode = 58 in /boot/config.txt --> resolution becomes 1680x1050 (60 Hz)
• iPhone 4S not able to connect to game (login page just refreshes) --> Safari
• iPhone 4S with Chrome not able to control and shoot at the same time
• Avoid browser copy gesture? --> set control stick to non selectable / focussable
• Goal box was still incorrect?

Suggestions not to be considered (at first):

• login in Wifi network should automatically open the browser
• implement bots for undersized team
• put virtual control stick to the right side of the display
• other control stick metaphor, like region-based approaches (cf. Leo's Fortune)
• use button / gesture for explicit logout
• do players stick to each other too much?
• is it good that players may push other players that heavily?

Game font doesn't support umlauts etc.

seems to have some issues with newer iDevices

hard to describe, maybe show two semi-transparent thumbs when screen is not touched

• WebRTC client-side implementation in JavaScript (preferably without huge libraries)
• WebRTC server-side implementation in C++ (probably using librtc)

After reading Hasib's thesis (who used the MMM framework), it looks like many people have issues with disabled auto-rotation. This also occurred several times during the demos IIRC. Would it be possible to bypass the OS-supplied rotation by using the W3 DeviceOrientation API [1]? Or is this useless when UI rotation is disable on the OS level? To get rid of the ugly device-/browser-specific special cases, it might be possible to use something like gyronorm.js [2].

• [1] https://www.w3.org/TR/orientation-event/
• [2] https://github.com/dorukeker/gyronorm.js

• trigger touchscreen using relay (?)
• measure response using photodiode

maybe add a second WiFi stick to forward internet traffic?

When moving the controller slightly to the top, it fires inputs which move the player downwards...

• Chrome on iOS doesn't work (known bug, but maybe we can find a workaround by now)
• Browsers in private mode don't seem to work (cookies?)
• iOS users in particular seem to get randomly disconnected