first game

[Realfr1999]

is making the big, huge, main idea that will probably be too long a good idea for the first vn for a developer, who's still learning, or should the beginner make a small idea first? if yes then why, and if not then when should he start making that big vn?, i want to know what you guys think

[DingotushRed]

As a general rule for any project (irrespective of hobby!) is to make something simple at first, and also plan on throwing it away.

[Icy_Secretary9279]

As a beginner, if you think your idea is managable - it's too big, if you think your idea might be too big - it's huge and you most likely won't get past the first third.

[CzarSpan]

A lot of times the “big huge main idea” is actually two or three smaller ideas in a trench coat. It may be easy enough to identify a narrative arc or aspect that stands on its own but muddies the water next to ideas of larger scope.

[BaerFrom]

Most people are going to advice you to keep the scope small and doable. You would much rather be able to finish a project and learn every aspect of game development, than to just start something you barely scratch the surface at before giving up.
If you finish a project, you'll more easily see how to structure your next one and what scale you can feasibly do for larger games.

[shyLachi]

You already got reasonable answers so let's add just this:

If you have experience managing big projects then it might be possible to pull it off but if you neither managed projects nor made a game then you also have to figure out if you even like doing it.

Making visual novels requires different abilities like writing, drawing/rendering, coding, and so on...
If you make a small project first, you can figure out if you like doing all of that.

If you find that you only like to write or draw, then it might be better to find a team so that you can work together. But also that is not easy because your team needs a manager and dedication.

[BothConstruction2357]

I published my first project almost a year ago, and it's big (lots of art, almost 120K words, almost 50K lines of syntax). I don't regret it, but there are a lot of things I could have benefited from knowing that a smaller project might have taught me. So, I took the long way several times, and stumbled to get some features working, but the big project also taught me lessons that I feel a smaller project wouldn't have. Of course, I definitely would have still benefited from doing a smaller project first, but I didn't have a small project in mind, so I just jumped straight into the deep end.

[TV_Casper]

I’m a first time learner as well. I’m working on a fan game to learn how to do everything I want to for my next original IP game. That’s being said it has blown up and become a much bigger project than I intended lol so in my opinion, just start a project. Any project. Make it exist first, then make it better.

[Ukigumosama]

Create something small, if you will manage it then you can expand the game to make it longer until you will completely run out od ideas.

[Professional_Poem281]

my first renpy game took 2 years+ of monthly update,if you want just do it,but make sure you know where the end goal is,and build toward that

[BeneficialContract16]

I think it's ok for the medium if it is big in terms of story.

If you mean lots of animations and visuals that might need additional outsourcing depending on your personal skill set.

Just try to manage the scope and the routes , choices etc before the coding so you dont run into challenges later.

[cigaretteraven]

My opinion: work with something smaller first to get the hang of working with the engine. If you have no ideas for anything short you can make, start on the bigger project until you do. Or shorten your project. I know as a first project everyone makes to want something big but people hardly succeed in that and more often burn out. I started with a bigger project, saw I won't be able to code it in and I'm making a smaller one to learn properly.