@rscata alright! One thing that is not intuitive in this version is that you can only see the error messages and stack traces if you turn on DEBUG=colyseus:errors
No problem! The problem however still presist if you use the server from the Unity package if im not mistaken. You might want to update this one aswell?
The Timeline is an experimental feature only present for lag compensation on the server-side. I personally haven't seen anybody using it yet. You can add it as a dependency in your client-side and take the snapshots whenever the state updates if you'd like to.
There's a big difference between lag compensation and client prediction techniques, though. I think you're looking for client-prediction. Unfortunately, the framework doesn't provide an easy way of doing either.
Ok, thank you. Oh yeah, I did actually figure it this way, but in this case, I'm worried about performance, as it would need to do 7x (10x, if I would also include the scale) more callback calls as if it would just return the array. So the string solution does work ok (.split('|')/.join('|')), but it sends/receives more bits of data.
Mean, for now, there is no way to hack around, so I would be able to get an array in "one batch"?
@endel I just finished an implementation of AI that puts players into "Regions". The server will broadcast a global state for messages, trades, etc. and then only broadcasts data from that region.
I have to work on sending the unseen state of a new region to a player when they first get into it and making the change more user friendly, but I'll try to upload my code soon!
