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

How to edit "Inheritance" in Object Oriented Programming?

6 posts in this topic

Hello World,

 

I have a question about extending child classes from parent classes in Object Oriented Programming. To be specific I am talking about UnrealScript, but I am pretty sure this concept is a kin to all OOP languages.

 

Lets say I am making a FPS game. I have 4 different weapon types, Pistols, Shotguns, Rifles and Rocket Launchers. Obviously all of these weapons are going to have functionality that is the same like ammo, accuracy, damage and so on. So you would make a parent class with all of the common functionality  and extend from that class when programming your weapons so in the child class you didn't have to rewrite all of that code.

 

However, what if you were writing the code for the rocket launcher for example, and you wanted most of the functionality that the weapons parent class offers, but some of it you didn't want? How would you avoid extending some of the functionality that the parent class has while still keeping most of it?

 

 

Here is some example code roughly written:

 

//Parent Class

 

class BasicWeaponFunctionality extends UTWeapon;

         placeable;

 

 

/** Initial ammo count if in weapon locker */
var int LockerAmmoCount;
 
/** Max ammo count */
var int MaxAmmoCount;
 
/** Holds the amount of ammo used for a given shot */
var array<int> ShotCost;

 

 

//Child Class

 

class RocketLauncher extends BasicWeaponFunctionality;

         placeable;

 

 

//How would I avoid extending the variable LockerAmmoCount from BasicWeaponFunctionality Class?

 

 

I hope I make sense, let me know if I don't so I can clarify just in case.

0

Share this post


Link to post
Share on other sites
One option is to use two base classes with one inheriting from the other. You'd have your rocket launcher class inherit from the first base class that doesn't have your locker information, and have the other three weapons inherit from the second base class that adds the locker information.
2

Share this post


Link to post
Share on other sites

Oh ok, well that seems easier than I thought it would be. I can't believe I didn't think of that. Hey thanks a lot that should work just fine!

0

Share this post


Link to post
Share on other sites

You could take a composition approach. Create classes that handle ammo storage, damage/accuracy calculations and whatever else you need for weapons. You then create individual weapon classes that have instances of those basic weapon component classes. This way you can pick and choose which weapon functionality you want for each weapon. It also allows you to easily construct specialisations of any piece of weapon functionality to use in specific weapon classes without having to worry about the effect it has on other weapon classes. 

0

Share this post


Link to post
Share on other sites
I don't know UnrealScript or your design, but here's how it looks to me:

All the variables you mention are not part of the game state, but are fixed properties of the weapon type. It would be better to separate that data and store it once per weapon type.

As it's just data there's no need for inheritance. If a particular weapon doesn't use one of the fields, that's fine.

For the code, the usual way to change the behaviour of a base class is to make the function virtual and override it.
0

Share this post


Link to post
Share on other sites

Ok, well the way it is setup is so I can minimize the amount of coding needed to be done. I am actually using Epic Games Unreal Tournament code as a base for my own project. It saves me a lot of work in the long run since all of the default values for weapons are already set, this way the changes I make will be fast and minimal. I don't really want to go through the trouble of rewriting any of the default code. Thanks anyways.

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