Post

I spent some of this week making an I/O system for level scripting in Unreal for @sleightofhand.game! I have long had thoughts on why these kick ass. Here's an unusually long blog post on: -why these kick ass -why they are necessary -how mine works -etc etc www.joewintergreen.com/i-o-systems-...

Cool qol details in the tool: -Dropdowns for everything -If targeting multiple actors it tells you how many -Button to duplicate an input -Button to select all with same name -Button to assign unique names to selected actors -Auto-assigns targetnames based on actor labels/vice versa as appropes

Added some debug vis for both instant and in-flight IO outputs today

moved it into a plugin so i can more easily release it at some point

this is fully a plugin so it can be project-agnostic, cpp'd a few things that were bp before (mostly still BP) etc. swapped it over at work so that i am not maintaining two versions. the debug stuff is fun to look at. @radiatoryang.bsky.social made duck hunt using buttons, movers and timers

fun to watch the debug on these lasers that turn each other on and off

got back to trying to finish this off so yall can give me money for it today. not quite there yet but added some new features: -disabling an output without deleting it, v useful for testing etc -"unlocking" an output so that you can type target/function names manually instead of choosing them

The latter is useful for addressing actors that aren't present at editor-time but which you know will exist at runtime, like: the player. so if you know the player will exist and has a function called "die" you could call that even though it's not there in the editor for instance