Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi NerfedAce,

I did your survey to the best of my abilities, but found it not very applicable. A few quick comments and suggestions for further surveys:

- If you make a question mandatory there should be an option "not applicable". There are no "enemies" in my games, at least not in the form of animated 3D models. I have a collecting game, building games, puzzle games and an economic simulation so far. The enemies - in the broadest sense - are the ocean, gravity, terrain, costs ... The only game where the enemy is a character is my detective game - but the murderer isn't visible (the point of the game is to find out who it is).

- I also never purchased an asset and downloaded my last free 3D assets years ago. The only assets I can't make myself and therefore download is music. There are several reasons that don't download animated characters, but you only allow for one answer. And the most important reason for me wasn't even listed: I don't get everything I want in a consistent style. Beside that I love modelling - it is one of the things I like the most about my game development hobby. So the assumption I would want to minimize the time I spend modelling is as if you'd ask someone who knits as a hobby why they don't just  buy their sweaters.

- It is considered good practice in a survey to ask a general open question like "Anything you'd like to add about getting 3D-characters?" at the end. Also if there is the option "other" the should be line to fill it in. 

Thank you for taking the time to complete the survey and for writing such detailed feedback. I really appreciate it.

You raised several good points, especially about having a "Not applicable" option for mandatory questions, allowing multiple reasons where appropriate, and including an open-ended question at the end. I can also see how some of my questions assumed a particular type of game or workflow, which doesn't apply to everyone.

When I designed the survey, I intentionally kept the options fairly narrow because I was trying to collect specific data that would be easier to analyze. In hindsight, that also made the survey less applicable for developers with different experiences, like yours.

I'll be revising the survey based on your feedback to make it more inclusive while still keeping the questions focused on the data I'm trying to gather.

Thanks again for taking the time to help improve it. Feedback like this is genuinely valuable.