Difference between revisions of "Fangame Engine"

From Mario Fan Games Galaxy Wiki
(updated the page in general and removed the clickteam movement engines section since it's not very related and it already has its own page)
(Made the article more neutral.)
 
Line 1: Line 1:
A '''fangame engine''' is the base code that can be used to create other fangames. The term often gets confused with "Game Engine", which refers to the program the Fangame Engines were made in, such as [[Game Maker]] and [[Unity]]. Fangame Engines can be seen in a fairly isolated form as [[howtos]].
+
A '''Fangame Engine''' is the base code that can be used to create other fangames. The term often gets confused with "Game Engine", which refers to the program the Fangame Engines were made in, such as [[Game Maker]] and [[Unity]]. Fangame Engines can be seen in a fairly isolated form as [[howtos]].
  
 
Mario Engines usually expected to contain features normally seen in the official games, such as Mario like physics, [[collision checking]], Question Mark Blocks, and enemies. It is common to see other features implemented to help make the game feel more unique.
 
Mario Engines usually expected to contain features normally seen in the official games, such as Mario like physics, [[collision checking]], Question Mark Blocks, and enemies. It is common to see other features implemented to help make the game feel more unique.
  
The abundance of full-featured open-source engines is a controversial issue; while they allow inexperienced or non-programmers to easily create their own games, in many cases the engines are barely modified, if at all. Bugs, annoyances, and a general "cookie-cutter" feel tend to persist with games produced with these engines. The [[Hello Mario Engine]] in particular is often cited as being overused and generally unchanged.
+
Open-source engines allow inexperienced or non-programmers to easily create their own games. In many cases, the engines are barely modified, if at all. Bugs, annoyances, and a general "cookie-cutter" feel sometimes persist with games produced with these engines. These engines are often cited as being overused and generally unchanged.
  
 
== Various [[Mario]] Engines ==
 
== Various [[Mario]] Engines ==
[[File:HelloMarioEngineScreenshot.png|thumb|384px|right|[[Hello Mario Engine]] is one of the most commonly used Mario Engines.]]
+
[[File:HelloMarioEngineScreenshot.png|thumb|384px|right|[[Hello Mario Engine]] is an example of a '''Fangame Engine'''.]]
 
===[[Game Maker: Studio]]===
 
===[[Game Maker: Studio]]===
 
*[[Hello]]'s "[[Hello Mario Engine]]"
 
*[[Hello]]'s "[[Hello Mario Engine]]"
Line 14: Line 14:
  
 
===Legacy [[Game Maker]]===
 
===Legacy [[Game Maker]]===
*[[Hello]]'s "[[Hello Engine 5]]"
+
*[[Hello]]'s "[[Hello Mario Engine|Hello Mario Engine Legacy]]"
 
*[[Hello]]'s "[[Open Source SMB1 Engine]]"
 
*[[Hello]]'s "[[Open Source SMB1 Engine]]"
 
*[[Gatete]]'s "[[Gatete Mario Engine 8]]"
 
*[[Gatete]]'s "[[Gatete Mario Engine 8]]"

Latest revision as of 19:02, 29 June 2017

A Fangame Engine is the base code that can be used to create other fangames. The term often gets confused with "Game Engine", which refers to the program the Fangame Engines were made in, such as Game Maker and Unity. Fangame Engines can be seen in a fairly isolated form as howtos.

Mario Engines usually expected to contain features normally seen in the official games, such as Mario like physics, collision checking, Question Mark Blocks, and enemies. It is common to see other features implemented to help make the game feel more unique.

Open-source engines allow inexperienced or non-programmers to easily create their own games. In many cases, the engines are barely modified, if at all. Bugs, annoyances, and a general "cookie-cutter" feel sometimes persist with games produced with these engines. These engines are often cited as being overused and generally unchanged.

Various Mario Engines

Hello Mario Engine is an example of a Fangame Engine.

Game Maker: Studio

Legacy Game Maker

Clickteam