-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Items usually don't appear on the client #175
Comments
It seems
I tried this beforehand which doesn't require changing the codec logic. It worked much more of the time, but still failed often, so changes to how packets are sent are necessary.
Also, when I try to decode
I'm writing then reading back the packet just before it's sent.
|
Interesting, thanks! As I understand it, Your idea of writing packets to a buffer on the game logic threads and then only writing them out on the IO threads is worth a try; I'll implement this tonight. As for |
Something else I found out: if the item doesn't appear when it is dropped, it does show on the client upon relog. |
Seems like this is fixed by 6895f44. |
I've still observed it a few times; are you sure? I have the feeling this is caused by dtolnay/inventory#7—some systems don't seem to be registered properly. The refactor in the hopefully-last-refactor branch should fix this definitively. |
When an item is spawned with the Legion rewrite, it usually doesn't appear on the client. Occasionally, the entity counter in the client debug menu will increment and then rapidly go back to 0, but the item stack still cannot be seen.
On the pre-Legion code, spawning items worked fine, so this is a bug confined to the new implementation.
Some debugging revealed that:
The text was updated successfully, but these errors were encountered: