|
|
Post by deauth0r on Dec 28, 2019 22:14:42 GMT
last night someone successfully created a ban chunk by spawning heads that contained about 32767 digits of pi (not even joking), this could easily be fixed by detecting (scan 10 blocks in a sphere around the player for a playerhead and check the name of said head) and then removing player heads which are over 22 characters in length
|
|
_Windows
Club 4000 Member
Posts: 7,881
| Likes: 9,611
|
Post by _Windows on Dec 29, 2019 13:48:13 GMT
Agreed that this is needed. There is no point in making these heads other than to cause lag or disconnect chunks.
|
|
Video's Alt Account
Member
This forum account is for demonstrating technical feats about what can load the forums.
Posts: 29
|
Post by Video's Alt Account on Dec 31, 2019 6:17:07 GMT
Vouch.
|
|
1cloud_
Veteran Member
hi
Posts: 315
|
Post by 1cloud_ on Jan 1, 2020 4:38:55 GMT
Vouch.
|
|
super
Veteran Member
Among Us
Posts: 1,282
|
Post by super on Jan 2, 2020 3:03:04 GMT
this is interesting. i'll see what i can do.
|
|
super
Veteran Member
Among Us
Posts: 1,282
|
Post by super on Jan 2, 2020 4:36:30 GMT
 this is now fixed for normal placement. please report any instances of other forms of placement here. |
|
|
|
Post by Polaris Seltzeris on Jan 2, 2020 5:21:37 GMT
this is now fixed for normal placement. please report any instances of other forms of placement here. I don't think this problem has to do with pi in particular, my guess is that it can't accept more than a 16 bit string or signed integer (which explains why 32767 was used). EDIT: Actually, it probably had nothing to do with what length it accepts (it probably could've accepted anything up to the 32 bit limit), but rather that the server or client won't handle a length that large. It could've been prevented if the server developers (not anyone here) had the sense to put in the most basic of sanity checks, rather than allowing people to put in a length that ginormous. Doesn't have anything to do with pi in particular though. |
|
super
Veteran Member
Among Us
Posts: 1,282
|
Post by super on Jan 2, 2020 15:25:53 GMT
this is now fixed for normal placement. please report any instances of other forms of placement here. I don't think this problem has to do with pi in particular, my guess is that it can't accept more than a 16 bit string or signed integer (which explains why 32767 was used). EDIT: Actually, it probably had nothing to do with what length it accepts (it probably could've accepted anything up to the 32 bit limit), but rather that the server or client won't handle a length that large. It could've been prevented if the server developers (not anyone here) had the sense to put in the most basic of sanity checks, rather than allowing people to put in a length that ginormous. Doesn't have anything to do with pi in particular though. yes, the way it works is by spamming the block. the string is so massive that it can crash people. it is stored as the skull's owner. pi (as a number) doesn't have anything to do with it. |
|
|
|
Post by deauth0r on Jan 2, 2020 18:01:53 GMT
I don't think this problem has to do with pi in particular, my guess is that it can't accept more than a 16 bit string or signed integer (which explains why 32767 was used). EDIT: Actually, it probably had nothing to do with what length it accepts (it probably could've accepted anything up to the 32 bit limit), but rather that the server or client won't handle a length that large. It could've been prevented if the server developers (not anyone here) had the sense to put in the most basic of sanity checks, rather than allowing people to put in a length that ginormous. Doesn't have anything to do with pi in particular though. yes, the way it works is by spamming the block. the string is so massive that it can crash people. it is stored as the skull's owner. pi (as a number) doesn't have anything to do with it. even then, how do you know that there aren't any schematics out there with an entire chunk of ban heads, needs to be some additional checks put into fawe tbh |
|
super
Veteran Member
Among Us
Posts: 1,282
|
Post by super on Jan 2, 2020 20:36:16 GMT
yes, the way it works is by spamming the block. the string is so massive that it can crash people. it is stored as the skull's owner. pi (as a number) doesn't have anything to do with it. even then, how do you know that there aren't any schematics out there with an entire chunk of ban heads, needs to be some additional checks put into fawe tbh that's why i told people to give me schematics (etc) in my first post |
|
