• 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
  • entries
    37
  • comments
    46
  • views
    21810

Untitled

Sign in to follow this  
Followers 0
Drakkcon

189 views

So I haven't put anything in this journal for a long time, 'cause nothing exciting has been happening with me (unless you call playing Baldur's Gate for the billionth time exciting).

But now, I'm working (again) on a game engine. Woo.

But this time it's different for the following reasons:

  • I am not planning this at all, I will just refactor as necessary.

  • I am making content as I need it, not all at once (big sticking point).

  • I am using C# and XNA.

  • I am better at programming.



So I'm going to have fun doing this without too much forward planning, and seeing how playable it is.

Anyway, the first thing I started on were the gameplay classes, because they're more fun to make than graphical classes.

So the most important game play class is the entity (I started spelling game play as two words because Firefox's spell check is yelling at me) because it represents something that can be interacted with.

Every entity has two parts: its sprite, and its other stuff. I couldn't figure out a name for the other stuff so I called it "EntityReference".

Here's what I'm talking about:

using System;
using System.Collections.Generic;
using System.Text;
using System.IO;

using FromNothing.Utility;

namespace FromNothing.Gameplay
{
class EffectValue
{
string idName; //must be unique
string visibleName; //what the player sees
double Magnitude; //how strong it is
long Duration; //how long (in milliseconds) it will last
}

//this class specifies all the information about an entity that I might want to save.
//Any thing in the game world that can be interacted with is an entity.
class EntityReference
{
//This MUST be unique, it is used to identify an object
string idName;
//This does not have to be unique, it is what the player sees.
string visibleName;
//This refers to the type of object that this actor represents. EntityTypes might
//be "door", "tank", whatever
string entityType;
//Every actor has various attributes and statistics associated with it.
//This dictionary maps an attribute name with its value. Examples of attributes
//would be "strength", "dexterity", and "hitpoints", or in the case of a door,
//"thickness", and "picklock difficulty".
public SortedDictionary<string, Variable> attributes;
//Attributes are variables that are always present and relate directly to gameplay.
//They never go away. LocalVars, on the other hand, have distinct lifespans. These
//might be used to track plot points involving an actor.
public SortedDictionary<string, Variable> localVars;
//Effects are temporary ailments that are capable of effecting all entities, not
//just ones with specific storyline purposes. They are usually very temporary.
//Examples of effects include "poison", "lung shot", or "on fire".
public SortedDictionary<string, EffectValue> effects;
//Actions Performable are luachunks that spell out what happens when a character
//performs a certain action on this entity.
public SortedDictionary<string, string> actionsPerformable;

//if the variable does not exist, it is created.
public void SetAttribute(string name, Variable value);
public void SetLocalVar(string name, Variable value);
public void SetEffect(string name, EffectValue value);
public void SetActionPerformable(string name, string luaChunk);
//there is no kill attribute because attributes live until the character is removed
public void KillLocalVar(string name);
public void KillEffect(string name);
public void KillActionPerformable(string name);
/////////////////////////////////////////////////////////////////////////////////
public Variable GetAttributeValue(string name) { return state.attributes[name]; }
public Variable GetLocalVarValue(string name) { return state.localVars[name]; }
public EffectValue GetEffectValue(string name) { return state.effects[name]; }
/////////////////////////////////////////////////////////////////////////////////
public void Serialize(Serializer serializer);
/////////////////////////////////////////////////////////////////////////////////
}

class Entity
{
public EntityReference reference;
public Sprite sprite;

Entity()
{
reference = new EntityReference();
sprite = new Sprite();
}


}
}




Anyway, if you see anything that sucks, let me know. I'm going to be a game developer some day, and if you don't help me now, karma dictates that you will be maintaining my code some day.

0
Sign in to follow this  
Followers 0


3 Comments


I could be totally wrong about this, but won't all your SortedDictionaries be null? I usually initialize things right where they're declared unless they reference other objects in the class, I even initialize value types even though there's no real point, just to match the references.

Also there's no point in function prototypes in C#. Unlike C++, the order functions/variables are declared doesn't matter at all. Plus why not just merge EntityReference and Entity?
0

Share this comment


Link to comment
Good luck, writing an engine is rough. I tried it, and in some ways succeeded. Everyone will tell you it's not worth it, and that's true from most commercial standpoints, but where you're at now you could stand to gain more from the experience. Plus there are always cases where needing your own engine is critical. A friend of mine just finished an engine that's less than 400KB so he could make a 3D web game
0

Share this comment


Link to comment
Quote:
Original post by Scet
I could be totally wrong about this, but won't all your SortedDictionaries be null? I usually initialize things right where they're declared unless they reference other objects in the class, I even initialize value types even though there's no real point, just to match the references.

Also there's no point in function prototypes in C#. Unlike C++, the order functions/variables are declared doesn't matter at all. Plus why not just merge EntityReference and Entity?


You're right, I was just sort of prototyping though, not wanting to write out the function definitions. That's not to say I don't forget to initialize stuff all the time in C# =)

Quote:

Good luck, writing an engine is rough. I tried it, and in some ways succeeded. Everyone will tell you it's not worth it, and that's true from most commercial standpoints, but where you're at now you could stand to gain more from the experience. Plus there are always cases where needing your own engine is critical. A friend of mine just finished an engine that's less than 400KB so he could make a 3D web game


Thanks!
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