Hey everyone! 
The core concept is done — RPG Engine now has full client-side prediction and much finer replication control.
I’m currently adapting the event system to this new workflow, and then I’ll ship the update 
And yes — all of this is done in Blueprints, with no C++ 
Hey everyone! I’ve finished the core part of the new update
Right now I’m testing the new client-side prediction system under 200 ms latency to see how it behaves under noticeable network delay while still keeping the server-authoritative logic intact.
If everything goes well, the next step is polish and release prep
Hey everyone! 
Today I finished work on the updated D_CharacterStates database 
It now better supports scenarios where some states can react locally on the client first and then be handled by the broader multiplayer logic 
The main goal of this approach is to make gameplay feel faster and more responsive In situations where it makes sense, the player can see an immediate reaction to their action instead of always feeling network delay first, while the system still keeps everything structured and under control 
Right now I’m continuing to integrate this into other mechanics and test how it behaves in real multiplayer conditions 
So far, the direction looks very promising — the game already feels much more responsive, and the overall architecture remains clean and manageable
In short: prediction-side work is moving forward, and the foundation for it is now much stronger 
Working on: BP_StateOrchestratorComponent
Building a routing/decision layer that sits between input/gameplay events and BP_MediatorModule. Its only job — look at the incoming state request, check the NetworkMode, and route it to the right execution path: ServerOnly, PredictedSafe, or Local.
Before this, every input handler had to manually figure out how to activate a state over the network. Now that logic lives in one place — the orchestrator decides, the mediator executes. Clean separation of concerns.
Hey everyone!
Today I added support for seeing shot and explosion effects even while using thermal vision 
We finally got to this feature
Now special vision modes won’t hide important combat effects, which makes battles feel much clearer and more complete visually 
It may seem like a small improvement, but these kinds of details really make the overall experience better
No, the smoke is very hard to see. I’ll improve it now.
Hey everyone! 
Honestly, I don’t even remember what originally triggered the request for this update — but now it’s here: RPG Engine V6.11.1
Thermal vision has now been properly refined, so visual effects remain visible while this mode is active On top of that, if the player was already using night vision or thermal vision through a skill or device before aiming, that visual state now carries over correctly into the scope view 
That means no more overexposed image or doubled visual processing when the same night/thermal effect is applied twice from different sources Overall, this makes special vision modes feel much cleaner, more consistent, and far more polished in actual gameplay
Hey everyone!
Work on the upcoming update is moving fast, and today I finished the full debugging pass of the Character State System.
The best part: the new prediction layer is already showing excellent results. Even under 400 ms latency, gameplay remains responsive enough for the player to stay engaged and keep taking actions — something that would feel dramatically worse without this system in place.
This is a major leap forward for RPG Engine. The project now has a far more advanced prediction-driven multiplayer foundation, pushing it toward a level that is rarely seen in Blueprint-only multiplayer frameworks.
The update is getting very close. RPG Engine is entering a new stage — one defined by better responsiveness, stronger multiplayer architecture, and a much higher standard for systems built without C++.
