Skip to main content

Survey results

I had exams, so I could not really work on PewPew, but now I am back. Let's take a look at the survey results.
There were 46 responses, and I started having responses only minutes after I posted the link on touchArcade's forum. One cool thing is that they appear in real time, in a spreadsheet. Well done Google.
And wow, I can actually copy paste the generated summary into this post.
Here we go:


The game modes are pretty even, though it would appear you like shooting more than dodging.

What is your favorite game mode?

What is your least favorite game mode?


I find the music excellent, and you seem to agree. That's good because the composer is not cheap, he earns 50% of the profit* made with PewPew. The soundtrack is available for free by the way.

How would you rate the music?
Very poor
Excellent


Ah! Google is not perfect after all, they messed up the parsing! That's about all we learn from this question, because I already knew that I am good at making a game balanced.

The difficulty of the "Assault" mode increases:



The difficulty of the "Chromatic Conflict" mode increases:



And now, the most important information I got: it appears you guys prefer a new game mode over online scores! That really really surprised me.

What would you prefer in the next update



In fact, I was planning on releasing an update with the only new thing beeing onlines scores, but that made me change my mind. So yeah, this survey was useful.
Also, I was thinking about doing a game mode that involved dropping bombs, but since you like shooting so much I went in a different direction... that I have yet to find.

Finally, I got a lot of interesting/passionated comments in the form. I'll talk about all the improvements I did for PewPew 1.2 in a futur post.
Thanks everyone.

* that amounts to exactly 0€
Labels:

Comments

Post a Comment

Popular posts from this blog

PewPew Live's look in a nutshell

Occasionally someone will asked how I obtained the PPL look. In a nutshell: Draw everything with lines, including the text and the various icons. It's a lot of work, but besides looking unique it creates a consistent appearance which is a thing that a lot of indie games struggle with. The lines are screen-space projected lines with miter joins. Draw the lines with additive rendering. This means that if a red and green line overlap, the overlap will be yellow. There are a few things not drawn with additive rendering (like the background of buttons to improve readability), but they are exceptions. Add bloom. There's lots of different bloom implementations. Nowadays I use a bloom that is similarly to the one in  blender's eevee . If you see banding, use dithering. Optional: Add even more post-processing like (very slight) chromatic aberration, lens dirt, scan lines, curved monitor, and vignette. No post-processing, just lines Bloom! Ignore the missing bloom at the top All the...
Post a Comment
Read more

A general state rollback technique for C++

I wanted to write this post for a while. It describes a C++ technique to implement rollback in the context of multiplayer games that I feel is quite interesting and useful. The tl;dr is: don't bother serializing individual objects, just rollback all the memory. Rollback-based multiplayer I've been working on a multiplayer version of PewPew, and for reasons that are outside of the scope of this post, I chose to implement multiplayer with deterministic lockstep and rollback. The basic idea behind rollback-based multiplayer is that the inputs of players are replicated to all the players. Whenever a player receives the inputs of another player, the state of the game is rolled back to the point where the input happened and fast-forwarded back to the present so that the state shown to a player takes into account the inputs of the other players. Because history is being re-computed, some events get undone. For example, it's possible a player saw themselves taking a bonus, but aft...
2 comments
Read more

Ridiculously cheap depth of field effect for lines

I'm working on PewPew's sequel, for which I've revamped the graphics. Instead of drawing lines directly using OpenGL, each individual line segment is made up of two triangles whose vertexes are computed with shaders. Getting lines in 3D space to be properly displayed on a 2D screen is not trivial. In PewPew's sequel I use the screen-space projected lines, a technique very well described in the  Drawing Lines is Hard  post. The upside of drawing the lines yourself is that you are fully in control, which allows you to implement nice things such as joints, perspective, and even simulate depth of field. https://en.wikipedia.org/wiki/Depth_of_field Usually depth of field (DoF) in video games is implemented using a post-processing step that blurs the pixels with an intensity that is a function of the depth of the pixels. When we are rendering lines, we can approximate DoF directly when rendering the lines by having the vertex shader increase the width of lines and r...
1 comment
Read more