godot-2d-jrpg-combat VS Rx.NET

So I'm trying to make a turn-based jrpg prototype based on this open project below. Basically, when I called the function _play_turn(P1), P1 node goes into this coroutine function and when you "completed" selecting action and target, P1 can act and get outside of this coroutine (pic below is just a sample, not all the codes in real script) https://github.com/GDQuest/godot-2d-jrpg-combat

godot also has a similar system that uses the Resource type. There's a great example putting them to use in a system from gdquest here: https://github.com/GDQuest/godot-2d-jrpg-combat

I had no idea how to start implementing a combat system so I started working on top of the GDquest's 2D JRPG Combat (https://github.com/GDQuest/godot-2d-jrpg-combat)

DynamicData is a .NET library that brings the power of reactive programming to collections. It is built upon the principles of Reactive Extensions (Rx), extending these concepts to handle collections like lists and observables more efficiently and flexibly. DynamicData provides a set of tools and extensions that enable developers to manage collections reactively, meaning any changes in the data are automatically and efficiently propagated through the application.

One of the greatest things i discovered recently, is Reactive programming / Reactive Extensions ( https://github.com/dotnet/reactive ).

https://github.com/dotnet/reactive has a lot of different time related extensions for "events". Maybe you'll find something for yourself, if you google for rate limiting with reactive.

Install Reactive Extensions: https://github.com/dotnet/reactive

Another option is to use the RxJava library in Java. This library uses reactive programming principles to make it easy to write asynchronous and event-driven code. It's particularly well-suited for handling streams of data and allows you to write code that is both efficient and easy to read.

I'd use a dedicated event bus based on Reactive Extensions or MediatR to publish domain events from your domain services. This probably doesn't solve all your ViewModel update problems as is, maybe you need to revise the granularity (maybe you can have smaller ViewModels that refresh single property that exposes the Model) and lifespan (sometimes you can create a ViewModel, make it perform it's task and then discard it completely) of your ViewModels.

If you're finding yourself in a situation where you need to turn this behavior into a pattern because there are a lot of View Models that need to execute async business logic in response to some changes, I'd go with something like MediatR or Reactive Extensions. The idea is, again, that some other, probably business-level, component listens to changes in a decoupled way (that means it doesn't subscribe directly to your View Model, but to an event bus instead). View Model publishes change events to the event bus, and business-component reacts to these events by executing the business logic.