Skip to content
This repository was archived by the owner on Dec 7, 2022. It is now read-only.

Long distance render tnt - #934

Open
Pablete1234 wants to merge 1 commit into
twizmwazin:masterfrom
Pablete1234:TNT
Open

Long distance render tnt#934
Pablete1234 wants to merge 1 commit into
twizmwazin:masterfrom
Pablete1234:TNT

Conversation

@Pablete1234

Copy link
Copy Markdown
Collaborator

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

@Pablete1234

Copy link
Copy Markdown
Collaborator Author

Real scrimm test: http://www.youtube.com/watch?v=fp6IA3ZzFeE

@ghost

ghost commented Jan 28, 2016

Copy link
Copy Markdown

@Pablete1234
Pablete1234 force-pushed the TNT branch 7 times, most recently from 00c8824 to 789eb08 Compare February 5, 2016 17:37
@Pablete1234
Pablete1234 force-pushed the TNT branch 3 times, most recently from 30c47f7 to 8418563 Compare February 6, 2016 05:05
@Pablete1234
Pablete1234 force-pushed the TNT branch 3 times, most recently from f7d6edf to ef300e2 Compare March 4, 2016 15:27
@Pablete1234

Copy link
Copy Markdown
Collaborator Author

New testing: https://youtu.be/dFLmknc8fDw
IMO it's pretty much done

@twizmwazin

Copy link
Copy Markdown
Owner

As soon as 1.9 is merged I want to get this on master

@Pablete1234

Copy link
Copy Markdown
Collaborator Author

@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

@twizmwazin

Copy link
Copy Markdown
Owner

That's fine

@Pablete1234

Copy link
Copy Markdown
Collaborator Author

@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

@twizmwazin

Copy link
Copy Markdown
Owner

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.

@Pablete1234

Copy link
Copy Markdown
Collaborator Author

@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)

@Pablete1234
Pablete1234 force-pushed the master branch 2 times, most recently from 27fe706 to 6d95d9c Compare March 28, 2016 06:28
@Pablete1234
Pablete1234 force-pushed the TNT branch 2 times, most recently from 475278b to baccf32 Compare May 15, 2016 13:43
@Pablete1234
Pablete1234 force-pushed the TNT branch 2 times, most recently from afea36d to d578c6e Compare May 25, 2016 01:20
@Pablete1234
Pablete1234 force-pushed the TNT branch 2 times, most recently from 0b6298c to d646185 Compare October 5, 2016 05:13
@Pablete1234

Copy link
Copy Markdown
Collaborator Author

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).
Videos of it in action (with 8 chunks render distance) :
https://youtu.be/xzaCbt5FtFI
https://youtu.be/4LVwyeOQxrs

@Pablete1234

Copy link
Copy Markdown
Collaborator Author

It's now working, and it reads player's chunks, but 2 things to keep in mind:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants