-
Notifications
You must be signed in to change notification settings - Fork 47
Long distance render tnt #934
base: master
Are you sure you want to change the base?
Conversation
27b70c1
to
b75e426
Compare
Real scrimm test: http://www.youtube.com/watch?v=fp6IA3ZzFeE |
00c8824
to
789eb08
Compare
30c47f7
to
8418563
Compare
f7d6edf
to
ef300e2
Compare
New testing: https://youtu.be/dFLmknc8fDw |
As soon as 1.9 is merged I want to get this on master |
@twizmwazin in 1.9 some entity rendering changed, the render distance for tnt is now half the client chunk render distance, and armor stands now render as far as your render distance goes, so i would rather use them than fake players |
That's fine |
@twizmwazin the issue is, how far away tnt should render dependes on the client settings, so having long render distance tnt is a bit harder, as we need to get the data from the client settings packet to know the amount of chunks the player is rendering |
I believe there is a way of getting some of players' settings. The server uses it to know how many chunks to send to the client. |
@twizmwazin yes, the setting exists, and it's sent by the client in the client settings packet, but that packet doesn't have an event, and doesn't get saved anywhere (that i'm aware of) in NMS (i tried to find it in 1.8 for the wither) |
27fe706
to
6d95d9c
Compare
475278b
to
baccf32
Compare
afea36d
to
d578c6e
Compare
0b6298c
to
d646185
Compare
Fixed and updated for 1.10, missing the setting for chunks, default to 64 blocks (as if all players had 8 chunks, if playing with more than 8 chunks, you will see the tnt twice (the real tnt and the fake tnt) in specific distances). |
It's now working, and it reads player's chunks, but 2 things to keep in mind:
|
Needs testing, and i'm not sure about how this affects performance with a big amount of players & tnt
Small demo of what a big explosion looks like:
https://www.youtube.com/watch?v=82I_gTsthWI