AllCrimes
Member
I've been coding in GML for many years, but I find that I spend a lot of time coding game 'parts' and never fully take the leap of filling these systems with the creative 'blood' that makes up a game. I've coded huge top down streaming worlds, random terrain and structure generation, inventory systems, crafting systems, world maps, AI that takes cover and works together, stealth, you name it I've gotten a wild hair one day and coded it just to see if I could.
The problem is that none of these things in and of themselves constitutes a 'game'. They are just features with no life poured into them. I purposefully steer clear of the creative parts in lieu of making the systems that contain them. For instance I have an inventory system that can display item information from a database of items with captions, icons, unique behaviors etc, but the database itself contains about 10 items because I never wanted to delve too much into the 'creative' part of making new ones. Doing that would mean I had committed to an idea for a game.
I've always thought I wanted to make a game, but maybe I just wanted to make the systems that make the games do what they do, or maybe I haven't found the right project, or I'm totally right brained and incapable of thinking up a formula for fun. Sometimes I think I ought to join a team, work on someone elses idea, but I work QA (for an actual game company funny enough..) and go to school for programming and I'm not sure I could meet the time requirements.
Anyone experienced this? Have thoughts?
The problem is that none of these things in and of themselves constitutes a 'game'. They are just features with no life poured into them. I purposefully steer clear of the creative parts in lieu of making the systems that contain them. For instance I have an inventory system that can display item information from a database of items with captions, icons, unique behaviors etc, but the database itself contains about 10 items because I never wanted to delve too much into the 'creative' part of making new ones. Doing that would mean I had committed to an idea for a game.
I've always thought I wanted to make a game, but maybe I just wanted to make the systems that make the games do what they do, or maybe I haven't found the right project, or I'm totally right brained and incapable of thinking up a formula for fun. Sometimes I think I ought to join a team, work on someone elses idea, but I work QA (for an actual game company funny enough..) and go to school for programming and I'm not sure I could meet the time requirements.
Anyone experienced this? Have thoughts?