Plugin Submission with Blueprints - static

Hi,

just wanted to ask if this is still relevant for custom Blueprint nodes in marketplace plugins:

If so, what is the reason for that?

I mean, for a potential existing plugin that uses an instance to call methods on itself, would i really now have to wrap all calls with a static function with the actual instance as a parameter just to call it?

Thanks,

Hey Knut and fellow ATBTT users! I mentioned this on one of the Youtube vids but wanted to check in here first. I created a variation on chess in BPs a while back, but want to refactor it. The ATBTT has a ton of functionality already that I’d planned on using but, I wanted to know if anyone has already created any versions of chess before I go further. I saw in an earlier thread someone mentioned wanting chess-like movement, and Knut had looked into it and determined that it would take a fair amount of BP work to get working correctly. Anyone make progress on that and have any tips for me?

Either way, upwards and onwards with it, I’m very excited to get this thing working in a better system (my old BPs are just dirty and clunky, even though they work…).