This channel is like watching someone learn 30 years worth of lessons that the software engineering industry learned the hard way. Except instead of picking up a textbook, you just learn them the hard way again. It’s awesome.
Wow this is so apt lol. Yeah you're exactly right. This is why I love this channel. I feel like it mirrors my own learning experience but this guy is way smarter, and there's single videos covering things it took me years to figure out lol
Actually I do believe he is going places.. I've seen people read relevant books and not being able to make use of that knowledge. Learning something the hard way can really make it stick. Plus, I believe it is perfectly fine to set oneself a goal that might be unachievable in order to learn and exercise new skills. And as this current video clearly shows, the meta-skills like "how do I work on a project in the first place " are part of that as well, increasing chances of finishing the next project. And while the videos might look like there is no delivered "product" after all these efforts, I'd like to point out that we are discussing this in the comments of a video that has meaningful content, a characteristic style and editing 🙂
I want to add on here that it's not just game design, but code design itself. If your code are just getters and setters and raw access to everything, you are asking for bugs and failures and roadblocks when you realised you can't do something without hacky workaround A good design, even during your practical programming exams, will let you design and abstract away different parts of your code that have good type-scoping and "tell, don't ask" styles and object inheritance and even monad designs that can make life great (without feeling like you're cheating with some library) Tell, don't ask and SOLID design paradigms are great when done right, though not fun
I think recognizing where one has made missteps and trying to actively correct them is a huge part of "failing faster" people don't talk about, you can fail at sonic speeds but your failures won't mean anything unless you learn from them, so a fantastic post-mortem dissection like this is a way to grow even stronger from your failures, I wish you the best of luck for your next game!
scope resolution and not pay enough attention to the game loop is unfortunately very easy to mess up. i had that exact same problem when i started out making games with SDL2. glad you were able to recognize this! also something called "paper prototyping" is actually a very powerful tool to test if the game is even going to be fun. no coding required just paper and a few pencils or art supplies depending on how crazy u wanna get with it.
> paper prototyping may i introduce you to procrastination prototyping, where instead of making something, you don’t, but you still think about it for months. given enough time and knowledge of related concepts you’ll eventually figure at least some of the problems out
I’m making my own game/engine, and I’m guilty of the same mistakes. I’ve been working on it for 7 years, and I’m nowhere close to done. But, I keep working on it, because I enjoy doing it. It’s a constant challenge that keeps me busy and entertained. Making a game is the greatest game I’ve ever played, even if I never finish.
@@test-zg4hv doing hobbies for your own enjoyment versus doing hobbies for the algorithm tm are two very different things. You can't just upload footage of writing code. You need to do voiceovers, and explain your thought process. You have to edit videos in a way that holds the viewers attention. It isn't as simple as film and profit. There is a reason yt videos have high production quality. So I don't think it's a dumb idea to not subject yourself to the pressure that is RUclips and waste time without making money
@@Barely_Edited there's no reason not to, if I enjoy doing something I eventually get good at it so why wouldnt I want to make money off of it so I could spend even more time doing what I like?
just wanna mention that the work you *did* with graphics and such was incredibly impressive and no doubt valuable to your long-term knowledge as a game developer. the benefit of things like this are not entirely immediately clear. you learned a lot.
You say you're not good at art, but all your art is very aesthetically pleasing. Honestly man you're an inspiration, building engines from scratch and making good pixel art
Thank you so much, am a beginner developer and something that's rlly hurting is my game design skills, ive dropped so many projects because of this but honestly this video sums up everything i did wrong in my failed projects, now i hope my game design skills improve haha
There’s a reason I have two game projects that have a “permanent” place in the back of my mind. Slowly cooking until I can construct a satisying gameplay loop/idea to connect the rather scattered ideas I have for each. Writing ideas down and trying to connect them ocassionally. It’s really helpful that way!
In conclusion: you started to build a house but you didn't even have the blueprints In any case, I like you because you do projects in a different and rustic way. I'm always glad to see you programming in C++ and using neovim even though I don't understand either one
neovim honestly isn't hard to setup, just use astronvim to setup neovim with syntax checking and stuff. once you're used to it, it is so so much better than most GUI ides
The only people who don't makes mistakes are those who aren't trying. I count my mistakes as tokens of progress. One thing I've learned over the years is to always always always design something thoroughly before you build it. That way you can have a good idea of whether it will actually work or not before you start to build it and potentially save you from hitting a dead end.
I've always gotten a "city of ember" vibe from this- I'd like to see some sort of continuation - this is the creative process, nothing wrong with it. No mistakes only happy accidents, and you never start from scratch - you start from experience
It was a book about an underground city- all they had were candles and streetlights so the city was colored amber, they'd been down there so long they forgot the surface existed- but when the generators thatve powered the city for hundreds of years start cutting out and a child finds clues that the cave isn't all there is, they and their friends search for an exit. They find a river that leads out and see sunlight
Honestly, the idea of a robot in a cave planting stuff has room for interesting mechanics. Off the top of my head, I can think of one idea: 1 - the robot is like Wall-E, and is trying to terraform a cave through planting various plants with all kinds of functions, with the end goal of transforming the atmosphere inside this enclosed cave system into a breathable atmosphere. The atmosphere wouldn't need to be like earth's, either - you could have room for different levels by having different atmosphere goals, each of which would present a specific challenge. For example, one plant takes in one type of gas and outputs another, but requires a specific terrain and a strong light. How do you achieve it? Other plants with more basic functions - like a plant that glows, but requires being planted on a specific rock or soil. Also, you could just ditch physics an go all in on magic. A plant that creates a gas barrier, but allows solids to pass through. A plant that breaks down rock into a specific soil, then dies. A plant that dissolves rock around it into a fluid. A plant that... you get my point. Kind of similar to Botania (mod for Minecraft) x Factorio x Terra Nil. But yeah, your game right now is an overdeveloped tech demo - just showcasing what your engine can do. Maybe just reuse the engine and try to make a game from scratch, but this time with a goal in mind?
I was thinking an ARPG with crafting elements, perhaps an alliance between plants, robots, and few surviving humans defending earth from an unknown threat. Lots of room for exposition through gameplay. I really like the vibe of the engine as well. I could definitely see a spin on ARPG combat with tower defense, realtime or turn based; resource management and crafting/harvesting. I also just love the theme of plants and robots.
Something like, idk, Icewind dale meets Zelda 1 meets Diablo for combat, and Starcraft meets plants vs zombies, on a background of Star dew Valley and Don't Starve? With automation like factorio... I think the mashup of style could be excellent, and would be a formidable challenge balance-wise. That'd be shooting for the moon for sure, with both real-time and turn based elements to implement (maybe just real-time that allows pause for management/stacking commands?) but having layers of gameplay like that seems both fun and ambitious. I'm just wishful.
The stuff above is what is missing within this game's design. It needs more brainstorming and more bullet point style notes of what you can do with the concept, where to take it and so on. Discarding the project now isn't quite necessary. Plenty of mechanics would work with the premise that already exists now.
that's what i was thinking, the engine is there and a base thematic is present, just needs mechanics and purpose. This can be saved imo, the creator just needs to decide on something instead of adding bells and whistles
I think you're right. A space colony game in which you play as a robot preparing a cave in a spare planet for humans/other intellingent aliens who will arrive in the cave later would potentially revolve around an enticing gameplay loop of cultivating an ecosystem of plants to produce a livable atmosphere as well as potentially fighting off hostile fauna to clear out and protect the colony cave. Heck, "Colony Cave", man that's a heck of a title right there! This gameplay loop would include those elements he mentioned as means to an end; crafting would come about as a way to make more weapons or resources to fight more monsters or maybe splice plants together to create new ones to achieve a desired atmosphere. Exploration would be an essential component of gameplay as you wouldn't be able to finish making the cave livable without exploring every nook and cranny for more monsters who could pose a threat to your colonists or looking for resources. Procedural Cave Generation would mean making the game far more replayable as each cave could be abstracted to be another cave on the planet somewhere. Heck, he would even have good motivation to go even further and develop features like multiplayer so that more people could colonize space caves together. It would have been like a little like Deep Rock Galactic but as a long term colonist instead of a "Get in and get out" space miner. I don't think this engine is a lost cause at all, as he still has the code and he has systems in place that he can quickly use to assemble a gameplay loop. However, I think he needs a good pitch and a good primary core gameplay loop in mind before he attempts this project again, and I think the "Robot colonist colonizes dangerous space game for humans by battling monsters and cultivating plants" approach to a primary core gameplay loop is punchy and effective because it would give him some smaller systems he could build immediately (such as basic combat with monsters) and give him an end goal to think about when redesigning his plant biology systems.
This video just solidifies the idea that every game developer should have gone through a little game design course and understand how to structure your idea and how to develop it so the risk of failure is lower. I've learned a lot in uni in this regard and I am ready to work like a pro... (sorta)
Lol, there's no way such a design course prevents you from failing at game design in general. Proper game design is like writing a music song. The first hundred or so attempts will fail, the next 20 to a 1000 probably will never become truly good, let alone original. Making a good videogame is difficult. Cloning other people their existing concepts is easy. Hence, why most games out there are kinda variations on existing stuff. The 'game design' courses in uni are usually about showcasing existing designs. It's rarely ever about _real_ game design.
Maybe it just needs a story, a goal, and an end game? What if the robot returns to post-apocalyptic earth in order to rehabilitate it? What if you start out by cleaning up trash, recycling materials to build useful tech, then use that tech to incubate better atmosphere and environmental conditions, which allows for seeds that were found in a seed-bank underground to begin to reproduce, cleaning out water supplies and decontaminating the land, slowly reintroducing and growing plant life to the point where it's producing enough oxygen so that the humans in space can return and begin recolonizing the planet in the end? That was my idea for a game, and then I found your channel and realize you were already many steps ahead of me in building the same game, but without the guiding story and goals. I was really excited about this project!
Failing fast and often is such an important concept to learn with programming. A lot of my early projects failed because I wanted to make things as absolutely perfect as possible, and I got stuck in refinement hell. I should have been adding features, but instead I was writing and rewriting the same thing over and over, because I wanted to be sure I couldn't build things better than I already did. But that's the thing; there will always be a better way to handle something, and code is never perfect. It's important to recognize that, and build what's fun.
As long as you're looking at Jon Blow, it might be helpful to find video of what Braid looked like before he hired an artist (he's done at least one talk that shows this) and to look at the old streams he did at the start of his current Sokoban project (you can find them on his youtube channel under "Game Engine Programming"). If you're not making the game around the art, that's probably the level of polish you want until you have interesting gameplay. Keep in mind also that Jon Blow did contracting work in the games industry for years before he shipped full titles by himself. I think a lot of the "Handmade" and adjacent communities want to go directly towards an ambitious project after they hear him speak, but I don't think you can skip the "many small projects, done competently" phase
It's an unfortunate conclusion, but i understand why it had to be done. Thank you for giving us this update video, and good luck on your future endeavors.
Local game engine maker discovers that game design is important, seeks to go study that now. Sure, you got pretty far along with the game and the engine and could have done well to prototype, but you at least managed to catch yourself before the sunk cost fallacy overtook you. And you have a game engine on hand now! Maybe the game didn't work out as a game, but instead as a tech demo. Sieze the chance to fail fast and figure out a direction, before sticking to it and proceeding. I highly recommend the series "Developing" by GMTK, there could be some lessons from the process they went through that could give you some ideas. All the best!
Dude, it is extremely impressive what you've managed to do by yourself. I'm just trying to start as a game developer and I imagine it would take hundreds of hours to build something like this. That is why it pains to see how much your game lacks direction in terms of game design. it may sound presumptuous (and it is), but if you feel like it I can talk to you in discord over voice or chat to help bounce some gameplay ideas off me and shape some image of a gameplay you'd like to build
The problem is that ideas have a low chance of being fun, so it’s best to test a bunch of ideas quickly before deciding on one instead of just starting with an idea and blindly building it hoping it works out
Good insight and learning experience for you! Regardless of the project or not, it was a great way for you to warm up to everything you're doing! Looking forward to your next reveal. Awesome seeing your Patreon! Keep up the good work and be sure to take care of yourself too
At worst you still made a really cool tech demo! As a software developer (mostly C) by trade, the programming and tech that goes into games has lots of really fun problems, but games themselves and game design are not especially interesting to me. It's funny how many programmers end up doing game related things as a personal project (myself included). My theory is just that its the most accessible and easy to distribute form of software out there, and there's always lots of game ideas floating around in everyone's heads. I think there is always something pulling at me to be idealistic about the idea of making an entire game from scratch all by myself. But at the same time when I really dive into doing art or spending a lot of time doing game design I realise that it just isn't where my particular talents lie. Of course if you enjoy doing art and game design as a hobby its an entirely different story, but for me personally I'm always having more fun when my time is being used as efficiently as possible contributing to whatever I am best suited to tackle on a given project. I have learnt to never discount the value of getting together with a friend who does art or game design, so that everyone's talents and time are utilised optimally! Keep up the great work!
Wish I had a programming friend lol. I m stuck with all these game idea's but fail at the programming stage... No matter how much I dumb down the difficulty of the programming aspect.
@@GodofGamesss it's definitely a steep learning curve but it's very liberating when you actually figure it out. You just keep trying till you get to a point where you have enough basic information to teach yourself the rest. You just have to be persistent and patient.
You have achieved a very unique and appealing art style, which is often half the battle for creating a successful game. Just because you don't have good gameplay mechanics yet doesn't mean the project failed, there is plenty of potential and you could also crowd source ideas and let people vote on the best ideas. There's clearly a game there waiting to be finished, you just need a clear path forward.
Thank you for your candor! I think that temptation to indulge in execution is an lifelong pitfall for us creative types who are also technical. We love being able to make something come to life and there's always a cool new tool or technique to learn, but as you said the end result of that is often a disjointed project full of very cool parts that don't join into an entertaining whole, and premature optimizations that might not have been needed. I've definitely had my share of projects fail for that reason so you're definitely not alone!
For me it's the opposite. I love thinking of the design but dread actually programming the mechanics. But I have gotten a lot better with that in past year.
This is the feeling I get watching Duke Nukem 3D get played. It feels like the tech was spun up first and then everyone was like "oh crap, we actually need to make a game" and whipped out whatever they released. Same few enemies available the entire game, a bunch of lame puzzles that take no skill to do (just some trial/error/slowing you down), and menial maps. The only thing it had going for it really was the shear amount of stuff to get stuck in and the World Wide Web nowhere near popular or dynamic enough to handle a community around it. What they accomplished engine/capability-wise was neat but that's it.
Hey man, been watching for ages. last time I commented was during that CPU build stream (asking if it would ever be put in a case) Either way, I really enjoy the channel; your calming voice, coding skills, and frankly amusing content always make your posts the highlight of my day. I cant wait to see this new project! P.S. RIP little robot.
Reminds me of Randy with arcana really bad. Dude focused WAY too much on the technical, engine side of things to a similarly extreme degree, until he gave up on it entirely.
Weirdly enough, I have the exact opposite issue whenever I work on a project. I spend days before actually starting a project thinking about ideas for it, how they fit together, how they would work, etc. But the issue is, I can never actually figure out how to create systems or make things actually work. I can know exactly what kind of thing I want to make, but then fail to actually execute it in any meaningful way because I'm not skilled enough to actually apply my ideas. This is the exact opposite of the problem shown in this video, where most of the effort and skill is in systems (things like the game engine, entity system, graphics. etc.) rather than the actual game design that those systems are supposed to support. This is probably the reason why people create studios and work in teams instead of just one person doing everything. Unfortunately, I and many other people do not have the luxury of having a team to work on projects and have to deal with our own issues when it comes to things like this.
Now that I'm working on my first game it's so strange/interesting watching people's dev logs and seeing what their strengths and weaknesses are when I pretty much just took it all for granted before. I have all the art skills but just baby coding skills and I'm trying to avoid making a spaghetti mess even though it's probably inevitable. I would have taken the advise to start smaller, make prototypes, etc, but the game I'm working on is already something I originally wanted to make an animated series out of that I postponed for years til "the time was right", so I said f it, we're doing the big thing now, so we'll just see how this goes. 😅
The idea of a robot awakening after God knows how many years in a deep underground cave system is so fascinating to me. The robot would immediately get to work to build an ecosystem capable of giving the humans in the surface oxigen and what not having to battle the local fauna, other rogue robots and battery issues. The end goal would be to make it to the surface but every floor would require certain stack of resources and materials to mine your way up, coltivate certain plants and gather specific materials in a system reminiscent of Fallout Shelter with advance survival elements, also the more the robot would climb to the surface the more dangerous and resource heavy the journey would get. Also the more the robot would get closer to the surface the more about the lore the player would get to know. (I'm imagine a post apocalyptic scenario obviously). Spoiler . . . . . . . . . . . . . . . . . . . . . . . . . In the end the robot would find humanity already went extinct centuries ago and the voicemails he was recieving throughout the adventure were a product of an AI, during the adventure tho the robot would have face many decisions (taming animals, reprogramming rogue AI instead of scavaging them for resources, choosing to prioritise certain plants to gift the humans with different benefits and so on) bringing him more closer to develop a "human soul" of somesort. Maybe after all a human did actually reach the surface, only not in flesh and bones.
It's okay to fail. At least you pulled the plug now and didn't work on it for several years. It's nice to see you talk honestly about it. Already hyped for the next project. You are still one of the sole reasons I use RUclips and a freaking legend.
For prototyping, there's a reason why we use "dev art", which is literally the most basic colors and placeholder assets to only focus on making the gameplay fun, not on making VFX "cool to look at." Sure you can have an idea of the kind of aesthetic and story you want, but that's more for the pitch after you refine the mechanics so the prototype is FUN TO PLAY. To summarize Thomas Brush's advice on how to even with video game creation: get a cool idea, iterate on it through a game design doc, get a time+money budget, then make the best prototype you can and pitch to investors so you can evolve it into the game you want to play courtesy of workers you hire to help you out. On the plus side, you do have the curiosity needed to make a game engine to iterate upon these ideas quickly enough to create a working prototype of any genre of game you like in a month.
Currently in the midst of prototyping a game right nowm. Glad i did it instead of my usual mentality of dreaming big. My intentions with what im building right now is itll probably get nuked but it will hopefully make for a good demo of what the game is supposed to be. Have made the mustake of making tons of art, with this its basic sprites and all my focus is being dumped on the gameplay. No matter how it looks, if it doesnt feel fun or like a game youd enjoy playing even as basic as it is, you need to make a change. The general mentality is graphics good = game good, but graphics should always compliment the gameplay
I'm going to be honest, this outcome was immediately obvious to me from your initial video. However, all the dev logs have been entertaining, so I'm glad you realized before you had even more time sunk in.
I love the idea of a lil' robot whose whole purpose was like cleaning up nature who falls into a little hole and finds a fascinating underground ecosystem! Then having to survive bad plants, catalogue unknown plants and solve puzzles using abilities from those plants while trying to find a way OUT of the cave. Maybe even generations of robots who tried and failed are able to be downloaded and each give small little tidbits of info or maybe a fun power up! Gives me ideas like a light reactive flower that when light shines on it then it unfolds into a platform, when you water another flower (which you have to find a water source to obtain water first) it maybe grows like a vine upwards, weeds that try to maybe get in your tires to stop you, acidic plants that try to melt your iron, having to mine iron to repair your shells, having to craft spears to fight off enemies with and maybe refining a mysterious ore found under the ground! It would be a wonderful chance for ambient storytelling as well! I am overflowing with so many cute and cool ideas! I hope you continue you it and feel free to steal any of my ideas from this but I really can't wait to see where you go.
I often find myself daydreaming about how game mechanics could be improved in existing and even AAA games... what comes to mind with the game you were trying to make here is to make it an isometric 3d roguelike or even metroidvania.
Hey that's the reason I love to watch you do your stuff. I work in a company where I do Java 8, the slightest change to anything has to be double confirmed by management and that implies writing lengthy risk analysis and feature details and blablabla... You wake up in the morning, take a shit half awake, and tell "hey what if I spent 6 months building a runtime broker for a super computer ? I'll figure out the need, the cost, the time needed along the way." then proceed to take your coffee, mumbling to yourself "i kinda love Pascal, maybe I should code in Pascal" and you're set for half a year.
After those past few videos I was a bit worried, but if you go back to C I feel like you'll have really found yourself. I know people think such things can't be done in C, but they most certainly can and having someone prove it by writing a more modern game that way would be a great inspiration. Who knows, maybe I'll finally get off my duff and write my own game.
I know this video is 2 months old, but I do want to comment to say how this video shed some light on the game dev process. I'm a game developer major in uni, and seeing the lessons you walked away with reflect in my work is very interesting, especially with how my professors set up content and work. The first thing we've been asked to do, in my multiple classes which ask you to develop your own game, is to give an 'elevator pitch', the one sentence idea you talked about. Then we are asked to design those, creating a document to better serve our future plans, then we do a basic prototype. Talking about 3 hours of work total, prototype. Seeing you extrapolate all of these same ideas from your project is very inspiring! I hope to get to a level where I can ask these questions to my own projects, and even begin to code my own engine, like you!
This has every bit of potential to be fleshed out. The grass spread, the planting and bringing color back is a wonderful element. Maybe a more limited world, with a specific goal in mind (i.e. make the gray ground 100% green, cover 50% in plants), and a result of the goal (i.e. a spaceship comes back to a planet once thought devoid now full of life, and has the tools to repair the robots friend/lover?/companion and ro-botanist can happily plant flowers with them). I feel the wave form collapse can still be implemented, making every new game you play different. Maybe an element where some things only appear in some random generations, and not in others (a way to do easter eggs). Of course, taking another idea and using it at your own is the opposite of your point in making an engine, or any project you have really. But, if you outsource for a few parts like that, you could easily flesh out this wonderful and beautiful game idea!
I like this channel because it chronicles my own larval phase of maturing into a coder. I wanted to do everything myself, to use ASM for everything, or even better, write a compiler in assembly for a language I would design myself. I made my own databases, my own assembler/disassembler, my own templating framework for web apps, my own server, my own unit testing framework, and yes, of course, my own game engine. Slowly but surely I discovered every rule of better software design by breaking it and finding out why the rule exists. Honestly, I think I'm a better coder at the end of it than I would be if I just read the rules in a book without an exact understanding of the consequences of breaking them. My reaction to bad code is visceral. I can see problematic patterns as they emerge in new situations without needing it to mirror some scenario I read about in a book. As a result, I can successfully use frameworks that are developing and changing, I can jump into a large project and hit the ground running, and I can write code that can be customized and maintained without changing any code at all. I'm sure someone wants to tell me that you could do all that just by following rules they memorized, but I don't think that _I_ could have. So don't get down on yourself when one project fails spectacularly. You learn your lesson, you let your mistakes scare you out of doing it the same way again. IMHO, it will make you a better coder in the end.
I mean nothing but positivity in this, but thank you for failing like this. (And for showing the rest of us). I’ve been theorycrafting a game for the past 6 months and anytime I try to start coding I always get hung up on engine stuff. Seeing just how many of your failures resolved around not prototyping has really inspired me! I think I have a core premise down pat, but thanks for showing that I really DO need to make a quick-and-dirty solution to be able to put the game FIRST.
Yeah, saw this coming from the start of the series. Tale as old as time. So preoccupied with whether you could, etc. Oh well, looking forward to the next one! That blurry preview looks like there might possibly be some procedural terrain generation involved? If so, can’t wait to hear about it!
4:42 this is a trap ive seen a lot of solo game developers fall into of seeing games like skyrim and terreria and trying to make a game with many systems and tons of content but no central mechanic (not that skyrim or terreria dont have central mechanics but that people think that all that makes them fun it having tons of content). Glad to see you've caught yourself learnt from it and good luck with the next one
I find it interesting that you've decided to shelve the entire project. I could imagine building an awesome gameplay loop off what you already have. My first thought of a game I could love is something along the lines of: You're a robot herbalist/alchemist. You're trapped 100 levels below the surface. You don't have any direct combat skills so you need to use your growing & alchemy skills to slowly work your way up to the surface. The core gameplay loop would be something like: 1. grow + crossbreed herbs (I'd have some kind of small chance of random mutations (well defined though, so like this flower can have a variant that it occasionally mutates into, or if you crossbreed x with y you sometimes get z), and they all have different properties that affect your alchemical recipes (and obviously you need certain herbs for certain recipes) 2. process your herbs into alchemical concoctions, these enhance your robot in certain ways and allow it to actually progress in its mission towards the surface. There's lots of stuff you could do - gas style concoctions, self-improvement ones (e.g. move faster, maybe robot can briefly do melee damage), thrown potions, alchemical traps etc. maybe some meta-progression ones too if that's your jam. Lots of design space to explore here. 3. take your potions and use them to fight monsters, they get tougher and the levels get more complex as you get closer to the surface. Also you occasionally find plants that you can grow in your garden in the caves. You can add all the fun gameplay spice you want here too - e.g destructible terrain, interesting vision-using mechanics, more complex enemies, minibosses, large bosses etc. But I think you could do really well starting with something small. 4. And that's the main loop. Grow -> alchemize -> fight + explore + loot -> grow -> ... It's also nice in that it's a gameplay loop that you can get up and running super easily (e.g. just have one or two alchemical concoctions initially, a couple of enemies with very simple AI's, and simple generated dungeons) and you can just keep adding variation to the gameplay loop as it inspires you. So you could e.g. add more complex inventory management and inventory based mechanics if you have a cool idea for how they'd improve gameplay. Personally I'd try to keep most my effort laser focused on plant growing and breeding mechanics (I've always wanted to make a game with a simple DNA analogue for plants and have Mendelian crossover etc. Kind of like the Creatures series (I was always sad how lacking the plant stuff was in Creatures, there was some simple colour mutation in some plants in Docking Station and I had a lot of fun breeding plants for colour even with just that, but otherwise plants were very static, but the creatures dynamic), but for plant breeding, but that's not something I'd start with since it'd be a lot of work to get right. And winning is reaching the surface to escape your sadrobotcave (that you fell into in a little cutscene at the start or your master locked you in, or your master died with you in, or... reveal a little of the 'origin' story ever 10 levels you explore in short flashbacks as a progression reward... or... pretty much whatever however you want to theme it since it doesn't really affect gameplay). I think thematically it'd fit the gameplay for the robot to feel very alone though, so I'd probably lean into that. Anyway that's what I'd build from your starting point! Maybe it's influenced by my love of roguelikes and roguelites, but done right I'd definitely play the heck out of it.
From watching the video it sounds like he already tried building off of what he had, in a few different directions, but wasn't able to make any of them it into something he was happy with.
The robot with flowers in a cave could be your first draft if you put more thought into gameplay. Imagine exploration where you have to grow plants to give you different effects, like healing, speed, haste and so on and as you explore the area around there are enemies you fight. Plants have a tech tree by cross pollination you need to research and learn first hand what each combinations does. Each cross pollination unlocks the recipe and what it does (after using the plant once) in a booklet your robot has and can open at any time to see what they need for specific effects. Imagine graves are around you have to find which have skeletons holding parts you need to make a portal and escape or something.
I don't know if it will make sense for anyone, but I've worked a lot on approach for creating plots(for any purpose) and game design. And I've come to such 'blocks'. 1.Idea: what do you want to tell person. Example: mindset if you don't wanna starve, you have to work, is not easy for execution, because world is much more complicated, and you can have traumas or the place where you live can have a crisis, or you will be able to change your situation only with time. so don't judge people quickly. if you don't want people to be rude with you(if it's possible), pay attention to their sore spots. 2.Goal: what you want to teach people to do.(it serves as goals for mechanics too) Example: empathy, don't make quick judging, be careful with your words. 3.Favourite moments: moments that you will keep as sweet and proud memories after finishing playing/reading/etc. It's clear value of your finished work. Example: when hero gave up his heritage for being with their love; when they saved lost dog, loved it very much, but decided to give it back to very lonely owner, who lost dog in his worst days, even though hero hates him, and could not telling him about finding it, after moving in nearby city. For plot it's enough and other blocks are quite common, so I don't mention them. And for game part. 1.Core mechanics: they are main instrument and reflection of ideas. Example: if main idea is don't judge people that have no work, if you don't know the whole story, then core mechanics could be: surviving: keeping stable sanity, and health parameters, by working at call center, bad phone connection will decrease your sanity empathy: if you want to get an answer, you have to listen closely and choose wordings, or they will hang up, you can get money bonuses for good service(don't matter it's not real) careful judging: if you'll listen, people will tell you their stories, and even can give you some advice for getting job, one of them even can get you an offer for some company with better conditions, it's long detailed surveys with repeating checking on clients 2.Tension-release-climax: rest and moment to wait for, to not get boring. Example: Rest = coming back home and talking to your hard-to-understand misterious neighbour, who could know something of the death, he's reflection of your level of convincing people; Tension = your normal job; Climax = checking days, when your phone calls estimated in real time(not real life, because calls are always recording; this checking probably don't exist) and they decide to keep you, kick you out, or raise your salary; 3.Game goal: long-term goal, that has clear instruction to player, and has a mystery(unknown = interesting). Goal appeals both to mind and to emotions. Example:to pay for the operation for the sibling to wake up from coma, who evidenced your parent's death(example), the more time pass, more memory loss they will have about traumatic expirience 4.Game conditions: why this goal is believable. Example: you need to raise money for sibling's operation, and this work is the only one that was available, and with flexible enough work schedule, and near the hospital, your credit limit is awful 5.Endings:criterias to get endscreen and what it is. It will shape direction of the game. Example: 1)you got offer from the client and easily raised the rest of the money, you know the truth if parameters are *Insert here* etc. 2)you didn't get an offer because didn't listen enough and keep working hard, you know the truth 3)you were kicked out from work and could not find new one fast enough to know the truth, but you can kinda understand what happened by neighbour info 4)... Something like this. Sorry, I got a little bit too excited. Examples are mostly for understanding of what I mean, not for perfect connections. It's hard tuning, I don't think it would be a big deal here. If anyone will get any use of this or new ideas, it will be great. Peace, people. Even if you will not read it.
I made a few games for Ludum Dare game jams, and found out not only is it hard to make a game from scratch and finish it in 2 days, but it is also even harder to make it fun.
I prettymuch knew this was going to happen with the first devlog, I have made the same mistake multiple times. you just have to do it, fail and learn to realize sometimes though
sometimes it helps to hear out others take on a given situation. drawing inspiration from their unique view and take it in with your own unique view. coming up with complex or symple systems together can be alot of fun and you might learn something about the process as a whole.
Game design is super cool. Like having a duel system and gameplay loops can be super fun. Even theory crafting is enought to make a game fun if you gave it enough thought. Also maybe you can make a discord for fast player feedback?
Great job, love to see a constructive introspection in game dev. I am sure you have learned a lot from this experience. Good luck in your future endeavors ;). You've accomplished in a short amount of time what Randy didn't even begin to ponder over in the last 3 years.
I would personally love to see this project open sourced at some point. I feel that there are some good ideas for gameplay that could be fully fleshed out and turn into a really cool game. If nothing else, it would stop some of the assets from becoming completely lost
Something that could help you to make gameplay (or not, idk), is that when you are making a game initially make the things you like and think it's fun, then ask for other opinions and then adapt your ideas, I don't know how to make a game (because I have like 12 incomplete projects), but I think it's that way you could make a game. (I haven't watched the whole video yet, so, I don't know if you said something like that)
I realise you've already decided, but I still wanted to share an idea: Combine your robot / underground / plant propagation concept with something like Factorio (extend current concept via automation), Opus Magnum / Space chem (create hardier / new plants), TIS-100 (program robot to do horticulture). Regardless, having an end-game / goal in sight is, I think, a good start. I am confident you'll produce something outstanding.
I personally just chose a game type and made the game modular. I then worked on making at least one module for each key part of the game, if I had problems with one module I would switch to a different one instead, just so I had everything needed for the minimum viable product. I plan on making alternative modules for each feature until I have at least 3 for each feature. Then I plan on testing them out and having friends and family try to find a good combination of modules that work well. I will then use that as the base of the game and work the other modules so they work as replacements for their respective modules I will then add additional features that can be toggled, and make multiple modules for different implementations of those modules I will play test and tweak any modules that seem to have issues melding with the rest, and try to make them all fit well no matter which modules are used. My end goal was to make it so people can create their own modules, but I don't have the skill to set up such a system. hopefully I will just inspire someone else to rip off my idea and take it where I can't.
Bravo my guy. This is something that less talented/experienced/motivated programmers often end up doing _better_ because there's a limit to how much they can go overboard. While performance (next to minimalism) is one of the best starting points for actual code generation, correctness and effectiveness metrics come first, since that is what you are translating into input/output descriptions to implement with code in the first place. In this case, a subset of effectiveness is design, so without it, you end up solving made up problems. This is exactly the type of primer that extremely motivated and intelligent programmers need early on, since intelligence is not correlated with wisdom.
I could see something intriguing being built from the underground version of the game. Using puzzles that let you reshape the environment by planting certain flora and waiting for it to grow, uncovering some mysteries as you get more access to the cave system. You learn it's the post-apocalypse, and the robots were made to regrow life on the planet in case of an ecological collapse, and now the robots are wandering around in the underground bunkers left by humanity that unfortunately didn't make it.
This video is just perfect, I'm also *trying* to make a game engine. I've restarted like 2-3 times. It's been around 10 months and not going to lie I made almost all these mistakes lol. Perhaps my biggest mistake was I expected too much from myself as I'm no professional. And, I didn't begin with simple prototype also ended up in a disaster. Now, I'm keeping it simple, doing tests, spending weeks on a single component (which is not ideal imo, I shouldn't spend this much on a single thing. If i change things in future, it'll be waste). Hopefully it'll work out
Step 1) Don't use object oriented programming, use procedural programming. Step 2) Don't learn quaternion physics for rotation, have a math library do it for you.
With such an interest in engines and programming, I really hope/wish you get into a game that is heavily simulated! Like noita or dwarf fortress. (Start smaller than those please though lol)
I think the robot plant idea is amazing. Imagine like dungeonkeeper. Planting mystical plants in carved out rooms to idunno. Conjure up elemental magic like mystical agriculture. From basic moss to life essence roses
This is why I like doing game jams like Ludem Dare where you have 48 hours to create a game for a theme. Spending that time to create a POC will tell you whether something will work or won't.
I’m going to be honest, I noticed some of these problems right away, but it was just too interesting watching you design the engine. In the end it was entertaining to watch still.
Here is my idea. Evil robots with pesticide spray cans come at night (since it is in a cave some other cicle like day/night) to kill all ur plants. You got to defend them, you need to plant the plants in a progressive way (crafting) to unlock bosses that you defeat and the game becomes harder like Terraria everytime you defeat one of the said bosses. As background story, robots took over and are sent to exterminate all plants, a shortcut made your system bug out and you want to save the plants rather than destroy them
great lessons here, and a great video to boot - but in my opinion your biggest mistake is one you're making with this wrap up video: you're moving on to a new shiny thing instead of finishing what you started. All of these mistakes can be easily redeemed, and (I think) there's a lot to be said for committing to shipping _something_ - the work that it takes to get there will not be easy but will give you the satisfaction of doing the thing you set out to do, rather than the gnawing feeling of always-moving-on-to-the-next-thing. Either way, I wish you good luck in your work - and thanks again for this insightful video!
Minecraft didn't have a core idea, it was only supposed to be a simple voxel engine project. If you add all of your random bits it will still make a fun game even if you can't summarize the gameplay in a single sentence.
All graphics and no core gameplay makes it feel like a tech demo. Like "Look at this cool engine I made! Here I put a little robot in a cave to show the cool lighting effects." I understand the approach. If I didn't watch multiple videos about game dev putting emphasis on prototyping, I would probably succumbed to my little writer/artist brain and made the whole graphics and lore of my first game before having anything fun to play. And to a certain extent I guess I do have that. I have plenty of ideas of stories and art directions that I would like to implement in a game. But, ultimately I now think of game ideas first of all as "games", as fun and concise gameplay loops, as the dynamic between different mechanics.
This channel is like watching someone learn 30 years worth of lessons that the software engineering industry learned the hard way. Except instead of picking up a textbook, you just learn them the hard way again. It’s awesome.
Wow this is so apt lol. Yeah you're exactly right. This is why I love this channel.
I feel like it mirrors my own learning experience but this guy is way smarter, and there's single videos covering things it took me years to figure out lol
It's an exercise in futility. This guy won't get anywhere.
Actually I do believe he is going places.. I've seen people read relevant books and not being able to make use of that knowledge. Learning something the hard way can really make it stick. Plus, I believe it is perfectly fine to set oneself a goal that might be unachievable in order to learn and exercise new skills.
And as this current video clearly shows, the meta-skills like "how do I work on a project in the first place " are part of that as well, increasing chances of finishing the next project.
And while the videos might look like there is no delivered "product" after all these efforts, I'd like to point out that we are discussing this in the comments of a video that has meaningful content, a characteristic style and editing 🙂
That's how I've been learning too.
@@MichaelSievers oh I agree! Just making a joke.
I can’t believe this is the first game design focused video you’ve made for this game
neither can I tbh
Ok, but, robots, plants, and cave, and it's really cool bro.
@@trashtrash2169 I'm sold.
I want to add on here that it's not just game design, but code design itself. If your code are just getters and setters and raw access to everything, you are asking for bugs and failures and roadblocks when you realised you can't do something without hacky workaround
A good design, even during your practical programming exams, will let you design and abstract away different parts of your code that have good type-scoping and "tell, don't ask" styles and object inheritance and even monad designs that can make life great (without feeling like you're cheating with some library)
Tell, don't ask and SOLID design paradigms are great when done right, though not fun
@@Yadobler you know he's a software engineer right?
I think recognizing where one has made missteps and trying to actively correct them is a huge part of "failing faster" people don't talk about, you can fail at sonic speeds but your failures won't mean anything unless you learn from them, so a fantastic post-mortem dissection like this is a way to grow even stronger from your failures, I wish you the best of luck for your next game!
scope resolution and not pay enough attention to the game loop is unfortunately very easy to mess up. i had that exact same problem when i started out making games with SDL2. glad you were able to recognize this!
also something called "paper prototyping" is actually a very powerful tool to test if the game is even going to be fun. no coding required just paper and a few pencils or art supplies depending on how crazy u wanna get with it.
i'm actually already paper prototyping for my next game! thanks for the suggestion.
@@jdh that's great to hear! don't worry btw everyone makes the same mistakes you did, it's just rare that people find out what went wrong.
@@jdh or you may use something like ms paint instead
> paper prototyping
may i introduce you to procrastination prototyping, where instead of making something, you don’t, but you still think about it for months. given enough time and knowledge of related concepts you’ll eventually figure at least some of the problems out
@@morgan0 damn i didn't know there was a name for this /j
I’m making my own game/engine, and I’m guilty of the same mistakes. I’ve been working on it for 7 years, and I’m nowhere close to done. But, I keep working on it, because I enjoy doing it. It’s a constant challenge that keeps me busy and entertained. Making a game is the greatest game I’ve ever played, even if I never finish.
But you are not making any RUclips videos about it, and making money out of it as this guy is 😊.
@@konjecture How does that change anything?
@@test-zg4hv doing hobbies for your own enjoyment versus doing hobbies for the algorithm tm are two very different things. You can't just upload footage of writing code. You need to do voiceovers, and explain your thought process. You have to edit videos in a way that holds the viewers attention. It isn't as simple as film and profit. There is a reason yt videos have high production quality. So I don't think it's a dumb idea to not subject yourself to the pressure that is RUclips and waste time without making money
@@test-zg4hvyou know you don’t HAVE to monetise your hobbies, right? its not all about the grind
@@Barely_Edited there's no reason not to, if I enjoy doing something I eventually get good at it so why wouldnt I want to make money off of it so I could spend even more time doing what I like?
just wanna mention that the work you *did* with graphics and such was incredibly impressive and no doubt valuable to your long-term knowledge as a game developer. the benefit of things like this are not entirely immediately clear. you learned a lot.
You say you're not good at art, but all your art is very aesthetically pleasing. Honestly man you're an inspiration, building engines from scratch and making good pixel art
Thank you so much, am a beginner developer and something that's rlly hurting is my game design skills, ive dropped so many projects because of this but honestly this video sums up everything i did wrong in my failed projects, now i hope my game design skills improve haha
I really love seeing someone recognize and reflect on their mistakes like this
There’s a reason I have two game projects that have a “permanent” place in the back of my mind. Slowly cooking until I can construct a satisying gameplay loop/idea to connect the rather scattered ideas I have for each. Writing ideas down and trying to connect them ocassionally. It’s really helpful that way!
In conclusion: you started to build a house but you didn't even have the blueprints
In any case, I like you because you do projects in a different and rustic way. I'm always glad to see you programming in C++ and using neovim even though I don't understand either one
neovim honestly isn't hard to setup, just use astronvim to setup neovim with syntax checking and stuff. once you're used to it, it is so so much better than most GUI ides
@@-aexc- yeah, but I didn't say nothing about set up, I know it is very easy to install the problem is the extreme learning curve
@@serbrawl7981 ah, it took about a week for me to get used to it after forcing myself to only use neovim
@@-aexc- great, I prefer mc paint
@@-aexc- click escape, :qa! for quit, :x for save and quit and press enter :)
The only people who don't makes mistakes are those who aren't trying. I count my mistakes as tokens of progress.
One thing I've learned over the years is to always always always design something thoroughly before you build it. That way you can have a good idea of whether it will actually work or not before you start to build it and potentially save you from hitting a dead end.
I've always gotten a "city of ember" vibe from this- I'd like to see some sort of continuation - this is the creative process, nothing wrong with it. No mistakes only happy accidents, and you never start from scratch - you start from experience
It was a book about an underground city- all they had were candles and streetlights so the city was colored amber, they'd been down there so long they forgot the surface existed- but when the generators thatve powered the city for hundreds of years start cutting out and a child finds clues that the cave isn't all there is, they and their friends search for an exit. They find a river that leads out and see sunlight
@@mikaelfoster9726 It's called "EMBER" not "AMBER" and yes I have heard of it!
@@rollinontheboard I thought it may be was! 😅 I have the memory of a goldfish- but nice to know I'm not alone lol ❤️
It very easy to say that but sometime starting from scratch is what's needed.
@@diddlenfiddle7311 yeah but unless you've just been conceived there's no such thing as starting from scratch-
Honestly, the idea of a robot in a cave planting stuff has room for interesting mechanics. Off the top of my head, I can think of one idea:
1 - the robot is like Wall-E, and is trying to terraform a cave through planting various plants with all kinds of functions, with the end goal of transforming the atmosphere inside this enclosed cave system into a breathable atmosphere. The atmosphere wouldn't need to be like earth's, either - you could have room for different levels by having different atmosphere goals, each of which would present a specific challenge.
For example, one plant takes in one type of gas and outputs another, but requires a specific terrain and a strong light. How do you achieve it? Other plants with more basic functions - like a plant that glows, but requires being planted on a specific rock or soil. Also, you could just ditch physics an go all in on magic. A plant that creates a gas barrier, but allows solids to pass through. A plant that breaks down rock into a specific soil, then dies. A plant that dissolves rock around it into a fluid. A plant that... you get my point.
Kind of similar to Botania (mod for Minecraft) x Factorio x Terra Nil.
But yeah, your game right now is an overdeveloped tech demo - just showcasing what your engine can do. Maybe just reuse the engine and try to make a game from scratch, but this time with a goal in mind?
I was thinking an ARPG with crafting elements, perhaps an alliance between plants, robots, and few surviving humans defending earth from an unknown threat. Lots of room for exposition through gameplay. I really like the vibe of the engine as well. I could definitely see a spin on ARPG combat with tower defense, realtime or turn based; resource management and crafting/harvesting. I also just love the theme of plants and robots.
Something like, idk, Icewind dale meets Zelda 1 meets Diablo for combat, and Starcraft meets plants vs zombies, on a background of Star dew Valley and Don't Starve? With automation like factorio... I think the mashup of style could be excellent, and would be a formidable challenge balance-wise. That'd be shooting for the moon for sure, with both real-time and turn based elements to implement (maybe just real-time that allows pause for management/stacking commands?) but having layers of gameplay like that seems both fun and ambitious. I'm just wishful.
The stuff above is what is missing within this game's design. It needs more brainstorming and more bullet point style notes of what you can do with the concept, where to take it and so on. Discarding the project now isn't quite necessary. Plenty of mechanics would work with the premise that already exists now.
that's what i was thinking, the engine is there and a base thematic is present, just needs mechanics and purpose. This can be saved imo, the creator just needs to decide on something instead of adding bells and whistles
I think you're right. A space colony game in which you play as a robot preparing a cave in a spare planet for humans/other intellingent aliens who will arrive in the cave later would potentially revolve around an enticing gameplay loop of cultivating an ecosystem of plants to produce a livable atmosphere as well as potentially fighting off hostile fauna to clear out and protect the colony cave. Heck, "Colony Cave", man that's a heck of a title right there! This gameplay loop would include those elements he mentioned as means to an end; crafting would come about as a way to make more weapons or resources to fight more monsters or maybe splice plants together to create new ones to achieve a desired atmosphere. Exploration would be an essential component of gameplay as you wouldn't be able to finish making the cave livable without exploring every nook and cranny for more monsters who could pose a threat to your colonists or looking for resources. Procedural Cave Generation would mean making the game far more replayable as each cave could be abstracted to be another cave on the planet somewhere. Heck, he would even have good motivation to go even further and develop features like multiplayer so that more people could colonize space caves together.
It would have been like a little like Deep Rock Galactic but as a long term colonist instead of a "Get in and get out" space miner.
I don't think this engine is a lost cause at all, as he still has the code and he has systems in place that he can quickly use to assemble a gameplay loop. However, I think he needs a good pitch and a good primary core gameplay loop in mind before he attempts this project again, and I think the "Robot colonist colonizes dangerous space game for humans by battling monsters and cultivating plants" approach to a primary core gameplay loop is punchy and effective because it would give him some smaller systems he could build immediately (such as basic combat with monsters) and give him an end goal to think about when redesigning his plant biology systems.
i'm glad this game isn't just abandoned, because the caves looked so cute!
I admire your courage for finding those mistakes and putting this up for all of us to learn from! I look forward to your future projects!
This video just solidifies the idea that every game developer should have gone through a little game design course and understand how to structure your idea and how to develop it so the risk of failure is lower. I've learned a lot in uni in this regard and I am ready to work like a pro... (sorta)
Lol, there's no way such a design course prevents you from failing at game design in general. Proper game design is like writing a music song. The first hundred or so attempts will fail, the next 20 to a 1000 probably will never become truly good, let alone original. Making a good videogame is difficult. Cloning other people their existing concepts is easy. Hence, why most games out there are kinda variations on existing stuff. The 'game design' courses in uni are usually about showcasing existing designs. It's rarely ever about _real_ game design.
Maybe it just needs a story, a goal, and an end game? What if the robot returns to post-apocalyptic earth in order to rehabilitate it? What if you start out by cleaning up trash, recycling materials to build useful tech, then use that tech to incubate better atmosphere and environmental conditions, which allows for seeds that were found in a seed-bank underground to begin to reproduce, cleaning out water supplies and decontaminating the land, slowly reintroducing and growing plant life to the point where it's producing enough oxygen so that the humans in space can return and begin recolonizing the planet in the end?
That was my idea for a game, and then I found your channel and realize you were already many steps ahead of me in building the same game, but without the guiding story and goals. I was really excited about this project!
Failing fast and often is such an important concept to learn with programming. A lot of my early projects failed because I wanted to make things as absolutely perfect as possible, and I got stuck in refinement hell. I should have been adding features, but instead I was writing and rewriting the same thing over and over, because I wanted to be sure I couldn't build things better than I already did. But that's the thing; there will always be a better way to handle something, and code is never perfect. It's important to recognize that, and build what's fun.
As long as you're looking at Jon Blow, it might be helpful to find video of what Braid looked like before he hired an artist (he's done at least one talk that shows this) and to look at the old streams he did at the start of his current Sokoban project (you can find them on his youtube channel under "Game Engine Programming"). If you're not making the game around the art, that's probably the level of polish you want until you have interesting gameplay.
Keep in mind also that Jon Blow did contracting work in the games industry for years before he shipped full titles by himself. I think a lot of the "Handmade" and adjacent communities want to go directly towards an ambitious project after they hear him speak, but I don't think you can skip the "many small projects, done competently" phase
It's an unfortunate conclusion, but i understand why it had to be done. Thank you for giving us this update video, and good luck on your future endeavors.
Local game engine maker discovers that game design is important, seeks to go study that now.
Sure, you got pretty far along with the game and the engine and could have done well to prototype, but you at least managed to catch yourself before the sunk cost fallacy overtook you. And you have a game engine on hand now! Maybe the game didn't work out as a game, but instead as a tech demo. Sieze the chance to fail fast and figure out a direction, before sticking to it and proceeding. I highly recommend the series "Developing" by GMTK, there could be some lessons from the process they went through that could give you some ideas.
All the best!
Dude, it is extremely impressive what you've managed to do by yourself. I'm just trying to start as a game developer and I imagine it would take hundreds of hours to build something like this. That is why it pains to see how much your game lacks direction in terms of game design.
it may sound presumptuous (and it is), but if you feel like it I can talk to you in discord over voice or chat to help bounce some gameplay ideas off me and shape some image of a gameplay you'd like to build
The problem is that ideas have a low chance of being fun, so it’s best to test a bunch of ideas quickly before deciding on one instead of just starting with an idea and blindly building it hoping it works out
Good insight and learning experience for you! Regardless of the project or not, it was a great way for you to warm up to everything you're doing! Looking forward to your next reveal. Awesome seeing your Patreon! Keep up the good work and be sure to take care of yourself too
At worst you still made a really cool tech demo!
As a software developer (mostly C) by trade, the programming and tech that goes into games has lots of really fun problems, but games themselves and game design are not especially interesting to me. It's funny how many programmers end up doing game related things as a personal project (myself included). My theory is just that its the most accessible and easy to distribute form of software out there, and there's always lots of game ideas floating around in everyone's heads.
I think there is always something pulling at me to be idealistic about the idea of making an entire game from scratch all by myself. But at the same time when I really dive into doing art or spending a lot of time doing game design I realise that it just isn't where my particular talents lie. Of course if you enjoy doing art and game design as a hobby its an entirely different story, but for me personally I'm always having more fun when my time is being used as efficiently as possible contributing to whatever I am best suited to tackle on a given project. I have learnt to never discount the value of getting together with a friend who does art or game design, so that everyone's talents and time are utilised optimally!
Keep up the great work!
Wish I had a programming friend lol. I m stuck with all these game idea's but fail at the programming stage... No matter how much I dumb down the difficulty of the programming aspect.
@@GodofGamesss it's definitely a steep learning curve but it's very liberating when you actually figure it out. You just keep trying till you get to a point where you have enough basic information to teach yourself the rest. You just have to be persistent and patient.
You have achieved a very unique and appealing art style, which is often half the battle for creating a successful game. Just because you don't have good gameplay mechanics yet doesn't mean the project failed, there is plenty of potential and you could also crowd source ideas and let people vote on the best ideas. There's clearly a game there waiting to be finished, you just need a clear path forward.
Thank you for your candor! I think that temptation to indulge in execution is an lifelong pitfall for us creative types who are also technical.
We love being able to make something come to life and there's always a cool new tool or technique to learn, but as you said the end result of that is often a disjointed project full of very cool parts that don't join into an entertaining whole, and premature optimizations that might not have been needed. I've definitely had my share of projects fail for that reason so you're definitely not alone!
I can relate, I'm currently working on a game of my own. I spent 2 Years starting projects and giving up on them before the one I'm working on now.
Ngl this is the first video that I watched from you but oh my your game looks so fancy! Really cool visuals!
Can relate a lot to 'programming is fun but doesn't inherently make a game - game design is scary and stressful and the thing you actually need to do'
For me it's the opposite. I love thinking of the design but dread actually programming the mechanics. But I have gotten a lot better with that in past year.
This is the feeling I get watching Duke Nukem 3D get played. It feels like the tech was spun up first and then everyone was like "oh crap, we actually need to make a game" and whipped out whatever they released. Same few enemies available the entire game, a bunch of lame puzzles that take no skill to do (just some trial/error/slowing you down), and menial maps. The only thing it had going for it really was the shear amount of stuff to get stuck in and the World Wide Web nowhere near popular or dynamic enough to handle a community around it.
What they accomplished engine/capability-wise was neat but that's it.
The lighting in your engine looks great dude! Good luck with your new project, from an ex-indie-dev :D
This was really really helpful. Not many people make videos like this and the honesty was golden. Thank you 👌I don't prototype enough
It has been so nice to see you building this game, waiting for the next project now :)
Btw you could make a Discord ^^
man i am so excited to find out what your next project is!!
Hey man, been watching for ages. last time I commented was during that CPU build stream (asking if it would ever be put in a case)
Either way, I really enjoy the channel; your calming voice, coding skills, and frankly amusing content always make your posts the highlight of my day.
I cant wait to see this new project!
P.S. RIP little robot.
Reminds me of Randy with arcana really bad.
Dude focused WAY too much on the technical, engine side of things to a similarly extreme degree, until he gave up on it entirely.
Weirdly enough, I have the exact opposite issue whenever I work on a project. I spend days before actually starting a project thinking about ideas for it, how they fit together, how they would work, etc. But the issue is, I can never actually figure out how to create systems or make things actually work. I can know exactly what kind of thing I want to make, but then fail to actually execute it in any meaningful way because I'm not skilled enough to actually apply my ideas. This is the exact opposite of the problem shown in this video, where most of the effort and skill is in systems (things like the game engine, entity system, graphics. etc.) rather than the actual game design that those systems are supposed to support. This is probably the reason why people create studios and work in teams instead of just one person doing everything. Unfortunately, I and many other people do not have the luxury of having a team to work on projects and have to deal with our own issues when it comes to things like this.
Now that I'm working on my first game it's so strange/interesting watching people's dev logs and seeing what their strengths and weaknesses are when I pretty much just took it all for granted before. I have all the art skills but just baby coding skills and I'm trying to avoid making a spaghetti mess even though it's probably inevitable. I would have taken the advise to start smaller, make prototypes, etc, but the game I'm working on is already something I originally wanted to make an animated series out of that I postponed for years til "the time was right", so I said f it, we're doing the big thing now, so we'll just see how this goes. 😅
The idea of a robot awakening after God knows how many years in a deep underground cave system is so fascinating to me.
The robot would immediately get to work to build an ecosystem capable of giving the humans in the surface oxigen and what not having to battle the local fauna, other rogue robots and battery issues.
The end goal would be to make it to the surface but every floor would require certain stack of resources and materials to mine your way up, coltivate certain plants and gather specific materials in a system reminiscent of Fallout Shelter with advance survival elements, also the more the robot would climb to the surface the more dangerous and resource heavy the journey would get. Also the more the robot would get closer to the surface the more about the lore the player would get to know. (I'm imagine a post apocalyptic scenario obviously).
Spoiler
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
In the end the robot would find humanity already went extinct centuries ago and the voicemails he was recieving throughout the adventure were a product of an AI, during the adventure tho the robot would have face many decisions (taming animals, reprogramming rogue AI instead of scavaging them for resources, choosing to prioritise certain plants to gift the humans with different benefits and so on) bringing him more closer to develop a "human soul" of somesort. Maybe after all a human did actually reach the surface, only not in flesh and bones.
It's okay to fail. At least you pulled the plug now and didn't work on it for several years. It's nice to see you talk honestly about it.
Already hyped for the next project. You are still one of the sole reasons I use RUclips and a freaking legend.
For prototyping, there's a reason why we use "dev art", which is literally the most basic colors and placeholder assets to only focus on making the gameplay fun, not on making VFX "cool to look at." Sure you can have an idea of the kind of aesthetic and story you want, but that's more for the pitch after you refine the mechanics so the prototype is FUN TO PLAY.
To summarize Thomas Brush's advice on how to even with video game creation: get a cool idea, iterate on it through a game design doc, get a time+money budget, then make the best prototype you can and pitch to investors so you can evolve it into the game you want to play courtesy of workers you hire to help you out.
On the plus side, you do have the curiosity needed to make a game engine to iterate upon these ideas quickly enough to create a working prototype of any genre of game you like in a month.
Cool! Thanks for sharing this valuable experience of yours ✨🙏... All the best for future projects 💯🙌🏼
Currently in the midst of prototyping a game right nowm. Glad i did it instead of my usual mentality of dreaming big. My intentions with what im building right now is itll probably get nuked but it will hopefully make for a good demo of what the game is supposed to be. Have made the mustake of making tons of art, with this its basic sprites and all my focus is being dumped on the gameplay. No matter how it looks, if it doesnt feel fun or like a game youd enjoy playing even as basic as it is, you need to make a change. The general mentality is graphics good = game good, but graphics should always compliment the gameplay
I'm going to be honest, this outcome was immediately obvious to me from your initial video. However, all the dev logs have been entertaining, so I'm glad you realized before you had even more time sunk in.
I love the idea of a lil' robot whose whole purpose was like cleaning up nature who falls into a little hole and finds a fascinating underground ecosystem! Then having to survive bad plants, catalogue unknown plants and solve puzzles using abilities from those plants while trying to find a way OUT of the cave. Maybe even generations of robots who tried and failed are able to be downloaded and each give small little tidbits of info or maybe a fun power up!
Gives me ideas like a light reactive flower that when light shines on it then it unfolds into a platform, when you water another flower (which you have to find a water source to obtain water first) it maybe grows like a vine upwards, weeds that try to maybe get in your tires to stop you, acidic plants that try to melt your iron, having to mine iron to repair your shells, having to craft spears to fight off enemies with and maybe refining a mysterious ore found under the ground! It would be a wonderful chance for ambient storytelling as well!
I am overflowing with so many cute and cool ideas! I hope you continue you it and feel free to steal any of my ideas from this but I really can't wait to see where you go.
I have not seen any videos from this channel, but omg that opening description sounds so much fun
I often find myself daydreaming about how game mechanics could be improved in existing and even AAA games... what comes to mind with the game you were trying to make here is to make it an isometric 3d roguelike or even metroidvania.
Hey that's the reason I love to watch you do your stuff.
I work in a company where I do Java 8, the slightest change to anything has to be double confirmed by management and that implies writing lengthy risk analysis and feature details and blablabla...
You wake up in the morning, take a shit half awake, and tell "hey what if I spent 6 months building a runtime broker for a super computer ? I'll figure out the need, the cost, the time needed along the way." then proceed to take your coffee, mumbling to yourself "i kinda love Pascal, maybe I should code in Pascal" and you're set for half a year.
I wish I had a buddy like you I know so little about engine coding but I have really solid game designs.
After those past few videos I was a bit worried, but if you go back to C I feel like you'll have really found yourself. I know people think such things can't be done in C, but they most certainly can and having someone prove it by writing a more modern game that way would be a great inspiration. Who knows, maybe I'll finally get off my duff and write my own game.
I know this video is 2 months old, but I do want to comment to say how this video shed some light on the game dev process. I'm a game developer major in uni, and seeing the lessons you walked away with reflect in my work is very interesting, especially with how my professors set up content and work. The first thing we've been asked to do, in my multiple classes which ask you to develop your own game, is to give an 'elevator pitch', the one sentence idea you talked about. Then we are asked to design those, creating a document to better serve our future plans, then we do a basic prototype. Talking about 3 hours of work total, prototype.
Seeing you extrapolate all of these same ideas from your project is very inspiring! I hope to get to a level where I can ask these questions to my own projects, and even begin to code my own engine, like you!
This has every bit of potential to be fleshed out. The grass spread, the planting and bringing color back is a wonderful element. Maybe a more limited world, with a specific goal in mind (i.e. make the gray ground 100% green, cover 50% in plants), and a result of the goal (i.e. a spaceship comes back to a planet once thought devoid now full of life, and has the tools to repair the robots friend/lover?/companion and ro-botanist can happily plant flowers with them). I feel the wave form collapse can still be implemented, making every new game you play different. Maybe an element where some things only appear in some random generations, and not in others (a way to do easter eggs). Of course, taking another idea and using it at your own is the opposite of your point in making an engine, or any project you have really. But, if you outsource for a few parts like that, you could easily flesh out this wonderful and beautiful game idea!
I like this channel because it chronicles my own larval phase of maturing into a coder. I wanted to do everything myself, to use ASM for everything, or even better, write a compiler in assembly for a language I would design myself. I made my own databases, my own assembler/disassembler, my own templating framework for web apps, my own server, my own unit testing framework, and yes, of course, my own game engine. Slowly but surely I discovered every rule of better software design by breaking it and finding out why the rule exists.
Honestly, I think I'm a better coder at the end of it than I would be if I just read the rules in a book without an exact understanding of the consequences of breaking them. My reaction to bad code is visceral. I can see problematic patterns as they emerge in new situations without needing it to mirror some scenario I read about in a book. As a result, I can successfully use frameworks that are developing and changing, I can jump into a large project and hit the ground running, and I can write code that can be customized and maintained without changing any code at all. I'm sure someone wants to tell me that you could do all that just by following rules they memorized, but I don't think that _I_ could have.
So don't get down on yourself when one project fails spectacularly. You learn your lesson, you let your mistakes scare you out of doing it the same way again. IMHO, it will make you a better coder in the end.
I mean nothing but positivity in this, but thank you for failing like this. (And for showing the rest of us). I’ve been theorycrafting a game for the past 6 months and anytime I try to start coding I always get hung up on engine stuff. Seeing just how many of your failures resolved around not prototyping has really inspired me! I think I have a core premise down pat, but thanks for showing that I really DO need to make a quick-and-dirty solution to be able to put the game FIRST.
I'm excited to see what you do next! Hope you hit 200k by the end of the year :)
Yeah, saw this coming from the start of the series. Tale as old as time. So preoccupied with whether you could, etc.
Oh well, looking forward to the next one! That blurry preview looks like there might possibly be some procedural terrain generation involved? If so, can’t wait to hear about it!
4:42 this is a trap ive seen a lot of solo game developers fall into of seeing games like skyrim and terreria and trying to make a game with many systems and tons of content but no central mechanic (not that skyrim or terreria dont have central mechanics but that people think that all that makes them fun it having tons of content). Glad to see you've caught yourself learnt from it and good luck with the next one
I find it interesting that you've decided to shelve the entire project. I could imagine building an awesome gameplay loop off what you already have. My first thought of a game I could love is something along the lines of:
You're a robot herbalist/alchemist. You're trapped 100 levels below the surface. You don't have any direct combat skills so you need to use your growing & alchemy skills to slowly work your way up to the surface.
The core gameplay loop would be something like:
1. grow + crossbreed herbs (I'd have some kind of small chance of random mutations (well defined though, so like this flower can have a variant that it occasionally mutates into, or if you crossbreed x with y you sometimes get z), and they all have different properties that affect your alchemical recipes (and obviously you need certain herbs for certain recipes)
2. process your herbs into alchemical concoctions, these enhance your robot in certain ways and allow it to actually progress in its mission towards the surface. There's lots of stuff you could do - gas style concoctions, self-improvement ones (e.g. move faster, maybe robot can briefly do melee damage), thrown potions, alchemical traps etc. maybe some meta-progression ones too if that's your jam. Lots of design space to explore here.
3. take your potions and use them to fight monsters, they get tougher and the levels get more complex as you get closer to the surface. Also you occasionally find plants that you can grow in your garden in the caves. You can add all the fun gameplay spice you want here too - e.g destructible terrain, interesting vision-using mechanics, more complex enemies, minibosses, large bosses etc. But I think you could do really well starting with something small.
4. And that's the main loop. Grow -> alchemize -> fight + explore + loot -> grow -> ...
It's also nice in that it's a gameplay loop that you can get up and running super easily (e.g. just have one or two alchemical concoctions initially, a couple of enemies with very simple AI's, and simple generated dungeons) and you can just keep adding variation to the gameplay loop as it inspires you.
So you could e.g. add more complex inventory management and inventory based mechanics if you have a cool idea for how they'd improve gameplay. Personally I'd try to keep most my effort laser focused on plant growing and breeding mechanics (I've always wanted to make a game with a simple DNA analogue for plants and have Mendelian crossover etc. Kind of like the Creatures series (I was always sad how lacking the plant stuff was in Creatures, there was some simple colour mutation in some plants in Docking Station and I had a lot of fun breeding plants for colour even with just that, but otherwise plants were very static, but the creatures dynamic), but for plant breeding, but that's not something I'd start with since it'd be a lot of work to get right.
And winning is reaching the surface to escape your sadrobotcave (that you fell into in a little cutscene at the start or your master locked you in, or your master died with you in, or... reveal a little of the 'origin' story ever 10 levels you explore in short flashbacks as a progression reward... or... pretty much whatever however you want to theme it since it doesn't really affect gameplay). I think thematically it'd fit the gameplay for the robot to feel very alone though, so I'd probably lean into that.
Anyway that's what I'd build from your starting point! Maybe it's influenced by my love of roguelikes and roguelites, but done right I'd definitely play the heck out of it.
From watching the video it sounds like he already tried building off of what he had, in a few different directions, but wasn't able to make any of them it into something he was happy with.
@@notnullnotvoid I guess it be that way sometimes eh
The robot with flowers in a cave could be your first draft if you put more thought into gameplay.
Imagine exploration where you have to grow plants to give you different effects, like healing, speed, haste and so on and as you explore the area around there are enemies you fight.
Plants have a tech tree by cross pollination you need to research and learn first hand what each combinations does. Each cross pollination unlocks the recipe and what it does (after using the plant once) in a booklet your robot has and can open at any time to see what they need for specific effects.
Imagine graves are around you have to find which have skeletons holding parts you need to make a portal and escape or something.
I don't know if it will make sense for anyone, but I've worked a lot on approach for creating plots(for any purpose) and game design.
And I've come to such 'blocks'.
1.Idea: what do you want to tell person.
Example: mindset if you don't wanna starve, you have to work, is not easy for execution, because world is much more complicated, and you can have traumas or the place where you live can have a crisis, or you will be able to change your situation only with time. so don't judge people quickly. if you don't want people to be rude with you(if it's possible), pay attention to their sore spots.
2.Goal: what you want to teach people to do.(it serves as goals for mechanics too)
Example: empathy, don't make quick judging, be careful with your words.
3.Favourite moments: moments that you will keep as sweet and proud memories after finishing playing/reading/etc. It's clear value of your finished work.
Example: when hero gave up his heritage for being with their love; when they saved lost dog, loved it very much, but decided to give it back to very lonely owner, who lost dog in his worst days, even though hero hates him, and could not telling him about finding it, after moving in nearby city.
For plot it's enough and other blocks are quite common, so I don't mention them.
And for game part.
1.Core mechanics: they are main instrument and reflection of ideas.
Example: if main idea is don't judge people that have no work, if you don't know the whole story, then core mechanics could be:
surviving: keeping stable sanity, and health parameters, by working at call center, bad phone connection will decrease your sanity
empathy: if you want to get an answer, you have to listen closely and choose wordings, or they will hang up, you can get money bonuses for good service(don't matter it's not real)
careful judging: if you'll listen, people will tell you their stories, and even can give you some advice for getting job, one of them even can get you an offer for some company with better conditions, it's long detailed surveys with repeating checking on clients
2.Tension-release-climax: rest and moment to wait for, to not get boring.
Example:
Rest = coming back home and talking to your hard-to-understand misterious neighbour, who could know something of the death, he's reflection of your level of convincing people;
Tension = your normal job;
Climax = checking days, when your phone calls estimated in real time(not real life, because calls are always recording; this checking probably don't exist) and they decide to keep you, kick you out, or raise your salary;
3.Game goal: long-term goal, that has clear instruction to player, and has a mystery(unknown = interesting). Goal appeals both to mind and to emotions.
Example:to pay for the operation for the sibling to wake up from coma, who evidenced your parent's death(example), the more time pass, more memory loss they will have about traumatic expirience
4.Game conditions: why this goal is believable.
Example: you need to raise money for sibling's operation, and this work is the only one that was available, and with flexible enough work schedule, and near the hospital, your credit limit is awful
5.Endings:criterias to get endscreen and what it is. It will shape direction of the game.
Example:
1)you got offer from the client and easily raised the rest of the money, you know the truth if parameters are *Insert here* etc.
2)you didn't get an offer because didn't listen enough and keep working hard, you know the truth
3)you were kicked out from work and could not find new one fast enough to know the truth, but you can kinda understand what happened by neighbour info
4)...
Something like this. Sorry, I got a little bit too excited. Examples are mostly for understanding of what I mean, not for perfect connections. It's hard tuning, I don't think it would be a big deal here. If anyone will get any use of this or new ideas, it will be great. Peace, people. Even if you will not read it.
I made a few games for Ludum Dare game jams, and found out not only is it hard to make a game from scratch and finish it in 2 days, but it is also even harder to make it fun.
I prettymuch knew this was going to happen with the first devlog, I have made the same mistake multiple times. you just have to do it, fail and learn to realize sometimes though
sometimes it helps to hear out others take on a given situation. drawing inspiration from their unique view and take it in with your own unique view. coming up with complex or symple systems together can be alot of fun and you might learn something about the process as a whole.
Game design is super cool. Like having a duel system and gameplay loops can be super fun.
Even theory crafting is enought to make a game fun if you gave it enough thought. Also maybe you can make a discord for fast player feedback?
Great job, love to see a constructive introspection in game dev. I am sure you have learned a lot from this experience. Good luck in your future endeavors ;).
You've accomplished in a short amount of time what Randy didn't even begin to ponder over in the last 3 years.
I would personally love to see this project open sourced at some point. I feel that there are some good ideas for gameplay that could be fully fleshed out and turn into a really cool game. If nothing else, it would stop some of the assets from becoming completely lost
your not wrong about going for design and graphics: the colours and the way lights hit, IS what gives the player a feeling of wonder.
I really like the look and feel of the robot game, hopefully you finish it someday
Something that could help you to make gameplay (or not, idk), is that when you are making a game initially make the things you like and think it's fun, then ask for other opinions and then adapt your ideas, I don't know how to make a game (because I have like 12 incomplete projects), but I think it's that way you could make a game. (I haven't watched the whole video yet, so, I don't know if you said something like that)
I realise you've already decided, but I still wanted to share an idea:
Combine your robot / underground / plant propagation concept with something like Factorio (extend current concept via automation), Opus Magnum / Space chem (create hardier / new plants), TIS-100 (program robot to do horticulture).
Regardless, having an end-game / goal in sight is, I think, a good start. I am confident you'll produce something outstanding.
I really hope you keep the art style.. The first of your videos on this game was amazing
I personally just chose a game type and made the game modular. I then worked on making at least one module for each key part of the game, if I had problems with one module I would switch to a different one instead, just so I had everything needed for the minimum viable product.
I plan on making alternative modules for each feature until I have at least 3 for each feature.
Then I plan on testing them out and having friends and family try to find a good combination of modules that work well.
I will then use that as the base of the game and work the other modules so they work as replacements for their respective modules
I will then add additional features that can be toggled, and make multiple modules for different implementations of those modules
I will play test and tweak any modules that seem to have issues melding with the rest, and try to make them all fit well no matter which modules are used.
My end goal was to make it so people can create their own modules, but I don't have the skill to set up such a system. hopefully I will just inspire someone else to rip off my idea and take it where I can't.
Bravo my guy. This is something that less talented/experienced/motivated programmers often end up doing _better_ because there's a limit to how much they can go overboard. While performance (next to minimalism) is one of the best starting points for actual code generation, correctness and effectiveness metrics come first, since that is what you are translating into input/output descriptions to implement with code in the first place. In this case, a subset of effectiveness is design, so without it, you end up solving made up problems. This is exactly the type of primer that extremely motivated and intelligent programmers need early on, since intelligence is not correlated with wisdom.
I could see something intriguing being built from the underground version of the game. Using puzzles that let you reshape the environment by planting certain flora and waiting for it to grow, uncovering some mysteries as you get more access to the cave system. You learn it's the post-apocalypse, and the robots were made to regrow life on the planet in case of an ecological collapse, and now the robots are wandering around in the underground bunkers left by humanity that unfortunately didn't make it.
really honest video, it help me understand your pov as I am new to programming games
This video is just perfect, I'm also *trying* to make a game engine. I've restarted like 2-3 times. It's been around 10 months and not going to lie I made almost all these mistakes lol. Perhaps my biggest mistake was I expected too much from myself as I'm no professional. And, I didn't begin with simple prototype also ended up in a disaster.
Now, I'm keeping it simple, doing tests, spending weeks on a single component (which is not ideal imo, I shouldn't spend this much on a single thing. If i change things in future, it'll be waste). Hopefully it'll work out
Good time to remember my 3 months ago comment in your video:
"That's why we don't usually reinvent the wheel"
Step 1) Don't use object oriented programming, use procedural programming.
Step 2) Don't learn quaternion physics for rotation, have a math library do it for you.
I was wondering when this video was gonna get made ^^;
With such an interest in engines and programming, I really hope/wish you get into a game that is heavily simulated! Like noita or dwarf fortress. (Start smaller than those please though lol)
Looking forward to seeing the new project!
I would love to see some kind of slasher in that setting and graphics, I think it has a pretty unique look
I think the robot plant idea is amazing. Imagine like dungeonkeeper. Planting mystical plants in carved out rooms to idunno. Conjure up elemental magic like mystical agriculture. From basic moss to life essence roses
I like the robot in the sky idea. Maybe it could be kind of like Minecraft Skyblock, where you start from nothing and have to build out your island?
I am super excited for your next project!
Welcome to the club! On the flipside, lessons learned the hard way seems to stick better though
I just started watching you yesterday when i got your first minecraft video recomanded. Now I'm really excited to see your new project. ☺
This is why I like doing game jams like Ludem Dare where you have 48 hours to create a game for a theme. Spending that time to create a POC will tell you whether something will work or won't.
I’m going to be honest, I noticed some of these problems right away, but it was just too interesting watching you design the engine. In the end it was entertaining to watch still.
Here is my idea. Evil robots with pesticide spray cans come at night (since it is in a cave some other cicle like day/night) to kill all ur plants. You got to defend them, you need to plant the plants in a progressive way (crafting) to unlock bosses that you defeat and the game becomes harder like Terraria everytime you defeat one of the said bosses. As background story, robots took over and are sent to exterminate all plants, a shortcut made your system bug out and you want to save the plants rather than destroy them
great lessons here, and a great video to boot - but in my opinion your biggest mistake is one you're making with this wrap up video: you're moving on to a new shiny thing instead of finishing what you started. All of these mistakes can be easily redeemed, and (I think) there's a lot to be said for committing to shipping _something_ - the work that it takes to get there will not be easy but will give you the satisfaction of doing the thing you set out to do, rather than the gnawing feeling of always-moving-on-to-the-next-thing. Either way, I wish you good luck in your work - and thanks again for this insightful video!
The lighting looked sweet in the engine you made. I could see it being used for stealth games
"The Sublime Object of Ideology" is well placed on your bookshelf. You are a man of taste I see, game design aside.
Minecraft didn't have a core idea, it was only supposed to be a simple voxel engine project. If you add all of your random bits it will still make a fun game even if you can't summarize the gameplay in a single sentence.
OH MY GOSH! Thank you a video! Your videos inspires me a lot man.
All graphics and no core gameplay makes it feel like a tech demo. Like "Look at this cool engine I made! Here I put a little robot in a cave to show the cool lighting effects."
I understand the approach. If I didn't watch multiple videos about game dev putting emphasis on prototyping, I would probably succumbed to my little writer/artist brain and made the whole graphics and lore of my first game before having anything fun to play. And to a certain extent I guess I do have that. I have plenty of ideas of stories and art directions that I would like to implement in a game. But, ultimately I now think of game ideas first of all as "games", as fun and concise gameplay loops, as the dynamic between different mechanics.
The flower saying "Howdy" scared me
Maybe you could make a video on your development environment. Looks quite interesting!
"I'm, at best, a game designer"
Shut. Up.
You're an inspiration. Thank you for vicariously being amazing and being an inspiration to be better.