Closed nsg closed 8 years ago
Note: you need to do a local interpolation for this. The server latency is to large.
Needs the server to know which item is currently selected in the belt? Like I see, the server only needs to know what block we what to place, when we want to place a block. So what I mean, rather keep the server completely out of this?
Hm, we loses the ability for the server to change the selection for us. But I like the idea to simplify things... That do you think @petterarvidsson?
On 25 December 2015 20:23:26 CET, Henningstone notifications@github.com wrote:
Needs the server to know which item is currently selected in the belt? Like I see, the server only needs to know what block we what to place, when we want to place a block. So what I mean, rather keep the server completely out of this?
Reply to this email directly or view it on GitHub: https://github.com/konstructs/client/issues/109#issuecomment-167259326
Hm, I actually didn't think of the possibility that the server might want to change the selection… But wouldn't it be somehow confusing to the players if suddenly their selection changed, although they didn't do a thing? For me it would :P
I guess not, the client could send this information every time the user clicks (would add very little overhead). I don't think we use the information for anything in the server at the moment, so I would vote for doing it this way (unless we stumble up on something while implementing as often happens). Shared state is always a pain :-)
Use scroll the mouse wheel to select items in the inventory belt.