Chickensoft.PowerUps 4.0.0

Suggested Alternatives

Chickensoft.AutoInject

Additional Details

AutoInject 2 now contains all of the mixins provided by PowerUps.

dotnet add package Chickensoft.PowerUps --version 4.0.0                
NuGet\Install-Package Chickensoft.PowerUps -Version 4.0.0                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Chickensoft.PowerUps" Version="4.0.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Chickensoft.PowerUps --version 4.0.0                
#r "nuget: Chickensoft.PowerUps, 4.0.0"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Chickensoft.PowerUps as a Cake Addin
#addin nuget:?package=Chickensoft.PowerUps&version=4.0.0

// Install Chickensoft.PowerUps as a Cake Tool
#tool nuget:?package=Chickensoft.PowerUps&version=4.0.0                

๐Ÿ”‹ PowerUps

Chickensoft Badge Discord Read the docs line coverage

A collection of power-ups for your C# Godot game scripts that work with the Introspection source generator.


<p align="center"> <img alt="Chickensoft.PowerUps" src="Chickensoft.PowerUps/icon.png" width="200"> </p>

Currently, two PowerUps are provided by this package: AutoNode and AutoSetup.

  • ๐ŸŒฒ AutoNode: automatically connect fields and properties to their corresponding nodes in the scene tree โ€” also provides access to nodes via their interfaces using GodotNodeInterfaces.
  • ๐Ÿ›  AutoSetup: provides a mechanism for late, two-phase initialization in Godot node scripts to facilitate unit-testing.

Chickensoft also maintains a third PowerUp for dependency injection called AutoInject that resides in its own AutoInject repository.

๐Ÿ“ฆ Installation

Unlike most nuget packages, PowerUps is provided as source-only nuget package that actually injects the source code for the PowerUp into your project.

[!TIP] Injecting the code directly into the project allows this package to work with a wide range of compatible Godot projects.

To install PowerUps, add the following to your .csproj file. Be sure to get the latest versions for each package on Nuget.

[!NOTE] The AutoNode PowerUp requires GodotNodeInterfaces, which allows you to access Godot nodes via an interface to facilitate unit testing.

<ItemGroup>
    <PackageReference Include="Chickensoft.Introspection" Version="..." PrivateAssets="all" OutputItemType="analyzer" />
    <PackageReference Include="Chickensoft.Introspection.Generator" Version="..." />
    <PackageReference Include="Chickensoft.PowerUps" Version="..." PrivateAssets="all" />
    <PackageReference Include="Chickensoft.GodotNodeInterfaces" Version="... " />
</ItemGroup>







๐ŸŒฒ AutoNode

The AutoNode PowerUp automatically connects fields and properties in your script to a declared node path or unique node name in the scene tree whenever the scene is instantiated, without reflection. It can also be used to connect nodes as interfaces, instead of concrete node types.

Simply apply the [Node] attribute to any field or property in your script that you want to automatically connect to a node in your scene.

If you don't specify a node path in the [Node] attribute, the name of the field or property will be converted to a unique node identifier name in PascalCase. For example, the field name below _my_unique_node is converted to the unique node path name %MyUniqueNode by converting the property name to PascalCase and prefixing the percent sign indicator. Likewise, the property name MyUniqueNode is converted to %MyUniqueNode, which isn't much of a conversion since the property name is already in PascalCase.

For best results, use PascalCase for your node names in the scene tree (which Godot tends to do by default, anyways).

In the example below, we're using GodotNodeInterfaces to reference nodes as their interfaces instead of their concrete Godot types. This allows us to write a unit test where we fake the nodes in the scene tree by substituting mock nodes, allowing us to test a single node script at a time without polluting our test coverage.

using Chickensoft.GodotNodeInterfaces;
using Chickensoft.PowerUps;
using Godot;
using Chickensoft.Introspection;

[Meta(typeof(AutoNode))]
public partial class MyNode : Node2D {
  public override partial void _Notification(int what);

