Guild Tactics
A downloadable game for Windows and Linux
Small combat demo for an in-progress Tactics RPG game, developed w/ Godot 4
WASD + space (confirm) + escape (cancel) for controls.
I've yet to add a fail / win state, so if you get to that point you can close+reopen to restart (if you want).
There is an in-game help menu, please give it a read for an explanation on mechanics.
This isn't exactly a "press release" or anything meant to be completely playable (yet). I'm just uploading this to share the in-progress combat demo with friends and the like.
Download
Install instructions
Just run the exe file.
Comments
Log in with itch.io to leave a comment.
THIS IS SO SICK! I found your devlog on youtube recently and it’s really inspiring since I’m trying to work on a similar system :D ! At the moment I’m trying to get the player to move when I click on a gridtile, but it isn’t behaving lol. But yeah! Please keep updating your progress it’d be rly cool to see 👍
Wow this is super awesome! I wish i could see the source code lmao. I am working on a tactics game as well, and I made a system to see how far the character should be able to move (with move cost and walls etc., which took longer then i'd like to admit.)
I made this system for 2D tilemaps, and am wanting to port it over to 3d. I was wondering how your system works for moving your characters
You dont want to see the source code lol... but as far as porting 2D to 3D, in all honestly I use mostly 2D oriented data with some lookups for things like height at a given position to help translate a 2D position to a 3D position. In other words, I have plain 2D map /data but track the heights in a separate data set, so for the most part its just 2D rendered in 3D.
ohh ok.
Do you use a tilemap and just have a custom renderer? how does it work?
Mmm no, the Tilemaps / Gridmaps in Godot were not very helpful. I made the entire map in Blockbench actually, and textured it like a normal 3D model, so really the map is just one mesh and is almost entirely distinct from the actual navigation. Navigation is setup by way of a GridMap; I just have a Gridmap with one, 50% transparency red cube in its mesh library and I draw that cube everywhere that is walkable (so on top of every "tile"). So there really are no tiles per se. At runtime, I just get every used cell from that Gridmap, where a red cube was, and register that position's X and Z value to an Astar2D object. I also track the y position in a separate lookup/dictionary, one where I can provide an astar ID (or position, doesn't matter) and get back a Y value - that way I can easily translate a 2D position to a 3D position. Why don't I just save the 3D positions? Well thats a good point, but most of the game logic runs on a 2D basis for simplicity and easier math since the Y value is rarely used in most cases.
Hi! I am building something similar for my children to play -- would you be willing to share how you implemented the turn order GUI in Godot? I really love the way you did it.
I look forward to hearing from you!
Hey Richard, thanks for the feedback! The UI is where I probably spent most of my time so I'm glad to hear its well received haha, took a lot of work to get is 'just right'. As far as the Turn Order GUI, its kind of a lengthy explanation so I'll have to post a video to YT with more details and let you know when that happens. For now though, the general idea is this:
1. PanelContainer -> HBoxContainer -> Control -> TextureRect(s)
The Control under the HBoxContainer lets the inner TextureRects move around freely, while still letting you inherit what their size should be based on the constraints of the PanelContainer/HBoxContainer that holds it all.
2. Outline Shader on the character images
The TextureRects each have the corresponding character image, and this has a Canvas shader that outlines the texture with a color that is picked based on whether the character is an enemy or ally.
3. TurnManager (class)
This isn't GUI itself, but its the data that drives the GUI. It holds all of the character's and their turn orders in an array, where turn order is implied based on index. When the array changes, the TextureRects are updated. If there are, lets say, 8 texturerects - each rect is assigned the nth index of the array from the TurnManager and just displays that character's texture. So rather than having a TextureRect assigned to each character implicitly, its more about being assigned to a specific index in that array the TurnManager maintains and then updating the GUI state whenever that array changes.
I hope that maybe gives some idea. I hope to put out videos soon going over the project and discussing more of the ideas and topics to help other people, its just kind of hard to compile all of that information so I've been putting it off haha