• 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.
  • entries
    625
  • comments
    1446
  • views
    1006545

Epoch and Entities

Sign in to follow this  
Followers 0
ApochPiQ

265 views

I've finally gotten around to clarifying and recording my thoughts on the entity system that underlies the rewritten Epoch toolchain in R10.

You can read the full writeup in the Epoch wiki article for the entity system.

0
Sign in to follow this  
Followers 0


5 Comments


The new layout seems a lot like (or at least the goals seem fairly similar to) Tangent.

Quote:

Moreover, this allows the programmer himself to define his own entities and syntactic extensions to the language.


Do you perhaps have a concrete example of how this looks/how it would work?
0

Share this comment


Link to comment
Not yet, unfortunately; I need to finish getting things like error recovery in the parser back up to speed before I can work on some of the initial extensions.

Conditionals and loops will be implemented this way, for instance; you'll end up doing something like this in the standard library:

void FlowControlLibrary::RegisterLibraryEntities(EntityInvocationTable& table, StringPoolManager& stringpool)

{
table.insert(std:make_pair(stringpool.Pool(L"if"), FlowControlLibrary::Conditional));
}

void FlowControlLibrary::RegisterLibraryEntities(EntitySignatureSet& signatureset, StringPoolManager& stringpool)
{
{
EntitySignature signature;
signature.AddParameter(L"condition", VM::EpochType_Boolean);
signatureset.insert(std::make_pair(stringpool.Pool(L"if"), signature));
}
}

void FlowControlLibrary::Conditional(StringHandle entityname, VM::ExecutionContext& context)
{
Boolean value = context.State.Stack.PopValue<Boolean>();
if(value)
context.InvokeEntityCode(blah);
}


Well, I obviously haven't thought it through entirely yet, as that last blah can attest [grin] However, that's the basic idea. That'll set up the bulk of the internals for handling the if entity, which will be invoked just like any other (non-function) entity:

if(foo == bar)

{
debugwritestring("Equality!")
}


There's a couple little details to get sorted out, such as how to distinguish between entities that have inline attached code versus entities which do not (functions, really), but that'll be pretty easy once I get the rest of the prerequisite junk cleared up.
0

Share this comment


Link to comment
Okay. That (at least at first glance) seems to be... not something for the common end user. Just curious about the approach. Always good to read about other work in the area.
0

Share this comment


Link to comment
Yeah, it's definitely more of a systems programmer/library programmer type feature, rather than something that your day-to-day apps guys will need to mess with.

I made that decision for a couple of reasons. First, while I like the idea of highly mutable syntax in theory, it serves as a communication impedance in practicality. I'd like people to be able to say they "know Epoch" in the same way that one "knows C++ and the standard library" for instance. If the syntax is too mushy then this gives way to far too much mucking about trying to determine what code means.

This ties directly into the second reason I wanted to make it a little less accessible: abuse. Operator overloading in C++ is a great example of a controversial feature that is occasionally invaluable and often open to hideous abuses. By raising the barrier to entry just slightly, I can avoid a lot of that problem: the kinds of people willing to dig into extending the standard Epoch library aren't likely to screw up something as simple as syntax extensions. By contrast, people who are likely to do something evil (by accident at least) aren't going to have immediate access to the syntax mutation facilities. This makes it a bit harder to blow one's feet off.
0

Share this comment


Link to comment
I suppose. Though also with C++, template metaprogramming has a high barrier to entry, but that mostly just keeps people from learning/using it (not necessarily a bad thing in this case, but...).

Still, that's one of the things I do like about what I've settled on for Tangent's syntax manipulation: You get most of the benefits without being able to modify the syntax. The actual parsing rules are fixed. The actual rules for how tokens are processed into coherent expressions are fixed. Allowing the programmer to intuitively define/overload the types of almost every token provides a lot of the same 'fix the syntax to better match the problem domain' benefits without a lot of the gory details. And aiming the language towards a more literate path should (hopefully) make it so that programmers don't need to look too deep to grok what's going on in custom libraries/extensions.
0

Share this comment


Link to comment

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