Asklemmy

43803 readers

742 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

How do solo devs make an entire game themselves? M (discuss.tchncs.de)

submitted 3 weeks ago by dependencyinjection@discuss.tchncs.de to c/asklemmy@lemmy.ml

43 comments fedilink hide all child comments

So, the question seems vague but I will elaborate.

I’m a software developer, but I don’t do games; yet I have an urge to try and make something.

It just seems so overwhelming, I know I want to make a game where the main character is a cat and you have to complete missions, but where do you even begin. Where does the art come from? How do you refine your idea, if all you know is you want a cat game? How do you choose an engine? Do you just start with the basics and get a cat walking around and see what comes next? If you can’t hash out the idea then so you have a right to even try and make a game? Is it best to follow tutorials to get used to making games? I feel the answer to that is no as before I become a software developer, tutorial hell was a thing and I realised I needed to make things for me to actually learn.

Sorry for all the questions, this was just a stream of thought.

you are viewing a single comment's thread
view the rest of the comments

[–] Paradachshund@lemmy.today 11 points 3 weeks ago (3 children)

One thing I'll throw out there is while there are rare cases where a solo dev really does everything themselves, when you see a really ambitious looking result from a supposedly solo dev, it's very likely they either contracted things out, bought/found assets, or had on and off help from people. It's only solo in the sense it's their vision and they get to put things together/make all the final calls on the game.

Making stuff solo is hard. I'm doing it right now and I'm purposely trying to use a lot of stock assets for art and music because the game alone is already a massive task by itself. Don't be afraid to use what's out there. If your game feels good to play most people will never worry about whether you hand built every blade of grass. In other words, go for as small a scope as you can, and don't be afraid to cut corners.

[–] dependencyinjection@discuss.tchncs.de 6 points 3 weeks ago (2 children)

Thanks. This is likely very true, I think Stardew Valley is a game where the dude did it all, but I guess that’s the exception and most games are collaborative efforts.

[–] codenamekino@lemmy.world 2 points 3 weeks ago

If you end up going in the Godot direction, a friend of mine has some useful tools to easily get started on animation rigging and controllers here.

He got started a couple years ago with no game dev experience, and he's done a couple of game jams recently, but most of his time has been spent building workflow tools. A couple months ago he finally got around working on one of the original games that he's wanted to make since he started.

load more comments (1 replies)