@NoelFB The issue is really frustrating, because the solution for us that we have to pass any captures into the lambda coroutine so we never use the lambda's "this". It's a viable workaround but maddening that you need to live in vigilant fear.
@damthauer On a related note: we have a number of useful Unreal Engine support classes for creating things like latent BP Tasks, as well as easily dispatching tasks to Unreal worker threads. It sounds like it might be valuable to release those as part of a future release of Squid::Tasks!
@damthauer If you have time to share, we're interested in gathering specific use cases that highlight situations that we didn't encounter in the course of our own development. We're also very interested in hearing if UE5Coro has found an elegant solution to the issues we encountered.
@damthauer Hey there! I'm one of the authors of Squid::Tasks (alongside Elliott). Could you share your top UE5Coro features you'd like to see added? Thanks!
@JeremySharps@GiantSquidology That's true, but hanster incisors (and cheek teeth) are never replaced. I think the key to that factoid is on constant replacement *and* growth.
@silliet Just saw your GDC talk! I am curious if you ever played Save the Date? It's a little visual novel about time loops and the power of ambiguous narrative, and I wondered if that or other narrative game experiences were parts of your team's inspiration.
@Veqtor @xavierck3d Put another way - what's their incentive to not do the same work to mint an asset they can sell to their players and keep 100% of the profit from. They could do that with NFTs, or just a proprietary traditional account server like they do now.
@Veqtor @xavierck3d What is the financial incentive for a new game that comes out to support this standard, and (e.g. the beanies) create all 88 beanies as assets in their game, etc? There is real work to be done, which will cost real money, and that money needs to come from somewhere.