(39) 's Extra Blueprint Nodes for You as a Plugin, No C++ Required!

Yeah, when I suggested a “do-once-and-drop” for the preview releases, I had no idea that such radical changes were being made across incremental versions.

I’d LIKE to think that the reason for is simply that Epic is making some deep changes in advance of marketplace plugins to obviate type of thing in the future and it’s just a one-off problem with bad timing (it seems like both times Victory did weird stuff, it was in making references to other plugin libraries), but honestly who knows at point.

I can certainly say I HOPE that’s what they’re planning, because if is the sort of thing everyone with a marketplace plugin is up against, marketplace plugins are dead in the water. I mean, near as anyone can tell, nothing that broke in Victory even had anything to do with the changes Epic is making between these version numbers. It’d be one thing if a plugin was hooked into audio decoding and then that got updated, but is stuff completely unrelated to the features and bugfixes Epic has listed for these incremental updates, it seems like.

I don’t get it.

When I say I’m out of my element when it comes to coding I’m not at kidding (I had to look through the Victory source for obvious comments to figure out that // is how you comment out a line. That’s how out of my depth I am poking around in there.)