Starting my story-rich indie game - Godot Devlog 0

[@dreamsdev]

I really liked your devlog, it looks more professional than most of the devlogs I watch and the games sounds interesting!

[@IDENTICYEA]

i mean check out other you-tubers too

[@pixelpastiche]

Yo! Good 0th Devlog. If Art is more of your background, then I think that it might be helpful to let your art direction and storytelling focus your game design. For examples when you mentioned that your character is traveling around a post apocalyptic world from a storytelling sense is your character there to bring life back to the world just to survive? Based on your choices here this can not only influence your art direction but also the mechanics that will present themselves.For example: If your character is bringing life then is it by walking near something or touching something? That last question is about your code. For waking near something your can use simple signals from overlapping triggers represented as an invisible area around the character, and then you can use that code over again, but change the context of what it does through animation and finding out what is actually being brought back to life. That then takes you back to the storytelling elements and you can start the process over again by answering that question: "What is actually being brought back to life?" or take a different question like "Are there machines that can be brought to life?" But then again, all of that could be different if your wisp is just trying to survive, but you can use the exact same process to generate ideas there too. I'm in much the same situation of dev-with-a-dream, and I've found that trying and abandoning a lot of ideas effectively comes from consciously making a lot out of a little and giving at lease one concrete reason as to why something HAS to be there. The further you get into the process and solidify your idea, the less you will need this type of thinking, but in the beginning this ensures that everything keeps some underlying relation to everything else before scope and vision fully set in. Good work and good luck, let me know if this helps/makes any sense.

[@Skeffles]

Sounds exciting! Good luck on development.

[@sechmascm]

For the interactions I recommend you use Area2Ds in a separate layer that wait for you to be inside them (so a body or area entered signal) and press an interaction key like E. Then the interaction would trigger. Layers and masks are useful for managing collisions or making custom behaviours for stuff like an interactible or lootable

[@NirajArts]

Your devlog is awesome and exciting! All the best for further development! :D

[@GrahamOfLegend]

Great work with this devlog! Looking forward to seeing more / playing your game!

[@FlatThumb]

Good luck! it is quite the journey. Also love your character design with the drawn on eyes!

[@kairu_b]

Nice devlog!

[@masonictraveler6558]

How did you learn to draw in such a style

[@Iboximc]

To under rated

[@VenexsOfficial]

Nice video, how long did it take for you to make it?

[@xilurus]

about the span of 5-7 days ill say.

[@muppe8246]

Nice

[@papasalvo]

I will subscribe and follow your progress. Might I recommend purchasing a Thronmax Mdrill 1 mic its about $80 USD and sounds great out of the box

[@monstereugene]

Why is your face sprouts sticky note?

[@xilurus]

That's actually one of the inspirations for the design :>

[@dominicwithers8516]

Hi

[@Alexey_Pe]

If you don't like coding, then why aren't you on an unreal engine, where you can make a game of any level and complexity using Blueprints, which were created for people like you. Why did you go to godot where they write the code ... I just looked and it turns out that godot has some kind of analogue to visual programming ue, but I would still recommend ue, because if you want to develop into something more complex, for example, multiplayer / 3d (all this in ue4 can be done on Blueprints), then on godot it will be more difficult. It also seems to me that you, as a more creative person, will like such a thing in ue as niagara. If you think about testing ue, then it is better not to use ue5, since this is a test version, better a more stable one, for example 4.27. Translated from Russian, I hope the translator did well and I won't have a lot of mistakes in the text)

[@xilurus]

that's very interesting! I never got to testing UE so I didn't know about these information like blueprints. They sound very useful! When I want to expand my ideas to a larger scale I might test the engine out :>

[@pixelpastiche]

Я говорю через гугл перевод. У движка ue есть хорошие функции и возможность встраивать чертежи, но с этой функцией легче ориентироваться, если у вас есть некоторый опыт работы с игровым дизайном и 3D-играми. Годо хорош для новичков и особенно для тех, кто сильно фокусируется на 2D, потому что он разработан в первую очередь для этого типа игр. Godot с открытым исходным кодом также позволяет группе людей в сообществе создавать вещи, а затем добавлять к ним новые функции одновременно. С Ue вам нужно быть более глубоким, когда дело доходит до решения проблем, а чужой код может быть труднее найти. Однако когда у людей есть опыт, они, вероятно, обратятся к Unreal, потому что что-то заставит их сказать: «О нет, мне нужно, чтобы Годо сделал больше!» Теперь это больше похоже на «О нет, я даже не знаю, что Годо может сделать в полной мере».

[@Theraloss]

UE is all about 3d, not 2d. Furthermore, you **must** know C++ to use it, because it's impossible to create a game without coding at all (well, there are software that allows you to, but not UE). It's true that UE has blueprints for common actions, but Unity does as well and for Godot you have a lot of options too. For 2d I would definitely go with Godot or Unity: the first one has the simplest language and we love open source, right? Unity, instead, has more of community support (of course he does) and behind the scenes it does a bit more stuff than Godot, but I'm pretty confident to say that choosing Godot for a 2d project is a great choose and you won't regret it.

[@Alexey_Pe]

@@Theraloss Do you have experience with ue4? I have been using ue4 for a year and right now I am successfully making a multiplayer game, and I confidently consider your opinion to be incorrect, you do not need to know C ++ to make games in ue4, this is the maximum misconception for a person who most likely did not even open uе4

[@pixelpastiche]

@@Theraloss You are flat wrong about UE4, and I do not know how you came to that conclusion in any way but ignorance or misinformation. Godot is a great choice, yes, but your reasoning and equivalence of experience as to why is just not good.

[@rojobaSC]

not going to happen. scope is too big for your first game. also GDevelop.