  [Node("Path/To/SomeNode")]
  public INode2D SomeNode { get; set; } = default!;

  [Node] // Connects to "%MyUniqueNode" since no path was specified.
  public INode2D MyUniqueNode { get; set; } = default!;

  [Node("%OtherUniqueName")]
  public INode2D DifferentName { get; set; } = default!;

  [Node] // Connects to "%MyUniqueNode" since no path was specified.
  internal INode2D _my_unique_node = default!;
}

๐Ÿงช Testing

We can easily write a test for the example above by substituting mock nodes:

using System.Threading.Tasks;
using Chickensoft.GodotNodeInterfaces;
using Chickensoft.GoDotTest;
using Chickensoft.PowerUps.Tests.Fixtures;
using Godot;
using GodotTestDriver;
using Moq;
using Shouldly;

public class MyNodeTest : TestClass {
  private Fixture _fixture = default!;
  private MyNode _scene = default!;

  private Mock<INode2D> _someNode = default!;
  private Mock<INode2D> _myUniqueNode = default!;
  private Mock<INode2D> _otherUniqueNode = default!;

  public MyNodeTest(Node testScene) : base(testScene) { }

  [Setup]
  public async Task Setup() {
    _fixture = new(TestScene.GetTree());

    _someNode = new();
    _myUniqueNode = new();
    _otherUniqueNode = new();

    _scene = new MyNode();
    _scene.FakeNodeTree(new() {
      ["Path/To/SomeNode"] = _someNode.Object,
      ["%MyUniqueNode"] = _myUniqueNode.Object,
      ["%OtherUniqueName"] = _otherUniqueNode.Object,
    });

    await _fixture.AddToRoot(_scene);
  }

  [Cleanup]
  public async Task Cleanup() => await _fixture.Cleanup();

  [Test]
  public void UsesFakeNodeTree() {
    // Making a new instance of a node without instantiating a scene doesn't
    // trigger NotificationSceneInstantiated, so if we want to make sure our
    // AutoNodes get hooked up and use the FakeNodeTree, we need to do it manually.
    _scene._Notification((int)Node.NotificationSceneInstantiated);

    _scene.SomeNode.ShouldBe(_someNode.Object);
    _scene.MyUniqueNode.ShouldBe(_myUniqueNode.Object);
    _scene.DifferentName.ShouldBe(_otherUniqueNode.Object);
    _scene._my_unique_node.ShouldBe(_myUniqueNode.Object);
  }
}

๐Ÿ›  AutoSetup

The AutoSetup will conditionally call the void Setup() method your node script has if from _Ready if (and only if) the IsTesting field it adds to your node is false. Conditionally calling a setup method allows you to split your node's late member initialization into two-phases, allowing nodes to be unit tested. If writing tests for your node, simply initialize any members that would need to be mocked in a test in your Setup() method.

using Chickensoft.PowerUps;
using Godot;
using Chickensoft.Introspection;

[Meta(typeof(AutoSetup))]
public partial class MyNode : Node2D {
  public override partial void _Notification(int what);

  public MyObject Obj { get; set; } = default!;

  public void Setup() {
    // Setup is called from the Ready notification if our IsTesting property
    // (added by AutoSetup) is false.

    // Initialize values which would be mocked in a unit testing method.
    Obj = new MyObject();
  }

  public void OnReady() {
    // Guaranteed to be called after Setup()

    // Use object we setup in Setup() method (or, if we're running in a unit 
    // test, this will use whatever the test supplied)
    Obj.DoSomething();
  }
}

๐Ÿ’ก AutoInject provides this functionality out-of-the-box for nodes that also need late, two-phase initialization. It also supplies an IsTesting property but will call the Setup() method after dependencies have been resolved (but before OnResolved() is called). If you're using AutoInject, note that you can either use the AutoSetup or Dependent PowerUp on a node script, but not both.


๐Ÿฃ Package generated from a ๐Ÿค Chickensoft Template โ€” https://chickensoft.games

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Chickensoft.PowerUps release.