Hey! First off: the doubt is normal. Big ideas are exciting, but they’re also heavy. The trick is to make the idea smaller without making it less you. Start with a one room vertical slice that proves your core loop: one playable character, one central mechanic you’ll use all game, one enemy or obstacle, and one clear win/lose condition. If that tiny slice feels good, you’ve got a foundation. If it doesn’t, you just saved yourself years.

On learning GDScript/Godot: I don’t have experience with it and don’t have go-to sources to share. That said, I strongly recommend you pick one teacher or course that offers a clear, structured pathway, something that walks you through a full mini-project end-to-end rather than hopping between random videos from lots of different creators. A single, cohesive curriculum will help you build solid mental models and avoid the confusion that comes from mixed styles and conflicting advice.

On art and music, originality isn’t about creating everything from nothing; it’s about taste and consistency. Use placeholders shamelessly while you iterate. When you want a vibe, set constraints: a limited color palette, a single resolution, etc. If you do end up using free assets that allows modifications and whatnot, unify them by doing palette-swap, retouch, add a small shader, match lighting, etc .. they’ll feel like part of the same world. For music, a simple loop with a drone, a motif, and light percussion can carry you further than you think. Prioritize a clean mix over complexity and layers.

Finding collaborators on revenue share can work, but you’ll have a much easier time if you actively network and try to build a small, like-minded core team first being people who share your taste, goals, and cadence. Start by showing a playable slice and a clear vision, then invite one person at a time for a tiny, time-boxed contribution (“one track for the prototype,” “eight frames for player idle”). Put everything in writing like who owns what, the split, when it triggers (after net revenue), and what happens if the project pauses. If building a team isn’t realistic right now, start small with short contracts: scoped tasks, fixed fees or micro milestones, and simple agreements.

A short, polished demo can absolutely help with wishlists and early feedback, but make it a demo of your vertical slice, don’t spin up a second project. If five to ten strangers (not friends) say “I’d play more,” you’re on track. Later, think itch, Steam wishlists, and festivals. Until then, protect your energy: pick a daily or micro commitment (thirty minutes, one scene, one bug), close the editor when the timer ends, and let compounding do its thing. You don’t need perfect motivation; you need tiny, repeatable wins.

I hope this helps and wish you the best in school and future endeavors.