Go, Go, Godot!
  • 0

Inventory System v1.17 available

October 24, 2024

A new version of the Inventory System is available. This release includes various refinements to existing systems to flesh out more combat-related functionality.

Inventory Ammo Provider

The GGAmmoProvider component is responsible for providing ammunition to equipped weapons. Previously, it only had a “simple” strategy: Creating ammunition out of thin air. The new GGAmmoProviderInventoryStrategy pulls ammunition from items in the inventory it’s connected to. This allows players to pick up ammunition from loot boxes and item spawns

Weapon and Combat Refinements

The MyRangedWeapon2D class, which powers the two example guns in the Multiplayer Interaction Demo has received some ammo consumption refinements to go with the Inventory Ammo Provider mechanic and now emits signals when firing/reloading. Melee weapons and projectiles now use the GGHurtBox component to deal damage. The HurtBox applies damages to a HitBox, which is then processed by a DamageCalculator strategy to update the HealthStats component.

The new Ghost “Enemy” spawns as part of the Multiplayer Interaction Demo, and can receive damage from both melee and ranged weapons. When taking hits, the amount of damage floats above the character/object, which is all handled on the server and replicated to clients for multiplayer by a new set of classes.

Changelog

Features:

  • Added a new configurable MyEntitySpawner2D to spawn the Ghost
  • Added the GGAmmoProviderInventoryStrategy, along with some ammo and projectile rework.
  • Added configurable target (defaults to “_blank”) for the GGRichTextURLOpener.
  • Added GGFloatingNotifier component to inform the GGFloatingDisplay component to display floating numbers for server and clients.
  • Melee Weapons now each have dedicated scenes.
  • Ranged Weapons were reworked for improved ammo handling and signal emission when firing and reloading.

Bug fixes:

  • Corrected the Drag-and-Drop configuration for the Inventory In-Game Menu UI integration.
  • Ensure damage calculation only runs server-side.
  • Various corrections to the netfox implementation of the character scene.
  • The Tour instructions now correctly show that CMD (instead of CTRL) is the drag-and-drop modifier on Mac.

The Inventory System Deep Dive and Architecture Guide helps game developers implement advanced multiplayer inventories using Godot Engine. The PDF Guide contains over 500 pages of code walkthroughs, diagrams, and explains concepts related to inventories, items, and more.

Get It Now
Learn More

assetgdscriptgodottutorial
Posted in Godot.
Share
PreviousInventory System v1.18 available
NextInventory System v1.16 available

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Related Posts

  • Godot and Netlify
    January 22, 2023

    Quickly deploying Godot games on the web with Netlify

    When I think of video games, I generally still think of an application that is downloaded and runs on the client. Technically, that’s still the case with web-based exports from Godot Engine, since the web browser has to download the files before being able to run them. I thought maybe I could just run the …

  • August 3, 2022

    Share your Computer’s Mouse and Keyboard with your Steam Deck

    I use an app called barrier. It allows you to share your mouse and keyboard with multiple devices. I use it, because I tend to have my laptop and Macbook sitting next to my PC, and it makes working across all devices very convenient. It’s a mix of a multi-monitor and multi-computer setup. Concept Your …

  • November 27, 2024

    Toggling Visibility of Nested CanvasLayers

    I had a setup with nested CanvasLayer nodes. Toggling the visibility of the root CanvasLayer doesn’t hide any nested CanvasLayer nodes. My solution was to listen to the visibility_changed signal, find any CanvasLayer child nodes, and apply the same visibility to them.

  • September 25, 2023

    Generating documentation for GDScript

    Any sufficiently large code base needs documentation. Documentation tends to come in all sorts of shapes and sizes. Among them are high-level architecture and design docs, class and method interface documentation, and inline comments to explain optimized or complex algorithms so the reader doesn’t have to parse the logic in their head (often, this is …

    © 2026 GoGoGodot.io. All rights reserved.