-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.Net Framework Compatible Package #83
Comments
I've taken the naive approach here (not a .NET expert) and changed the https://github.com/lewiji/activelogic-cs e.g. by cloning the repo, building the |
Sorry for the late reply; this is mostly .NET compatible with the Unity API calls fenced off. The test suite runs over .NET. |
I've been using the above fork with Godot engine without issue so far, for context |
@lewiji would a Nuget package help at all with the Godot integration? Other than that I see no reason to not test changes from your fork and merge some! |
A Nuget package did already exist - https://www.nuget.org/packages/ActiveLogic/ |
Personally I'm happy just linking to the library via a filesystem reference, but I'm a solo dev and my C# experience is pretty much limited to Godot scripting the last 2-3 years (haven't used C# outside of that over my 12 years as a swe). So I don't know what the best practice/correct/desired thing is for dedicated .NET programmers who use godot :) (and fwiw in case this was your question: initially I tried using the nuget package, but it wasn't compatible and couldn't be used, which is why I investigated and forked) Something worth noting, is Godot will soon(tm) be migrating from Mono, over to targeting dotnet 6 CLR, work is underway and I think almost complete, so I'm not sure how that affects things in terms of the targets of dependent packages. I'm working on getting a dotnet 6 fork of godot working on my machine with some other godot devs, so will test that out, it may well just work with the standard AL library target. This is for godot 4, which is currently in early alpha and probably won't be stable until late this year, possibly the dotnet 6 changes might run over longer, and godot 3 will still be supported for a long time. So there's a bit of a question mark there around framework targets that I'm not sure of.
Yeah, I think I follow you and I tend to just avoid doing that stuff inside BTs anyway; I have some internal state to individual trees that seems to work fine, but it's nothing complicated. But I don't really do anything like pulling state out of the BT into a game entity, or doing conditional logic from outside of the BT based on the BT state. It's something I haven't really found a need for, so haven't tested it out much. But more docs explaining those features may inspire some use where I've done things in a less flexible way because I wasn't aware of the feature set around this! |
I have a project I'd love to use this library on and for reasons I'm limited to .Net Framework only. Would it be possible to get a .Net framework compatible package on Nuget?
The text was updated successfully, but these errors were encountered: