Read our own action manifest to configure inputs #156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As long as a game doesn't have an action manifest configured in the Steamworks publisher UI, it is free to call SetActionManifestPath as many times as it wants.
These are still the same hardcoded inputs, reading the manifest is a separate problem.
Not complete, still only actually getting handles for the default action set.
I don't wanna talk about it. So many layers of wrong, and I somehow discovered them in reverse order.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For my application, I am dynamically generating action sets at startup. Since there was already a TODO about looking at the JSON to set up inputs internally, I did that. This also required fixing the other TODO about renaming actions so they match the Godot button names.
I also allow starting up without an action set present, so that it can be set at the application's leisure. As long as a game doesn't have an action manifest configured for publishing via the Steam backend, it is free to call
SetActionManifestPathas many times as it wants and at any point during application lifecycle. At the moment a blank action set is created immediately at startup, but this is to make the inspector not explode when looking at the property. I want to remove this eventually.This might fix #132. I'm using input in a weird way for my app so I haven't tried mapping actual analog data through to a game as godot input.