• 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

Simplest/Most complicated Rpg game engine design?

2 posts in this topic

Hit there i am fairly new in game development. Only made some small 2d space shooter. However me and my friends decided to make a simple 2d rpg style game engine/game written in Java.

First of all we decided it will be Tile based (without animation at least for now) and we plan on making it isometric in the future since it is just a matter of output.

We wanted it to be simple but powerful. So i got an idea and it goes something like this.

We make a game engine that doesn't have a lot of gameplay coded. It has understanding of what and item is it has an inventory but not the actual items.
It is divided in packages:

1: Central_command

2: Graphics

3: Input/output

4: Memory menagment


The idea is to have a lot of classes in central command. With in a way has access to everything witch usually means the memory. A map will simply be a txt file that has a roguelike based ascii map and a script for all object's on it if any. For example Wall is hardcoded but a potion of health is not.

The scripting system wont be complex. It only has to be able to store variables, use if, else, while statements and most importantly to communicate with central command.

This is the idea.

Have and object that represents the loaded script. place that object inside and Item class. class Item has a use/passive method.
A health potion will be an item with a corresponding image and script that will be invoked when the use() method is called.
The actual script will be something like this:
" player = Command.getCurrentPlayer(); player.setHealth(player.getHealth() + 20); "

I know that adding scripting ability to your engine is probably the hardest task. But it really simplifies other aspects of your engine. Because it is not needed to code all the stuff right in.

Is this the way to go or not?
How hard is it really? The interpreter sounds like its BIG but not complex. (remember this is a very SIMPLE scripting language)
Is this idea any good or should we stick with hardcoding everything?

PS I am sorry if this is too technical and should be put in game programming section. But it is a DESIGN question in a way.
Also here is a link of what we done so far (we just started so we used an existing open source tileset)
[attachment=8357:Engine Development.bmp]

Share this post

Link to post
Share on other sites
This should probably be in the programming forum. Game design is for gameplay stuff rather than code design.

However, it's important to have a good idea of your game design before you start programming it. Planning the features you need will allow you to validate if your architecture is correct. Also try to keep it simple. If you try to build it to allow everything, you will never get anything done. Since you're new to game development, I wouldn't try to make things the "correct" way, but rather the "working" way. Mistakes will be made so don't stress over it and just get it working.

Share this post

Link to post
Share on other sites
It's a very bad idea. I recommend doing it the opposite way, focus only on gameplay and ignore the engine and everything else as much as possible.
Also, sentences like "decided to make a simple 2d rpg" and "scripting system" have no right to appear in the same topic :) Simple implies you want to make it simple which means no things like scripting systems.

"or should we stick with hardcoding everything?" - yes, you definitely should stick to hardcoding everything, especially since it is your first RPG and you want it simple.

In the end the only thing that matters is the player's fun. Players won't see how clever it was coded, only if it was playable or not. Therefore, gameplay (and art assets) is the critical thing you should focus all your efforts on.

As a programmer I would also add that we, programmers, always tend to make clever engines and leave gameplay "for later" which makes beautifully coded but completely unplayable games :) As a rule of thumb, if you are a programmer and wonder if you should add engine thing next or something else next, the proper choice is the "something else" :)

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