Talk:Game Engines

From GPWiki
Jump to: navigation, search

I'd like to add my project, the Ignifuga Game Engine to the list, it's still alpha but functional. Is that ok?

I don't see a problem with that. You might want to create a wiki page for the project and tell us more about it rather tan try to cram it all into a row on the table. Codehead 18:11, 1 March 2012 (UTC)

We are offering a network and persistence engine. It is called "APlay". You can take a look at it at [1]. It features a graphical editor and has a novel way of approaching the idea of abstracting the network communication and persistence. I was wondering if it qualifies for this list? --Hcsama 12:32, 12 October 2011 (UTC)

Interesting. Off the top of my head I'd say that as APlay doesn't provide the traditional features of a game engine (GFx, Sound, Physics) it probably doesn't belong in this list. People wouldn't be looking here if they were seeking something that provides the things you describe.

However, I see no reason why you shouldn't add it anyway if you like. You might even want to create a page on the Wiki for APlay and let people know what it has to offer.

Codehead 14:57, 12 October 2011 (UTC)

Ok, I put it in. I'll also create a small entry the network libraries section. But isn't actually a library in the common sense, much more like an engine. --Hcsama 11:06, 14 October 2011 (UTC)

Feel free to create a page at and tell us more!

Codehead 12:17, 14 October 2011 (UTC)

A few missing engines: SPRING RTS!!!!!!!

3d Gamemaker & Fps creator??,,, VASSAL, Lugaru (pronounced Loo-GAH-roo) is the predecessor to Overgrowth, HPL1, Gish OpenSource,,, cube?,

How about a column for the year the engine became available? Or a range of years for when the engine was popular? This would make it easier for readers to separate the old and dated from what is new and fashionable. --Jasmine85 16:50, 17 May 2010 (EDT)

What does "License: Commercial" mean? The GPL is technically a commercial license, but if something was under the GPL, it would get listed as "(Open Source)" instead. Telling me that the license is "commercial" doesn't tell me anything but that it might be under the GPL or it might be under a proprietary license or anything in between.

Good point. I believe the intent was to use "commercial" for engines that require payment. If you have a better suggestion, please let us know! --Ryan Clark 14:14, 26 July 2006 (EDT)

Many of the recent additions to this page seem to be "libraries" rather than "engines", at least, to me. What do others think? --Ryan Clark 18:38, 9 July 2006 (EDT), you might try using the preview button. We realise you like G3D, but you don't need 4 edits to get that across, one would be plenty. --pfeilspitze 14:05, 10 May 2006 (EDT)

I was wondering if there was a reason that the Quake engines weren't a part of this listing. All three (Quake, Quake II, and Quake III Arena) are available as both a GPL and commercial engine. Is there a reason that these engines weren't included? If not, I'll add them. --Kam 18:33, 29 November 2005 (EST) EDIT: Added Quake, QII, and QIII engines. --Kam 20:29, 29 November 2005 (EST)

I don't see any reason why they shouldn't be added. Feel free to go ahead. Thanks for contributing! --Ryan Clark 18:55, 29 November 2005 (EST)

Table Width

The features table seems to be getting a bit full. On my screen (1024x768), the text is getting cramped. Can the table be made wider than the screen? Codehead 05:31, 14 December 2005 (EST)

Nevermind, it already is. D'oh! Must have been the diff screen limiting the width. Codehead 05:34, 14 December 2005 (EST)

Maybe it would be a good idea and do like wikipedia does. Split the table into multiple tables. I.e. Maybe one table should have Language, scripting, platform, and pluses and minuses, and the other table have graphics, sound, ntwortking, and other features. A second thing would be to add None instead of leaving table cells blank, and a last thing would be to color code the thing for easier reading... just like wikipedia does.

Might have a decent improvement..

The engine table isn't exactly the state of art at the moment. I've been searching a bit and found out it's possible to use classes in the wiki table code. So, I propose this:

	border: 1px solid #000000;
	border-collapse: collapse;

table.enginetable td
	border: 1px solid #000000;

The above code needs to be put in one of the wiki's CSS files. It will only work on tables which bear the class "enginetable", for example:

{x| class="enginetable" cellspacing="0"

(remove the 'x' ofcourse). I've tested it using Proximitron, and looks like this:


Just a suggestion :). If I could do the CSS thing inside a Page, I'd try it, but AFAIK that's impossible

Source code available column

It would be nice if there was a row in the table with yes/no values that say whether source code is available or not (also for commercial products).


Isn't SDL considered a game engine? It has all the characteristics of an abstract game engine, supporting 2D graphics, OpenGL integration, input handling, thread handling, basic sound, great OpenGL integration, and a vast community of developers that made great libraries that extend SDL with things like advanced sound handling, GUI, etc, and it's platform-independent.

It's cited as support for other libraries but not even mentioned as one, I think it should.

I would consider it a library, not an engine. The line between engine and library is blurry, but if anything is a library, SDL is! Engines tend to be more specific and do a lot of things on your behalf. Libraries are more general and allow you to do a wider variety of things, but require more effort to work with. Since SDL is so obviously general, I wouldn't hesitate to call it a library instead of an engine. However, this is (obviously) just my opinion! --Ryan Clark 11:44, 19 October 2006 (EDT)

Filter list by column headings

It would be nice if you could select to see engines specific to the language you're interested in, or the license type you're interested in. Basically, some kind of filter on the list would be nice in terms of easily finding what you want. Is this possible? -IGTHORN

EDIT: Also, So far, the DaBooda link is broken and the DXgame link as well. DX game can be downloaded from other sites, witha google, haven't checked dabooda, but maybe has that. -- 11:40, 13 May 2007 (EDT)
I know this is an old comment but something like that would be good for the page. It is very daunting to be able to navigate the current page. Either that or the page needs splitting into multiple pages instead of one blob of a mess {Liam 13:14, 10 August 2009 (EDT)}

Blender Game Engine

Although the application itself is a general 3d application, it does feature a built-in game engine programmable with python, does it qualify?

I've added a section for the Blender Game Engine. Please edit as seen fit. Musicaljelly 15:14, 6 June 2010 (EDT)

Cleaning this mess up

While this page contains a lot of useful information, its structure really is a mess. Here's a quick checklist of stuff that isn't really cool:

  • There are no fixed keywords or keyword orders, so sorting pretty much becomes obsolete for most columns and a lot of Game Engine entries just invent their own vocabulary of describing themselves.
  • There is no visible standard for those entries except that they're all in a table.
  • Columns "Plus" and "Minus" are too subjective - they should be removed and replaced by a general "Remarks" column.
  • The "Other Features" column is often abused for entering vast descriptive texts about the respective engine. This reduces user overview dramatically.
  • Language is often used in an ambiguous way. Again, a set of fixed keywords should be used to make sorting useful.
  • Sorting doesn't work on icons, but removing them wouldn't be cool either - any ideas?

Here is what I've done so far:

  • Removed "Info" icons with mouseover information by merging them into existing icon mouseover texts and linking text.
  • Introduced a fixed set of keywords for the "License" column: "Commercial", "Free", "Open Source". That's it. All specific licensing information should be concealed within the keywords text link.
  • Split the "Graphics" column into "Graphics" and "Used Tech". The first one now only allows "2D", "3D" (being a superset of 2D) and "No", while "Used Tech" is there for referencing all kinds of libraries and technology - in this case OpenGL, DirectX, etc.

Still to do:

  • Clean up column "Language"
  • Replace "Plus" and "Minus" with a generic "Remarks", and keep all texts below a certain length
  • Cut a lot of text from "Other Features", this should only be a list of words and only include noteworthy features
  • Remove dead engines (Deadlinks, last updated 2009 and no noteworthy projects, etc.)

Good Work! I'm not sure about 'Used tech' as a column title. I agree that the column should be there, but maybe 'Technology', 'Technologies' or 'Tech Used' would be a better title? I'll have a think about it, I can't come up with a better on at the moment.

Codehead 16:54, 30 November 2013 (UTC)

Feel free to change it then :) It was just the first thing that came into my mind.

Fetze 17:12, 30 November 2013 (UTC)