|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Dialogic||2,547||11 hours ago||138||mit||GDScript|
|💬 Create dialogs, characters and scenes to display conversations in your Godot games.|
|Termloop||1,220||1||2 years ago||April 22, 2023||5||other||Go|
|Terminal-based game engine for Go, built on top of Termbox|
|Pythonstdiogames||596||2 years ago||12||December 30, 2020||5||mit||Python|
|A collection of text-based games written in Python 3 that only use "standard i/o".|
|Godot 3d Mannequin||513||2 years ago||10||other||C#|
|An Open Source 3d character and character controller for the Godot game engine|
|Openmu||506||19 days ago||17||mit||C#|
|This project aims to create an easy to use, extendable and customizable server for a MMORPG called "MU Online".|
|Legend Wings||457||6 years ago||Swift|
|iOS Swift Game - Push SpriteKit to the limit|
|Pokemon Font||439||3 years ago||January 18, 2017||ofl-1.1||CSS|
|GAME BOY font from Pokémon R/G/B/Y/G/S/C, Unicode extended.|
|Rpg Core||437||4 months ago||1||other||C#|
|UNITY engine RPG framework|
|Ipokemon||428||7 years ago||9||mit||Objective-C|
|PokéMon like game on iOS with Location Based Service.|
|Dnd Tldr||410||3 years ago||9||cc-by-sa-4.0|
|Dungeons and Dragons - Too Long; Didn't Read|
Open 3D Mannequin is an Open Source 3d character and character controller for the Godot game engine
⚠ The project only supports Godot version 3.2 and above.
Table of Contents
This is a third person character controller designed to work both with the keyboard and a gamepad. It features a camera that can auto-rotate or that can be controlled with a joystick.
The 3D Third Person Character Controller is made of two scenes:
CameraRig.tscn- A 3D camera rig with a state machine for aiming
KinematicBodywith a state machine for player movement. Contains an instance of
CameraRig. It also includes the animated 3D mannequin.
To use the default character, instance
Player in your game. See
Game.tscn for an example. In this demo, the obstacles are mesh instances with static body collisions making up a cube world.
The game supports both mouse and keyboard, and the gamepad.
The scene that deals with the movement, collision, and logic of the player. The player is a KinematicBody with a capsule collision shape, and the movement logic is within a Finite State Machine.
The scene also holds an instance of the
PlayerMesh for animation purposes. This scene lives in the
PlayerMesh.tscn scene. It holds the skeletal rig for the mesh's animation, the 3D model of the body and head sepearately, and the animation tree and player to control the animation workflow of the model. The lot is wrapped up in a spatial node with some logic to transition to which animation based on which state the player is in.
The scene that deals with the CameraRig movement. It follows the Player in the game, but in code it moves and rotates separately from it. It has a
SpringArm node to help with preventing collision with level geometry - moving the viewpoint forwards to prevent moving the camera inside geometry. It also has a system that holds the raycast for aiming-mode, and the 3D sprite that is a projected reticule. The logic is held in a finite state machine.
To change the player and the camera's behavior, you need to change properties on the corresponding states in their state machine.
Most of the configuration available for player movement are located on the
Move state in the Player scene - the player speed and the rotational speed.
The CameraRig has more options. On the main CameraRig state in the CameraRig scene are items like the default field of view, whether Y is inverted, and sensitivity.
In addition, the Aim state allows some finer-tuned changes, like whether the aiming camera is first or third person, and by how much it should be offset over-the-shoulder of the character.
While the scenes can be modified extensively with new nodes and raw code, the state machine model allow for some simple, new functionality with relative ease.
As an example, there is the
Extensions folder which contains additional player states for using the aiming view to fire a hookshot that pulls you towards the reticle. Once those states have been added to the Player's
Move state, you only need to replace the return statement in Move's
enter with code like
owner.camera.connect("aim_fired", self, "on_Camera_aim_fired") and Move's
exit with code like
owner.camera.disconnect("aim_fired", self, "on_Camera_aim_fired")
The source Blender file is available in the releases tab. The character comes with all its animations. At first glance, it can look like it is lacking a rig.
Instead of a complex rig with many controls, we use ephemeral rigs as seen in Richard Lico's 2018 GDC talk Animating Quill. To do so, we work with the Blender add-on Rig on the Fly. This allows you to quickly generate a rig and controls adapted to the animation at hand. Once the animation is done, you bake it, and you're done!
GDQuest is a social company focused on education and bringing people together around Free Software.
This Free Software is sponsored by our course Code a Professional 3D Character with Godot.
We share the techniques professionals use to make games and open source the code for most of our projects on our GitHub page.
This project is dual-licensed:
GDQuest and contributors (https://www.gdquest.com/).