• 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
shawk08033

Representing player classes in c++

8 posts in this topic

This isn't such an easy to answer question depending on a infinite number of variables it could literally be anything.

[CODE]
class PLAYER
{
public:
int IDNum; //this is the ID number
int LocX; //X location
int LocY; //Y location
string Name; //Name of Player
}
[/CODE] Edited by yewbie
0

Share this post


Link to post
Share on other sites
I just saw a similar thread with people debating how detailed an inheritance tree should be and when you should choose composition instead of inheritance; from that thread I'd say there's no 'best' way to represent your player.

Rather, write out a description of what your player character [b]is[/b] and what it [b]has[/b].

In the simplest form, a player is a creature that has an inventory and can be controlled by a person.
A monster is a creature that could have an inventory and is controlled by the computer.

The main difference between a player and a monster is that the player is controlled by a person. You could make a generic creature class with health, mana, stats like strength, and have it hold an 'inventory object' which is represented by an inventory class. Then you would attach the input from a person to the generic creature's movement methods and that becomes your player. Everything else that isn't hooked up to an input device (and is controlled by the computer instead) is your monster.

Hopefully that helps out some.
1

Share this post


Link to post
Share on other sites
I have a player class like in c++ class i need a player class like witch or warrior
[source lang="cpp"]#ifndef PLAYER_H
#define PLAYER_H

#include "gameobject.h"
#include "gameobject_component.h"
#include <QString>

class Player : public GameObject
{
public:
Player(QString name, int maxlevel, PlayerClass classtype);
Player(QString name, int level, int xp, int maxlevel, PlayerClass classtype);
void Update();
void Checklevel();
void Attack();
virtual ~Player();
bool isactive;
int Level;
int Maxlevel;
int Xp;
float Money;
QString Name;
float Mana;
float Maxmana;
float Health;
float Maxhealth;
float Speed;
float Strenght;
float Intelect;
float Hitrate;
GameObject backpack[30];
GameObject_Component Componets[100];
protected:
private:
};

#endif // PLAYER_H
[/source]
0

Share this post


Link to post
Share on other sites
Classes as in unit archtypes or something like that really depends on your game.

Figure out what the differences are:

Are the differences only graphical? - If so then you don't really need a seperate Class type.
Are the differences very major? - Break it out by what is different and seperate that out (again it really depends 100% on how you are using it)

You are asking very broad generic questions, you are going to get very broad generic answers =)

You could literally have your classtype be represented by an Enum that is simply a number representation of which class the player is.
1

Share this post


Link to post
Share on other sites
I would have to agree with using enums for the sake of simplicity.

On a side note, some of those public variables and functions look like (from the names) that they could be private (or protected) instead of public. Putting everything into public isn't necessarily bad, but it's not a good habit to get into as it can present some bugs down the rode.
0

Share this post


Link to post
Share on other sites
Do you know much about component based architecture? im new here myself, but in everything i have been taught and everything i have actually made, component based architecture was superior to an inheritance model. Unless you are making a few very simple game object classes, you will want to make components and then tack them on to your game object. And the player controller would be one of them.
0

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