NotAFile
NotAFile
I had a look and can't find any missing information. Feel free to reopen.
Regarding the fallback options, I started a ExtensionFallbackPolicy mechanism in pique which would allow protoexts to specify if a fallback is possible and allow scripts and admins to specify if...
> suddenly everyone has to fall back because the vanilla client doesn't support the extension. To be clear, this would be a per-connection thing. So the fallback would only affect...
I had looked into a design here too a while back. I can try to find my notes again but it avoids a few pitfalls that this is vulnerable to,...
The solution I ended up with was using the server list protocol to send the server keys out-of-band and to derive new client keys per server for security and privacy....
Yes, the Feature flags are requirements for pretty much all new packets we add... However, we really must do feature flags on both sides, for other use cases. Adding e.g....
It would be nice if these could be identical to the 1.x packets... Is this the case?
I think it might be a better idea to do the resource packs thing instead of reinventing the wheel for every model... although I can't think of a way to...
The 1.x entities have a "carrier" field which can specify which user is currently carrying the object. I think genereally it would be useful to make this as close to...
a few more concerns: * how should the physics used for the object be decided? Some objects like tents have different types of physics and those should ideally be brought...