• 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

Component-Entity or Entity Module

0 posts in this topic

I'm working on building utilities (explicitly not an engine) for a game project I'm working on. One of those utilities is getting C++ and scripting working together so that the scripting language can be used to set properties of C++ classes, and also to react to changes in those properties that come from the game and other general scripting things.

But there are constraints to the design. The scripting component is for logic, not functionality and for custom behaviour modification by cleverly dropping some reactions to events in and not building the base functionality. And I know exactly how the scripting will fit into an entity and entity-manager module; but I'm still grasping at straws with how the scripting will work with components. My thoughts on this are so far:

Entity & Script Module:
Entity has properties & functions
These properties & functions are exported to the script.
This allows me to do everything I need to do in terms of controlling game logic, scripting levels, tweaking properties & iterating on custom mechanics in real time.

I think this is a safe model, because I know that the script will be able to do it's job with minimal programming support. I know that sounds like a pipe dream but it's all to do with what the scope of the script is, which isn't much, it can handle it.

However I can only guarantee that this script can do it's job for this particular project, which is simple in scope, but I can't guarantee that this entire module will fit the requirements of future projects and thus become an inflexible trashware that was short sighted in it's purpose and usage.

Entity, Component & Script Module:
Entity has components.
Entity has script.
The components are set for an entity by the script. So the components an entity uses are data defined. These would be components like weapons, movement, health, AI, physics.
The components communicate amongst themselves but they essentially replace the properties and functions that were exported to the script as before. The components now reporting to and receiving their tips from the script.

I can see the benefit in this, It does make the design constraints of code a little tighter, so better code. I can see that it allows me to do basically exactly the same thing as number 1. How ever by my estimation supporting the mechanics that can be customised will be more c++ code in the game. On the flip side of code conservation, I'm very sure that a reflection parser and builder for an ecs module, that's what I'm calling it now, will be much easier to write and support because of the constraints of components operating with the scripting.

The thing that I grasp, is that a lot of experienced programmers despise the entity model because they've wished for something in the past. I'm asking for the advice, which of these two options represents the least [b]risk[/b] to the project, measured against long term benefit.

PS: I'm still on the fence with this, but I am leaning towards #2 because of the future benefit, and because I can call it an E.C.S. module, Full Metal Panic! fan? Anyone?

UPDATE: I'm researching as much of the component object model as possible so that I can learn enough about it to make a decision between it and the entity model. If anybody has some source code detailing the use of a component model, and I mean some component classes, entity classes, and data representation that links them together. I'd really love to see it. Edited by Kyall

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