[Experimental] Feedback on: Cyclops Flooding damage player feedback
ranmafan
Join Date: 2018-02-04 Member: 236837Members
Hey there devs, I've been playing the game on experimental (those performance fixes are amazing btw) and I just saw the new Cyclops flooding effect. I'd like to give some feedback and make some recommendations:
1) The effect at present is not immediately obvious to the player - that is, I don't know I'm taking damage at a glance without getting off the helm and looking behind me.
2) To make the 'info at a glance' obvious, I'd say add the water leaking effect to the bubble canopy. That is, s water leaking down the left side as if the seam of the Cyclop's bubble is compromised. Drops of water might help too, but just a stream of water flowing down in front of the player should suffice to be immediately obvious to the player that all is not well. (This would be similar to how a breach in the base module has a very mild trickle of water flowing from the breach effect)
3) The water leaking on the top deck does not carry over to the lower deck. I'll assume this is known.
Minus the fact that it's still WIP, these are how I'd fix the issues at the moment.
Thank you for listening!
(8 years in game dev, still a game dev, lead designer at a small studio. Feel free to drop me a message to check my credentials)
1) The effect at present is not immediately obvious to the player - that is, I don't know I'm taking damage at a glance without getting off the helm and looking behind me.
2) To make the 'info at a glance' obvious, I'd say add the water leaking effect to the bubble canopy. That is, s water leaking down the left side as if the seam of the Cyclop's bubble is compromised. Drops of water might help too, but just a stream of water flowing down in front of the player should suffice to be immediately obvious to the player that all is not well. (This would be similar to how a breach in the base module has a very mild trickle of water flowing from the breach effect)
3) The water leaking on the top deck does not carry over to the lower deck. I'll assume this is known.
Minus the fact that it's still WIP, these are how I'd fix the issues at the moment.
Thank you for listening!
(8 years in game dev, still a game dev, lead designer at a small studio. Feel free to drop me a message to check my credentials)
Comments