• 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 object model using angelScriptA

2 posts in this topic

Hi all!


I've been using angelscript for around two to three moths now, and I'm having a blast.


I've been using it to develop a component based architecture for my game (rather than the usual inheritance thingie I usually do).


So, I have a component called as a "scriptComponent" that acts as a wrapper around components wriiten in angelScript. Plus, each object type has a "creator" script function that knows how to create the type that I need. 


I'm having this weird architecture where I call a script function to initialize an actor of a certain type, This function uses the scriptComponent class (which is in C++) to wrap other script objects as components for the required actor. It then initializes the actor and attaches said scriptComponents to the actor. It then returns the fully created actor back to the code.



So, for example, if I wish to create an actor named "Enemy", I'd call a script function called "enemyCreator" which goes like this:



//This function in turn, creates a generic actor object and attaches script classes by using the scriptComponent like so:

Actor@ enemyCreator(vector2 pos, float angle){
    Actor @actor = Actor(pos, angle);

 scriptComponent@ sprite = scriptComponent("Sprite", "gameEnvt");
 scriptComponent @body = scriptComponent("Body", "gameEnvt");

return actor;






 The scriptComponent searches for the required script class using the angelScript engine, and then instantiates it like this:




scriptComponent::scriptComponent(std::string scriptObjectName, std::string envtName){

scriptEngine *engine = scriptEngine::getInstance();
    AS_ScriptEnvt envt(engine->getEnvironment(envtName.c_str()));

    //the script object initializer is a simple struct that holds data need to initialize the script object
    AS_ScriptObjInitalizer *init = NULL;
    this->scriptObject = engine->createScriptObj(*init);

   //script "runs" are a wrapper around asScriptContext. 
    //it asks the script object for the initialization function. the script object sets up the script run
    //with the correct function as well as the correct script object.
    this->scriptObject->getRunByDecl("void Init(componentActor @actor, string envtName)", *run);

    //it then passes the arguments and executes the function

    //it then takes all the asIScriptFunction* it wants by asking for the functions. 
    //which are then called during the required time by using the script run
    this->onUpdateFunc = this->scriptObject->getFunctionByName("Update");
    this->onDrawFunc = this->scriptObject->getFunctionByName("Draw");
    this->onHandleMessageFunc = this->scriptObject->getFunctionByName("handleMessage");
    this->onBeginColisionFunc = this->scriptObject->getFunctionByName("handleBeginCollision");
    this->onEndCollisionFunc =     this->scriptObject->getFunctionByName("handleEndCollision");
    this->onPreSolveFunc = this->scriptObject->getFunctionByName("handlePreSolveCollision");
    this->onPostSolveFunc = this->scriptObject->getFunctionByName("handlePostSolveCollision");



Does anyone see any problems with this architecture? I'm  feeling that I'm missing something here that will have devastating consequences once I begin to create a lot of components. I've never been good at figuring out how this sort of this plays out when complexity increases


Thanks all!


PS- the names of the classes have been changed around a little, and the initialization function of the enemy and the constructor of the scriptComponent are watered down, so if you see some dangling refrence to other parts of the system that I missed to remove, or some syntax error, ignore it.



Share this post

Link to post
Share on other sites

I'd say you've come with a good way to use the scripting engine. I don't see any problems with your architecture.


This actually sounds very similar to what I show in the game sample that comes with the SDK. I'm not sure if you had a chance to look at that before you came up with your own implementation. Obviously the game sample is very simplified but the way the script and game engine are tied together is pretty much identical to the way you've done it. 






Share this post

Link to post
Share on other sites

Ah, nice to know that there's no problem :)


And yes, I did go through the examples but I found them to be.. confusing. So I just stumbled along :) 


Thanks Andreas! (for both the help and the awesome scripting language)


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