Godot game engine reaches 2.0

Post by gnarbarian » Tue, Feb 23, 2016, 4:02 PM UTC

cgarrigue wrote: post #34

eru wrote: post #17

Earlier quoted context omitted.

> Until Unity became popular, everybody was doing their own game engine for their own game. The very first Half-Life was already using one of the Quake engines. As was Hexen. The first Deus Ex was using the Unreal engine. That was all probably ten years before Unity.

I've been part of a community of hobbyist/indy gamedev since 2002. At that that time, there were very few engines usable by hobbyists due to price constraints: - Quake 3 Engine for FPS-like. Other FPS engine were moddable, but as the source code was not available it limited the possibilities. - RPG Maker for old school JRPG - Adventure Game Studio and GameMaker for Sierra/LucasArts adventure games. I could probably i…

Post by tcfunk » Tue, Feb 23, 2016, 4:08 PM UTC

Mithaldu wrote: post #2

Some meta discussion: "xyz reaches/releases version number 234234.324234" is entirely meaningless and the best way to ensure that nobody will care about your release announcement. Your project may internally have a very well defined and entirely logical policy as to how exactly to change version numbers based on internal project changes, but from the outside this is 100% untrustable and invisible, meaning your 2.0 re…

Post by hesdeadjim » Tue, Feb 23, 2016, 4:56 PM UTC

Cyph0n wrote: post #8

One thing I don't get with game engines: why do they feel the need to make a X-like scripting language, where X=Python in this case, and X=JavaScript in Unity's case? Why do they make people re-learn the specifics and slight differences of a language that has been around for more than a decade? On top of this, they are making their engines more difficult to maintain: bug fixes, new features, deprecation and backwards…

Post by stcredzero » Tue, Feb 23, 2016, 6:22 PM UTC

hrnnnnnn wrote: post #21

oolongCat wrote: post #14

Earlier quoted context omitted.

This should answer your question, http://docs.godotengine.org/en/latest/reference/gdscript.htm... As for my personal experience with GDScript, I used to experiment with Godot a while back, and honestly I never felt like GDScript was some sort of hindrance never felt it was in the way. It was really, really easy to pick up if you know another programming language already.

Totally agree. I made the same small game in Unity and Godot about a year ago to compare them. Learning and using Godot script was no big deal. The main difference was that I could use VS for Unity and it had a vim plugin, but if I wanted to edit text in-editor I was stuck with Godot's own one.

Post by AimHere » Tue, Feb 23, 2016, 7:14 PM UTC

eru wrote: post #17

scrollaway wrote: post #10

Earlier quoted context omitted.

There's a history of reinventing the wheel in game development just for the sake of doing so. Until Unity became popular, everybody was doing their own game engine for their own game. All those game engines have their own image formats, sound formats, archive packing format, etc. None of this is ever open source, of course... And before you think "in the name of performance", it's usually actually in the name of prem…

> Until Unity became popular, everybody was doing their own game engine for their own game. The very first Half-Life was already using one of the Quake engines. As was Hexen. The first Deus Ex was using the Unreal engine. That was all probably ten years before Unity.