Tamás Gálffy

Oh that's a good one! I remember encountering this, maybe I just haven't gotten around to fixing it yet. I'm considering having a `spawned_at` field on RollbackSynchronizers to store when...

Spent some time on this, some things to add. --- > The below logger I added, reports that a new player joining, runs the below function from tick 0 to...

Managed to fix on user project with the following change to TickInterpolator: ```gdscript func _after_tick_loop(): if enable_recording: push_state() PropertySnapshot.apply(_state_from, _property_cache) ``` The change is adding the `PropertySnapshot.apply` call. Apparently what...

Ok so If I read you right, the proposed fields are: - Player ID - Session ID - Joined at tick - Avatar I'll consider these given the way netfox...

Closing this issue for now, I don't see enough demand to add these in addition to the justifications in my previous comment. Same for #269. One addition to Player ID...

@TheYellowArchitect the video doesn't show up on my end :slightly_frowning_face: Could you try sharing it as an unlisted YT video or something else?

@TheYellowArchitect I've updated @284, could you please check if the issue still persists on that branch?

> This is a design flaw. How? You want the server to know you want to fire, so you call an RPC. Since it's using an RPC, there's no point...

I'll return to this issue with more detail, but I have to highlight this: > For example, a replay system cannot work by simply having the initial states, and all...

Since it would take some time until I can dedicate more attention to this, I suggest building whatever makes sense for your game. What I'd probably do is this: 1....