Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Noob View Of Game Development Versus...
Started by roaminggamer Dec 01 2018 10:01 AM

2 replies to this topic
[TOPIC CONTROLS]
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

roaminggamer

[GLOBAL: userInfoPane.html]
roaminggamer
  • Corona Geek

  • 7,380 posts
  • Corona SDK

Update: I'm making this post for no particular reason, other than to share the humor.

 

Update 2: There isn't really a message to this post either, but if there were, I guess it would be, "While making games is fun and can be profitable, understand it is actually more work than you know (or can perhaps even guess at initially)."

 

 

I was reading this article and when I saw some of the images I had to laugh:

 

https://codeburst.io/the-2018-game-developer-roadmap-e07e45b3c423

 

While I don't agree with everything in the article, I wasn't laughing because I disagreed, but rather, because the images were so spot on.  I could also imagine a new person reading the article and promptly having a heart attack thinking "I gotta learn all that?"

 

When I see new folks come into the community (and others I have in the past been a member of) I can tell they see game development like this:

noobview.jpg

 

 

Whereas my personal journey has been more like this (and I'm still learning):

myreality.jpg

The thing is, this wasn't all at once.  It represents a lifetime of doing many other things and game development.  Still, the journey is a little longer than more new folks can guess and/or believe it will be.

 

 

Credit: I modified an image from the article to make this post.


Edited by roaminggamer, 01 December 2018 - 10:27 AM.

  • Appletreeman likes this

[TOPIC: post.html]
#2

XeduR @Spyric

[GLOBAL: userInfoPane.html]
XeduR @Spyric
  • Contributor

  • 368 posts
  • Corona SDK

As a kid, I started out by toying with in-game level editors to create my own maps, campaigns and even mini games. Then as those were no longer enough, I moved on to engines that didn't require programming like RPG Maker and Games Factory. Then, for several years, I moved on from the idea of game development to just consuming them. I hadn't really considered game development as a profession until my first year at a university.

Naturally, I did partially take the noob view into mobile game development, where my friend and I looked at a few games that were popular at the time and we said to ourselves: "We can do better than that." and that's where the ongoing learning process began. Really, it was a several years of trial and error after that point. :D

Our first commercial game was relatively successful in terms of downloads. Before we removed it from the app stores, it had reached ~210k downloads. We hadn't, however, given any thought to monetisation. The game only featured ads and we had even designed them to blend into the game so that they'd bother the players less, resulting in even worse click rates. :D As we kept updating the game with "cool new content", we also kinda bloated the game away from its original "lite and cool" to "what do all these buttons do?"

For our second game, we wanted to address the monetisation issue, so we included IAPs. However, this time the game was larger and buggier than before. It was built around having multiple levels and constant updates, which turned out to be too difficult and cumbersome to handle as we hadn't designed the game with expansions properly in mind. To give you guys a little perspective, we are talking about a minigolf game with +100 levels. Each level was sketched on paper and then redrawn in photoshop. The image was then traced in PhysicsEditor to create physics bodies. Finally, any additional obstacles were written in code for every level, including their transitions, etc. So, adding a single new level was a real undertaking and to make things worse, we had hard coded the level select scene to require 18 level courses, making 18 levels the minimum update count or we'd have to rewrite several scenes. So, we learned to plan better in the future. :D

For our third game, we wanted to take the artistic route and we created something that couldn't be played without a 3 part tutorial. We gave our beta testers the game, all who ignored the tutorial and were then confused by the gameplay. So, we learned that simplicity is great and trying to be too fancy just for the sake of it isn't good.

For our fourth game, we really didn't plan things to the end and we kept on having to rewrite some functions and entire systems on a weekly basis. We actually took this game to the PocketGamer expo in Helsinki several years back and landed a publisher there, however, we didn't read the fine print and our game was locked in an unfavourable contract with them for a long time.

With every past game, as well as every current game, I've had to learn new skills, from basic trigonometry, rudimentary image editing and programming in lua to programming server side as well as managing teams, businesses and projects, as well as economics and legal contracts. Each of our games has yielded some important lesson, some better and costlier than others, but that's life and lessons learned. :D



[TOPIC: post.html]
#3

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,000 posts
  • Corona SDK

But all you need is a TRS-80 and the source code for the original Star Trek game to get started.

 

:-)

 

Rob




[topic_controls]
[/topic_controls]