• 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.


This topic is now archived and is closed to further replies.


[java] RTTI & Garbage collection Question

0 posts in this topic

Ok, here''s the situation. I''m working on a game where the end user will be able to create new game objects. Anyways I''m setting it up so that these new objects can spawn objects (e.g. a missile launcher spawns missile objects). Now each of these objects (missile and missile launcher) will reside in different files, and all object files will be loaded at load time. Due to the fact that I''m keeping objects seperate, and each object won''t know what objects actually reside in the system until load time (not compile time) I plan on using the Class class and the forName function. Class missileToSpawn = Class.forName("MyNewMissile"); Now because the MyNewMissile class was loaded into the RTTI at load time this should work fine. My question is -- Is the RTTI ever garbage collected? If so, does it follow that same rules as objects, as long as it is being referenced, it will exist. So by making missileToSpawn variable static, MyNewMissile will always reside in memory, therefore be quick to access? I can''t seem to find anything on the web, and my concern is speed. If the MyNewMissile class ever got garbage collected, the next time I tried to spawn one, there would be file access -- NOT GOOD. P.S. I''m keeping things seperate becuase I want other missile launcher classes be able to spawn this type of missile. But because things are in seperate files, I don''t want the MissileLauncher class to have direct access to MyNewMissile, I don''t know what would happen if someone downloaded the missile launcher class but not the MyNewMissile class. By doing it this way I can make the game engine simply invalidate the missile launcher class if a class by the name of "MyNewMissile" doesn''t exist in memory. I hope this message is clear enough. And thanks in advance if anyone out there can help. -Shaft

Share this post

Link to post
Share on other sites