My Message close
GAME JOBS
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
May 23, 2013
 
Virdyne Technologies
Software Engineer, iOS/Mobile
 
Virdyne Technologies
Project Manager
 
Stomp Games
Web Game Programmer
 
Hasbro
Producer - Boys Integrated Play
 
LeapFrog
Associate Producer
 
Off Base Productions
Senior Front End Software Engineer
spacer
Blogs

  New School Blues Dev. Diary #9: UGAGS engine
by Mike Doucet on 01/28/13 05:26:00 pm
Post A Comment Share on Twitter Share on Facebook RSS
 
 
The following blog was, unless otherwise noted, independently written by a member of Gamasutra's game development community. The thoughts and opinions expressed here are not necessarily those of Gamasutra or its parent company.

Want to write your own blog post on Gamasutra? It's easy! Click here to get started. Your post could be featured on Gamasutra's home page, right alongside our award-winning articles and news stories.
 

Developer Diary #9: UGAGS

We’ve chatted quite a bit about the design and look of New School Blues.  But what about the code needed to make it run?  Every developed game needs an engine, a structure that the game gets its logic from .  Think of it like a car, even with tires and a slick body it won’t run without something telling it what to do. Let’s let YoyoBolo programmer Amir get into more detail:

image

Game engine made by yours truly…

“New School Blues is being developed using an engine called UGAGS.  What is UGAGS you ask?  Well it stands for Untold Graphic Adventure Game System, and it does pretty much as advertised; especially for a tool that’s still in it’s early stages of development.

It makes laying out navigation meshes and waypoints in the room a relative breeze, which having experience doing this in code, can be a pain if you’re doing so without any visual guidance; which UGAGS offers.

image

Can you imagine how long it would take to place all these clickable objects purely in code without a visual tool like UGAGS?

My current tasks are trying to implement the game logic into each of the rooms.  That basically means I’m trying to make the game play like a game by adding events and interactive points where they are needed.  It’s a fun process but can get a bit overwhelming when you’re trying to juggle all the variables up in your head; I usually have scattered sheets around with garbled lists of variables that I may need.  UGAGS in this area can get a little tricky but given it’s stage in development I don’t really hold anything against the little guy.”

More on UGAGS and programming on NSB to follow.  For now, thanks for reading!

 
 
Comments


none
 
Comment:
 




 
UBM Tech