• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Vfor Vikram

Tools Developer - Examples

4 posts in this topic

Hi,

Can someone please explain the exact meaning of "Tools" for Game development, or more precisely "Tools Developer".

Is it like programming level editors and IDE?

Also, things like "mesh deformation / fracture tool" provided by game engines like UDK / Unity3d - Are they part of "tools" development or "engine" development?

I am a hobby game programmer and have been looking out to break into the industry. I have intermediate experience in c++ and I'm pretty good in C#. I don't want to go the QA route and hence thought applying as a tools developer would take me closer.

My Reasons for this approach -

All the small start-ups near my place are not really focused. For example, they do archi visualizations, click on baby mobile apps, etc. The more focused ones ask for experience and also "game programmer" salaries are like 50% - 70% less than other software domains. I thought I'll apply at some big studios as I have experience in C# and usually preferred for tools development

I'm not a great algorithm guy. I'm just average. But I'm good in OOPs and designing applications, etc. I may not be cut out for "engine" programming
0

Share this post


Link to post
Share on other sites
Yes, it includes those things.

Tools editors may be state machine editors, level editors, tools to visualize animations, build chain for packing assets, build chain for preparing producer-created tuning files or packing audio assets or whatever else.

As for feeling like you aren't cut out for engine work, don't worry about that! Most programming is of the gameplay engineering work. The programming grunt work of projects is creating things like spawners, rule-based event logic, interaction handlers, and so forth. Relatively few people work on the core engine itself.
0

Share this post


Link to post
Share on other sites
[quote name='frob' timestamp='1329835063' post='4915172']
As for feeling like you aren't cut out for engine work, don't worry about that! Most programming is of the gameplay engineering work. The programming grunt work of projects is creating things like spawners, rule-based event logic, interaction handlers, and so forth. Relatively few people work on the core engine itself.
[/quote]
Whoa, don’t be so hasty!
Yes most programming is of the gameplay nature, but if he is applying for a position that actually has “engine” or “tools” in the name, I expect they will have him working on the core engine itself, and he should worry (I feel from his initial post).

Language here is a tricky thing—many studios interchange a lot of words that really mean something else (especially here in Japan, where a “planner” is a game designer and a “designer” is an artist [img]http://public.gamedev.net//public/style_emoticons/default/huh.png[/img]).
For example, during my interview at my current company, the CEO said, “We have our own in-house engine. Well it’s not really an engine, it is a framework.”
Then you have people such as Hodgman who claim an engine and a framework are the same thing.
I asked, “How is it different from an engine?”, to which he replied, “There is no main loop.”
Then my coworker later said, “Huh? No main loop? Yes there is. I mean sort-of…”

From my experience, anything with “tools” in the name suggests also working on the core engine.
This is how it is in my company and it makes sense, because the tools are closely related to the core engine. They need to be made together, and with tight communication.
You don’t want to have a core-engine programmer trying to explain how the tool should handle modifying such-and-such super-advanced feature and have the average-level gameplay programmer making the tool scratching his head.

Generally they are the same team. In my company we even switch between working on the engine and working on tools, so they are not only the same team but the same people.


The bottom line is that this is very much open to interpretation and you should really ask the company itself.
If you feel that is not possible, but you see reason to consider you are skilled enough for the job, apply anyway. The worst that can happen is that you don’t pass the interview.
Just make sure to clarify what they expect of you during the interview, and if it is not what you expected, you can politely explain you misunderstood the position and ask if they have another position for which you might be qualified. You may still get a job yet.


L. Spiro
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0