I'm looking for a term that would describe the information that is not supposed to be known by players, not essential for their gaming experience.

Like a game object (or feature) that isn't actually present (or is not directly addressed by its name) in the game, but some other game objects are based on its functionality.

Or a kind of a backstage game object whose functionality is inherited by several other very important game objects, most of which have names, and are known to players, but that base object is supposed to stay a secret, because it doesn't actually mean or do much by itself, so it is of little to none importance to players.

  • 1
    Do you mean that this object is part of the game's backstory?
    – Jim
    Apr 10, 2013 at 5:05
  • I guess I should add that to the post. Apr 10, 2013 at 5:09

2 Answers 2


"Background" or "underlying" seems most likely to suit your purpose. On the other hand, you might want to use "hidden," or to take yet another tack, "implicit" or "implied." "Unexpressed," "unstated," and "tacit" might also be of some use.


This sounds like a programming question, so I'm answering as a programer with more technical information, hopefully I'm right about your intent.

Public vs Private: the most common terminology to distinguish between what you use personally, and what you are making available to others. Though generic enough that it's precise meaning varies by context and even language used.

Internal vs external: also commonly used phrases. external would be your users, in a game case the gamers. Thus internal would be all the things the developers know about, but don't intend to share to the rest of the world.

API: definition of commands that can be used by another. In essence your API will effectively be a list of all your public facing objects and methods; everything you want someone else to know about and use, while anything not in your API is implicitly assumed to be private.

calling something 'base' also implies the second half. A base object implies an object that is intended to be expanded on by other objects later. Technically a base object could exist in the game itself, but usually the presumption would be that the base object exists only to be extended; and thus it most likely will not be exposed to the regular game or players directly.

You can of course combine these terms. Saying a private base object would fully define what your saying. Languages may have specific terminology to them you can use as well. In java terms you would say "private abstract class" for instance.

You could also use abstract or interface to have similar meaning as 'base'. but those two terms are a little more technical and have slightly more explicit meanings.

on a more general term 'mechanics' is usually used by gamers to reference the nitty gritty of how a specific object, or more commonly class, ability, or item, functions. actually when someone references the 'mechanics' of an object they are usually referring to the exact math or rules behind an object. In essence their saying 'the stuff that is knowable or calculatable by avid players, but may not be obvious or made readily available to every day gamers'. So every gamer may be told this spell does damage, but when someone discusses the mechanics of a spell they may be discussing specifics of how the spells damage is calculated. Thus a discussion of mechanics can be somewhere between the two points of view you mentioned, not always known to all gamers, but not impossible to access by those who wish to know.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.