Sign in to follow this  
Nicholas Kong

What exactly is considered a system?

Recommended Posts

Nicholas Kong    1535

So I am building a Java class that manages the health of a ship I am building for my arcade shooter game. So can I call the class a health system then?

 

Can I say a system is just a Java class that is made up of components(in my case is just a heartJPanel that is added on to the gamePanel that holds the canvas and an array of JLabel added on to the heartJPanel that displays the hearts that represents the health condition of the ship).

 

I never really understood what exactly make something a system(like a battle system, lighting system, physics system, combo system) in the software development side of game programming. 

 

I worked on my arcade shooter game for 3 months so I just want to make sure I understand what a system is.

Edited by warnexus

Share this post


Link to post
Share on other sites
ultramailman    1720

I think the meaning of "system" depends on the context. For example, it can mean a whole computer, an operating system, etc..

 

In terms of gameplay, a system can refer to a feature of the game. For example, a craft system, a trade system, etc..

 

In terms of game programming though, I think it can mean a mediator, a controller, etc... Something that manages parts of a game, something higher level than the smaller parts that make up a game.

 

You can call your "health system" a system, but I think it's a system in the sense of gameplay.

Edited by ultramailman

Share this post


Link to post
Share on other sites
SaurabhTorne    499

The immediate focus of interest which involves some input and output equal to input, overall is a system. Remaining all is surroundings.

In thermodynamics the system which is governed by a boundary, you will find resemblance the above statement.

 

So apply it to gaming which is a system of effects related to some initial condition. for example weapon fire, flash light, pickups, barriers, all these can be considered as independent systems for easier programming.

so in case of the systems of weapon that fires.

Keyboard input is the input, and output is bullet and flash, also another output is the sound of weapon fired. etc..

Luckily, in games the relation or sequence of these events of the system can be manipulated instead of governed by laws of physics as in case of real life systems.

So you can create a bullet that is metal but weapon fires with birds chirping ;)

 

if there is some code that manages these systems , it itself is also a system that consists sub-systems. hence to differentiate these kind of classes are called as manager class.

Basically your free to call it anything, for a farming game , it will be either farm manager or farm system, or bla bla :)

 

Saurabh

Share this post


Link to post
Share on other sites
Capoeirista    3266

I never really understood what exactly make something a system(like a battle system, lighting system, physics system, combo system)

As far as game development goes (from a code perspective) I think of a system as something that is updated on a per-frame basis and manages dynamic content - physics, sound, lighting. On the flip side, managers take care of static content like textures. 


Of course that's just my interpretation, based on the last couple of engines I've worked with and the engine I'm currently building.

Edited by Orangeatang

Share this post


Link to post
Share on other sites
Nercury    812

To iterate previous responses, there may be systems on different levels:

 

Game

 

You may have a crafting system. You can craft a tool using a defined amount of wood and steel. Players can learn this system and expect it to work the same way.

No such system would mean no defined way tools appear. They may be raining from the sky one second, the other second they will degrade into worms.

 

Game engine

 

For example, you may have a material system. You can have a documentation which describes how to load textures, apply materials - how to generally use this system.

No such system would mean that there is no defined way to do material management, and every use case may be completely different.

 

Project management

 

You can have a bug-tracking system which sets a way in which bugs are reported, checked and resolved.

No such system would mean fixing bugs as they come. Joe and Jones may be fixing the same bug at the same time, no one cares.

Edited by Nercury

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