Replies: 1 comment
-
|
Yeah, AI will often do way more than asked or break things because it doesn’t test frequently. Hope you get the mess cleaned up 😄 I’d suggest committing whenever something is done—even a single line or one‑word change. That helps a lot with cleanup while maintaining the repo. And yeah, keeping backward compatibility for all Unreal Engine versions is really time‑consuming. I go back and forth checking each version. My approach: just make it run on one version first, and test other versions when everything else is done. I do that right before release. For normal commits I avoid checking all UE versions—saves a ton of time. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'd like to share some of the updates I've made but my build has gone about 150+ updates with new features, actions, bug fixes etc.
I'm not sure how my fork can even be merged anymore.
Some key things I fixed.
I initially only set out to fix 1 bug so I could keep working... but I kept finding more bugs so I kept smashing them out. After a couple of dozen bugs I realize I haven't been committing any of the changes. I am still constantly fixing bugs and blockers.
I also think trying to support all version of UE5 is noble but overly time/token consuming.
Also right now trying to come up with a better multi-agent workflow.
So my local setup is a mess now :D
Beta Was this translation helpful? Give feedback.
All reactions