2019-09-23 20:58:15 ItzKmaf XD 2019-09-23 20:58:23 MiniDigger am working on a server :D 2019-09-23 20:58:28 MiniDigger my client doesn't do shit rn 2019-09-23 20:58:30 ItzKmaf What for 2019-09-23 20:58:36 ItzKmaf And quick question. 2019-09-23 20:58:44 ItzKmaf What packets are needed 2019-09-23 20:58:45 MiniDigger just for fun 2019-09-23 20:58:51 ItzKmaf To keep a connection going 2019-09-23 20:59:02 ItzKmaf Like what ones need to be responded to 2019-09-23 20:59:06 ItzKmaf for 1.14.4 2019-09-23 20:59:07 MiniDigger just keep alive 2019-09-23 20:59:30 MiniDigger after you got "ingame" 2019-09-23 20:59:43 MiniDigger see https://wiki.vg/Protocol_FAQ#What.27s_the_normal_login_sequence_for_a_client.3F 2019-09-23 20:59:50 MiniDigger altho you can skip most of those 2019-09-23 21:00:24 MiniDigger heh, last updated yesterday 2019-09-23 21:00:34 ItzKmaf Thanks 2019-09-23 21:00:36 MiniDigger and i thought I was going crazy for seeing new packets in there 2019-09-23 21:01:22 MiniDigger but thats actually a good idea, I could try implementing my client 2019-09-23 21:11:28 ItzKmaf How do we show no skin parts 2019-09-23 21:11:33 ItzKmaf Displayed Skin Parts Unsigned Byte Bit mask, see below 2019-09-23 21:11:39 ItzKmaf Displayed Skin Parts flags: 2019-09-23 21:11:52 ItzKmaf Do we just send 0000 2019-09-23 21:12:42 timmyRS Yes, that would be the way to do it 2019-09-23 21:12:44 ItzKmaf 0x00* 2019-09-23 21:12:46 ItzKmaf Okay Thanks 2019-09-23 21:13:20 timmyRS Although, I don't see why you'd want that. Just send 0x7F. 2019-09-23 21:13:51 timmyRS If the skin has no second layer, nothing will be seen either way. If you send 0x00, and the skin looks incomplete, people might think your client is broken. 2019-09-23 21:18:48 <-- killme (~killmePI@185.9.253.124) a quitté (Ping timeout: 245 seconds) 2019-09-23 21:21:50 ItzKmaf Okay will do 2019-09-23 21:21:54 ItzKmaf Thanks again xD 2019-09-23 21:22:03 --> killme (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-09-23 22:37:39 <-- ItzKmaf (33098d74@116.141.9.51.dyn.plus.net) a quitté (Ping timeout: 260 seconds) 2019-09-23 22:47:48 --> ItzKmaf (33098d74@116.141.9.51.dyn.plus.net) a rejoint #mcdevs 2019-09-23 22:47:56 ItzKmaf Hey Im back i think i got hit off 2019-09-23 22:47:58 ItzKmaf Anyway 2019-09-23 22:48:05 ItzKmaf So its still not working 2019-09-23 22:48:25 ItzKmaf So i was wondering if anyone could attempt to connect to The Archon and tell me if their client works 2019-09-23 22:48:41 ItzKmaf I have tried 1.8.x and 1.14.4 2019-09-23 22:48:47 ItzKmaf With my Protocol 2019-09-23 22:55:11 ItzKmaf Im not Sure if its cause of cloudflare 2019-09-23 22:55:20 ItzKmaf I really do not have a clue at this point 2019-09-23 23:07:59 <-- ItzKmaf (33098d74@116.141.9.51.dyn.plus.net) a quitté (Ping timeout: 260 seconds) 2019-09-23 23:36:58 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-24 00:11:24 --> begin_end (admin@ho.by) a rejoint #mcdevs 2019-09-24 00:11:24 -- begin_end est maintenant connu sous le nom EW8GU 2019-09-24 00:27:35 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-09-24 00:29:27 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-24 02:24:53 --> mgrech_ (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-24 02:26:17 <-- mgrech__ (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 245 seconds) 2019-09-24 02:47:55 --> mgrech__ (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-24 02:51:08 <-- mgrech_ (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 268 seconds) 2019-09-24 03:09:21 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Ping timeout: 252 seconds) 2019-09-24 03:36:09 --> ItzKmaf (33098d74@116.141.9.51.dyn.plus.net) a rejoint #mcdevs 2019-09-24 03:36:54 ItzKmaf For some reason it works with 1.7.10 2019-09-24 04:05:14 <-- mgrech__ (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-09-24 04:51:18 <-- _123DMWM (~123DMWM@2601:18d:580:3870:bcf8:80d5:ff0c:18a6) a quitté (Ping timeout: 252 seconds) 2019-09-24 04:52:06 --> _123DMWM (~123DMWM@c-73-60-129-142.hsd1.ma.comcast.net) a rejoint #mcdevs 2019-09-24 04:58:28 <-- ItzKmaf (33098d74@116.141.9.51.dyn.plus.net) a quitté (Remote host closed the connection) 2019-09-24 05:45:43 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-jfczmbqgpwoqwkln) a rejoint #mcdevs 2019-09-24 06:45:05 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-09-24 06:45:38 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 240 seconds) 2019-09-24 06:45:39 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-09-24 07:10:00 timmyRS I know he's already gone, but I managed to get my client to connect using 1.14.4: https://lava.st/y17t9.png 2019-09-24 07:14:59 <-- levifig (~levi@hakr.io) a quitté (Ping timeout: 246 seconds) 2019-09-24 07:16:32 --> rheddry (~levi@hakr.io) a rejoint #mcdevs 2019-09-24 08:09:39 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-09-24 08:13:14 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-24 08:47:14 <-- rheddry (~levi@hakr.io) a quitté (Ping timeout: 240 seconds) 2019-09-24 08:49:06 --> levifig (~levi@hakr.io) a rejoint #mcdevs 2019-09-24 09:40:31 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-09-24 09:42:18 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-24 10:24:28 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-09-24 10:42:04 <-- electronicboy (~electroni@atlas.valaria.pw) a quitté (Remote host closed the connection) 2019-09-24 10:42:15 --> electroniccat (~electroni@atlas.valaria.pw) a rejoint #mcdevs 2019-09-24 10:42:57 <-- Mustek (~Mustek@steamdb/supporter/mustek) a quitté (Ping timeout: 245 seconds) 2019-09-24 10:44:12 <-- EW8GU (admin@ho.by) a quitté (Ping timeout: 245 seconds) 2019-09-24 10:44:16 --> Mustek (~Mustek@steamdb/supporter/mustek) a rejoint #mcdevs 2019-09-24 11:49:15 --> mgrech__ (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-24 12:46:09 --> EW8GU (admin@ho.by) a rejoint #mcdevs 2019-09-24 15:06:14 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-09-24 15:30:25 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-24 19:14:53 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-09-24 20:06:47 --> skyrising (~skyrising@ppp-62-216-195-99.dynamic.mnet-online.de) a rejoint #mcdevs 2019-09-24 20:38:49 barneygale It took me a while to realise this, but when dealing with chunk data, if you treat the whole packed long array as a bitstring and do a bitwise reverse of 64-bit chunks, then getting/setting values becomes trivial as they're never split up! 2019-09-24 20:40:33 barneygale The entry is in `bitstring[idx*bitsPerBlock:(idx+1)*bitsPerBlock`. The kinks are the perf cost on serialize/deserialize, and that you also need to reverse an entry's bits on set/get. 2019-09-24 20:40:52 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Quit: Textual IRC Client: www.textualapp.com) 2019-09-24 20:41:32 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-09-24 20:41:42 timmyRS I opted for a similar solution while remaining perfectly compatible with NBT: https://github.com/timmyRS/Phpcraft/blob/master/plugins/FirstPackets.php#L140-L149 2019-09-24 20:42:00 timmyRS Also, I hope you realize that altering your implementation based on the name of the variable is stupid. 2019-09-24 20:42:23 barneygale What do you mean? 2019-09-24 20:42:57 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-jfczmbqgpwoqwkln) a quitté (Quit: Connection closed for inactivity) 2019-09-24 20:43:30 timmyRS > I switched to the `bitstring` implementation if the take is named "BlockStates" 2019-09-24 20:44:06 barneygale No; I'm switching to `bitstring` for all cases of Tag_Long_Array and in my methods for packing/unpacking "Chunk Data" packets 2019-09-24 20:44:20 barneygale I'm not entirely convinced by the approach yet but I'm playing with it all the same. 2019-09-24 20:45:04 timmyRS Anyway, my implementation is basically a "bitstring" which I then split up into longs 2019-09-24 20:45:17 timmyRS I assume you can do something similar, although I'm not familiar with python. 2019-09-24 20:45:37 barneygale oof php 2019-09-24 20:53:05 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Quit: Textual IRC Client: www.textualapp.com) 2019-09-24 20:54:32 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-09-24 21:01:22 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Quit: Textual IRC Client: www.textualapp.com) 2019-09-24 21:02:20 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-09-24 21:08:40 +pokechu22 Yeah, that's a reasonable way to think of it -- the current implementation makes some sense if you consider the first bit to be 1, the second to be 2, the third to be 4, and the last to be 2^64 (which reduces the reversing) but that does create the weirdness when it's split between multiple longs since they don't match up when written out 2019-09-24 22:00:32 --> AwesomeTy79 (32cb2669@gateway/web/cgi-irc/kiwiirc.com/ip.50.203.38.105) a rejoint #mcdevs 2019-09-24 22:00:45 <-- AwesomeTy79 (32cb2669@gateway/web/cgi-irc/kiwiirc.com/ip.50.203.38.105) a quitté #mcdevs 2019-09-24 22:11:05 barneygale Implementation here if anyone's curious: https://github.com/barneygale/quarry/blob/master/quarry/types/chunk.py#L54 2019-09-24 22:11:27 barneygale I can't vouch for its performance (lol python) but iterating over all blocks seems nice and fast now. 2019-09-24 22:15:23 barneygale And I suppose I have the luxury of aiming for clarity of implementation rather than performance as nobody really uses quarry ;) 2019-09-24 22:35:13 rom1504 yeah that's a nice approach 2019-09-24 22:35:23 rom1504 I want to do this too for prismarine-chunk (js) 2019-09-24 22:38:50 +ammar2 Is prismarine-chunk a seperate lib? I also planned on having chunk parsing separated from the core networking library because of how fragile it is 2019-09-24 22:44:59 rom1504 yes 2019-09-24 22:45:19 rom1504 in node-minecraft-protocol we just expose the chunk as an array of bytes 2019-09-24 22:45:58 rom1504 then users (eg mineflayer) use prismarine-chunk to parse/serialize it 2019-09-24 22:46:54 rom1504 we have 1.8 -> 1.12 implementations in prismarine-chunk, but no 1.13 (nor 1.14) implementation yet, I'm planning to code a clean one using a bitbuffer approach at some point 2019-09-24 23:17:36 barneygale I wonder if reference-counting the palette makes any sense. I suppose it makes repacking the data a bit cheaper 2019-09-24 23:20:00 +pokechu22 Vanilla does it for air, but otherwise it's *probably* overkill; repacking is going to require going through everything anyways 2019-09-24 23:35:53 <-- Guest40966 (~WizardCM@103.93.232.1) a quitté (Remote host closed the connection) 2019-09-24 23:38:13 --> Wizard (~WizardCM@103.93.232.1) a rejoint #mcdevs 2019-09-24 23:38:36 -- Wizard est maintenant connu sous le nom Guest24629 2019-09-25 00:06:04 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-25 00:07:38 <-- mgrech__ (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 268 seconds) 2019-09-25 01:17:52 --> n24 (dce952d6@214.82.233.220.static.exetel.com.au) a rejoint #mcdevs 2019-09-25 01:24:11 <-- n24 (dce952d6@214.82.233.220.static.exetel.com.au) a quitté (Remote host closed the connection) 2019-09-25 02:12:41 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 276 seconds) 2019-09-25 02:15:26 --> logwet (79dca054@121.220.160.84) a rejoint #mcdevs 2019-09-25 02:15:57 logwet What sequence of packets does Bungeecord send to the player to prepare them for a server change 2019-09-25 02:21:15 +pokechu22 I think just respawn (twice if they're in the same dimension; there's a note about that on the page IIRC) 2019-09-25 02:25:01 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-09-25 02:26:42 --> ItzKmaf (33098d74@116.141.9.51.dyn.plus.net) a rejoint #mcdevs 2019-09-25 02:26:54 logwet Would: Respawn, Respawn, work? 2019-09-25 02:27:42 logwet And those forwarded packets include everything from encryption request to chunk data etc. 2019-09-25 02:28:14 +pokechu22 I think it would, yeah. You'd have to skip over a bit, since you can't send join game again (you might need to translate it into some other packets), but e.g. chunk data should be fine 2019-09-25 02:30:16 logwet Does the client wait for the player position and look to show the world to the player (after it receives a respawn packet) 2019-09-25 02:32:18 +pokechu22 I don't remember, exactly. I think it does wait for something, though, since you see the dirt screen for a bit 2019-09-25 02:32:48 +pokechu22 Probably the position 2019-09-25 02:35:10 logwet Thanks 2019-09-25 03:11:40 ItzKmaf I really am struggling with reading Chat in 1.8.x Protocol 47x 2019-09-25 03:12:30 ItzKmaf https://gyazo.com/d2b62bea21ca3df730b375925598d84b 2019-09-25 03:12:41 ItzKmaf That should print out a String of json 2019-09-25 03:12:44 ItzKmaf If i am correct 2019-09-25 03:12:53 ItzKmaf But instead i get this 2019-09-25 03:13:08 ItzKmaf https://gyazo.com/65024052eb00c944b5bd6477ab568bc9 2019-09-25 03:13:13 ItzKmaf Some chat is read correctly 2019-09-25 03:13:20 ItzKmaf Which is the "" 2019-09-25 03:13:25 ItzKmaf And most of it is under read 2019-09-25 03:13:30 ItzKmaf But i can't see why 2019-09-25 03:16:17 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-09-25 03:17:02 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-25 03:38:08 --> NickG365_ (~NickG365@2607:5300:60:6e29:472:6425:3733:0) a rejoint #mcdevs 2019-09-25 03:40:52 <-- NickG365 (~NickG365@2607:5300:60:6e29:472:6425:3733:0) a quitté (Ping timeout: 264 seconds) 2019-09-25 03:40:52 -- NickG365_ est maintenant connu sous le nom NickG365 2019-09-25 03:51:33 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Ping timeout: 265 seconds) 2019-09-25 04:08:46 stilbruch the custom servers on wiki.vg don't seem to have been updated in a while. Anyone know of any that are updated to 1.14.4? 2019-09-25 04:28:17 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 265 seconds) 2019-09-25 04:29:14 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Ping timeout: 240 seconds) 2019-09-25 06:36:11 <-- logwet (79dca054@121.220.160.84) a quitté (Remote host closed the connection) 2019-09-25 06:44:59 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-09-25 06:46:31 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 265 seconds) 2019-09-25 06:46:31 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-09-25 07:40:36 timmyRS stilbruch, https://github.com/timmyrs/Phpcraft works for 1.14.4, but the features are limited 2019-09-25 08:03:51 <-- ItzKmaf (33098d74@116.141.9.51.dyn.plus.net) a quitté (Ping timeout: 260 seconds) 2019-09-25 08:34:12 <-- wvffle (~wvffle@host-46-175-47-49.wtvk.pl) a quitté (Ping timeout: 245 seconds) 2019-09-25 09:34:12 <-- _123DMWM (~123DMWM@c-73-60-129-142.hsd1.ma.comcast.net) a quitté (Ping timeout: 245 seconds) 2019-09-25 09:34:18 --> _123DMWM (~123DMWM@c-73-60-129-142.hsd1.ma.comcast.net) a rejoint #mcdevs 2019-09-25 09:58:24 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Ping timeout: 265 seconds) 2019-09-25 10:00:46 --> kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a rejoint #mcdevs 2019-09-25 10:00:46 -- Mode #mcdevs [+v kev009] par ChanServ 2019-09-25 10:06:16 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Read error: Connection reset by peer) 2019-09-25 10:06:46 --> kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a rejoint #mcdevs 2019-09-25 10:06:46 -- Mode #mcdevs [+v kev009] par ChanServ 2019-09-25 11:17:15 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-09-25 12:44:22 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-cluxaeafdpsgspza) a rejoint #mcdevs 2019-09-25 13:03:23 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-25 13:11:54 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-25 13:26:57 <-- stilbruch (~stilbruch@2604:a880:cad:d0::c6f:d001) a quitté (Ping timeout: 250 seconds) 2019-09-25 15:12:56 --> stilbruch (~stilbruch@2604:a880:cad:d0::c6f:d001) a rejoint #mcdevs 2019-09-25 15:25:09 <-- Thinkofname (~Think@163.172.95.9) a quitté (Ping timeout: 252 seconds) 2019-09-25 15:30:40 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-09-25 15:32:35 --> Thinkofname (~Think@163.172.95.9) a rejoint #mcdevs 2019-09-25 15:32:35 -- Mode #mcdevs [+v Thinkofname] par ChanServ 2019-09-25 17:24:08 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-09-25 18:08:32 <-- Thinkofname (~Think@163.172.95.9) a quitté (Quit: Leaving) 2019-09-25 18:22:46 --> Thinkofname (~Think@163.172.95.9) a rejoint #mcdevs 2019-09-25 18:22:46 -- Mode #mcdevs [+v Thinkofname] par ChanServ 2019-09-25 19:31:49 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Remote host closed the connection) 2019-09-25 20:06:32 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-cluxaeafdpsgspza) a quitté (Quit: Connection closed for inactivity) 2019-09-25 22:06:48 --> ItzKmaf (3309097a@122.9.9.51.dyn.plus.net) a rejoint #mcdevs 2019-09-25 22:51:53 tktech There will be 10 minutes of downtown at 22 UTC on Friday for some quick updates to the database 2019-09-25 22:56:19 tktech MiniDigger: if you find that some of the packets listed in the FAQ are optional for minimum connection can you mark them as such, or create a different minimal section? I'm sure it would be useful to others. 2019-09-25 23:07:19 <-- ItzKmaf (3309097a@122.9.9.51.dyn.plus.net) a quitté (Ping timeout: 260 seconds) 2019-09-26 00:11:40 --> Dadido3 (~quassel@p200300D9DF265000C900C0E461E3EF7B.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-09-26 00:14:03 <-- Dadido3_ (~quassel@p200300D9DF265000C900C0E461E3EF7B.dip0.t-ipconnect.de) a quitté (Ping timeout: 245 seconds) 2019-09-26 02:13:16 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 240 seconds) 2019-09-26 02:23:00 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-09-26 04:54:12 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 245 seconds) 2019-09-26 07:14:20 MiniDigger The packets required to spawn in the player are marked as such 2019-09-26 07:14:58 MiniDigger (at least when I looked the other day, since way more packets have been added recently I am not sure anymore) 2019-09-26 07:16:15 MiniDigger Ok, it's kinda a mess, some are marked optional, some are marked required, some don't have any note 2019-09-26 07:16:35 MiniDigger Maybe I can clean that a bit up pater after work 2019-09-26 07:34:37 timmyRS it's pretty much just the teleport for the client to spawn, chunk data if you don't want them to spawn in the void 2019-09-26 08:03:26 MiniDigger Also login success 2019-09-26 08:04:49 timmyRS ...yeah. probably also join game. 2019-09-26 11:58:23 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-09-26 14:07:19 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-26 15:02:27 <-- niceplace (~nplace@185.128.25.132) a quitté (Quit: ZNC 1.7.3 - https://znc.in) 2019-09-26 15:02:44 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-26 15:19:58 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-09-26 17:22:55 <-- charims (~quassel@wsip-24-234-28-130.lv.lv.cox.net) a quitté (Ping timeout: 246 seconds) 2019-09-26 17:26:21 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Remote host closed the connection) 2019-09-26 17:33:04 --> redstonehelper (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-09-26 19:54:50 --> A4L (~A4L@93-103-235-126.static.t-2.net) a rejoint #mcdevs 2019-09-26 20:00:25 A4L Hello! I am using node-minecraft-protocol for creating a proxy server (client <-> proxy server <=> another server, where <=> is a permanent link, <-> is usually disconnected/client closed). I have a problem: When I login to the server with proxyServer and then connect to the proxyServer with a game client, all packets, except keepalives (handled by proxyServer) are rebroadcasted without modification. The 2019-09-26 20:00:27 A4L problem is that the game client does not get map data (chunks), because server sent them to the proxyServer before there was any game client. If I kiII myself (in game obviously) and respawn, server will send proxyServer new chunk data, which is relayed to the client. But before that, all that I see is black void. F3+A does not reload chunks, so I am asking You how is the "reload chunks" packet crafted, or 2019-09-26 20:00:29 A4L are chunks reloaded locally? 2019-09-26 20:09:19 <-- niceplace (~nplace@185.128.25.132) a quitté (Quit: ZNC 1.7.3 - https://znc.in) 2019-09-26 20:09:38 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-26 20:23:40 +ammar2 A4L: yeah, afaik there's no "reload chunks" packet or similar sent to the server 2019-09-26 20:23:44 +ammar2 it probably just reloads it locally 2019-09-26 20:23:54 +ammar2 your best bet is probably to cache them at the proxy server 2019-09-26 20:24:46 +ammar2 but then you might get out of sync if block place/remove packets are sent 2019-09-26 20:24:52 +ammar2 hmm 2019-09-26 20:53:53 A4L okay, thanks! 2019-09-26 22:58:15 <-- EW8GU (admin@ho.by) a quitté (Ping timeout: 264 seconds) 2019-09-26 23:25:09 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-26 23:25:57 --> EW8GU (admin@ho.by) a rejoint #mcdevs 2019-09-27 00:06:19 tktech ammar2: does it matter? Eventual consistency would be fine for a human rate of block updates no? 2019-09-27 00:59:17 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-09-27 01:46:44 +ammar2 tktech: hmm, it would become eventually consistent if the server resends the chunks, but I think if you're playing in like a "view distance x view distance" area, then the central chunks will never be resent 2019-09-27 01:47:12 +ammar2 I'm guessing the purpose of the project is for servers where you have to queue up to join so holding a spot is important 2019-09-27 03:28:22 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Ping timeout: 245 seconds) 2019-09-27 03:53:37 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Ping timeout: 240 seconds) 2019-09-27 05:38:27 <-- chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a quitté (Ping timeout: 264 seconds) 2019-09-27 05:43:49 --> chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a rejoint #mcdevs 2019-09-27 06:48:11 <-- Morrolan (morrolan@znc.morrolan.ch) a quitté (Quit: Goodbye) 2019-09-27 07:13:54 --> Morrolan (morrolan@znc.morrolan.ch) a rejoint #mcdevs 2019-09-27 07:44:54 --> VADemon_ (~VADemon@141.41.197.208) a rejoint #mcdevs 2019-09-27 07:45:59 <-- VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a quitté (Read error: Connection reset by peer) 2019-09-27 07:46:38 <-- VADemon_ (~VADemon@141.41.197.208) a quitté (Client Quit) 2019-09-27 07:56:15 <-- Byteflux (~byte@byteflux.net) a quitté (Quit: lax is dum lol) 2019-09-27 08:04:24 --> Byteflux (~byte@byteflux.net) a rejoint #mcdevs 2019-09-27 08:07:46 --> VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a rejoint #mcdevs 2019-09-27 09:59:50 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Remote host closed the connection) 2019-09-27 10:03:12 --> kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a rejoint #mcdevs 2019-09-27 10:03:12 -- Mode #mcdevs [+v kev009] par ChanServ 2019-09-27 12:20:42 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-09-27 14:08:31 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Read error: Connection reset by peer) 2019-09-27 14:09:26 --> kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a rejoint #mcdevs 2019-09-27 14:09:26 -- Mode #mcdevs [+v kev009] par ChanServ 2019-09-27 14:28:25 <-- Thinkofname (~Think@163.172.95.9) a quitté (Quit: Leaving) 2019-09-27 14:41:27 --> Thinkofname (~Think@163.172.95.9) a rejoint #mcdevs 2019-09-27 14:41:27 -- Mode #mcdevs [+v Thinkofname] par ChanServ 2019-09-27 15:11:11 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-27 15:33:04 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-09-27 16:53:02 Not-5e4d [McUpdates] Minecraft snapshot 19w39a has just been published to the launcher! 2019-09-27 16:53:10 Not-5e4d [McUpdates] Data generated by 19w39a: https://apimon.de/mcdata/19w39a/19w39a.zip 2019-09-27 16:53:16 Not-5e4d [minecraft-data] automatic-beyond-belief pushed 1 commit to master [+0/-0/±1] https://git.io/JeZsl 2019-09-27 16:53:18 Not-5e4d [minecraft-data] automatic-beyond-belief 679bd71 - Add 19w39a to common/protocolVersions.json 2019-09-27 16:54:54 Not-5e4d [Burger] New data now avaliable for 19w39a: 2019-09-27 16:54:55 Not-5e4d [Burger] Diff from 19w38b: https://pokechu22.github.io/Burger/diff_19w38b_19w39a.html (https://pokechu22.github.io/Burger/diff_19w38b_19w39a.json) 2019-09-27 16:54:57 Not-5e4d [Burger] Full data: https://pokechu22.github.io/Burger/19w39a.html (https://pokechu22.github.io/Burger/19w39a.json) 2019-09-27 17:00:03 Not-5e4d [McUpdates] An article about Minecraft Snapshot 19w39a was just published: https://www.minecraft.net/en-us/article/minecraft-snapshot-19w39a 2019-09-27 18:01:01 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Remote host closed the connection) 2019-09-27 18:37:20 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-27 19:13:55 <-- skyrising (~skyrising@ppp-62-216-195-99.dynamic.mnet-online.de) a quitté (Remote host closed the connection) 2019-09-27 19:14:13 --> skyrising (~skyrising@ppp-62-216-195-99.dynamic.mnet-online.de) a rejoint #mcdevs 2019-09-27 21:03:21 --> Kiip (5f61c333@095-097-195-051.static.chello.nl) a rejoint #mcdevs 2019-09-27 21:03:48 <-- Kiip (5f61c333@095-097-195-051.static.chello.nl) a quitté (Remote host closed the connection) 2019-09-27 22:56:00 --> Bamby (~Bamby@2a01cb0882c3f500b1da3a14b04e5001.ipv6.abo.wanadoo.fr) a rejoint #mcdevs 2019-09-28 00:53:30 <-- Bamby (~Bamby@2a01cb0882c3f500b1da3a14b04e5001.ipv6.abo.wanadoo.fr) a quitté (Read error: Connection reset by peer) 2019-09-28 02:11:14 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 240 seconds) 2019-09-28 02:18:37 <-- VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a quitté (Read error: Connection reset by peer) 2019-09-28 02:18:37 --> VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a rejoint #mcdevs 2019-09-28 02:20:56 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-09-28 03:25:16 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-09-28 06:40:17 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-09-28 06:41:42 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 245 seconds) 2019-09-28 06:41:42 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-09-28 07:17:53 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-09-28 10:03:16 <-- VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a quitté (Read error: Connection reset by peer) 2019-09-28 11:11:38 <-- EW8GU (admin@ho.by) a quitté (Ping timeout: 240 seconds) 2019-09-28 11:14:36 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 240 seconds) 2019-09-28 12:13:10 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-28 13:13:50 --> EW8GU (admin@ho.by) a rejoint #mcdevs 2019-09-28 13:52:14 --> redstonehelper (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-09-28 14:00:21 --> niceplaces (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-28 14:00:35 <-- niceplace (~nplace@185.128.25.132) a quitté (Ping timeout: 265 seconds) 2019-09-28 15:48:31 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 2019-09-28 16:20:02 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Read error: Connection reset by peer) 2019-09-28 17:01:57 <-- EW8GU (admin@ho.by) a quitté (Ping timeout: 240 seconds) 2019-09-28 19:59:46 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-28 20:18:10 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-28 23:21:59 <-- csnxs (sean@unaffiliated/plussean) a quitté (Ping timeout: 246 seconds) 2019-09-28 23:29:12 --> csnxs (sean@unaffiliated/plussean) a rejoint #mcdevs 2019-09-28 23:58:50 barneygale I mentioned a day or two ago that you can smooth out some of the maths for the tightly-packed chunk section arrays by doing some bitwise reversals. It's just occurred to be that the same is true for light arrays, except that the chunk size is 8 bits rather than 64 bits. Long story short I think I now have a general-purpose class that works for block data, light data and heightmap data in much the same way 2019-09-28 23:59:40 barneygale Serialization/deserialization is expensive, but gets/sets are fast 2019-09-29 00:01:52 +pokechu22 Is it really faster to reverse twice than to just split it (especially with light where it's always going to be in a single byte)? 2019-09-29 00:02:20 barneygale No, definitely slower in that case 2019-09-29 00:04:00 barneygale tbh it's probably slower than bitshifting/ORing in all cases anyway, but the implementation is a bit tidier and the mental model is a little easier too 2019-09-29 00:04:41 rom1504 would be so much easier if the bits were not reversed in the longs... 2019-09-29 00:57:51 --> pvpctutorials (~skyrising@185.229.59.179) a rejoint #mcdevs 2019-09-29 00:59:57 <-- skyrising (~skyrising@ppp-62-216-195-99.dynamic.mnet-online.de) a quitté (Ping timeout: 240 seconds) 2019-09-29 01:38:45 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Remote host closed the connection) 2019-09-29 01:55:53 <-- A4L (~A4L@93-103-235-126.static.t-2.net) a quitté (Quit: WeeChat 2.3) 2019-09-29 02:09:27 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 265 seconds) 2019-09-29 02:14:43 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-09-29 02:26:44 --> wvffle (~wvffle@host-46-175-47-49.wtvk.pl) a rejoint #mcdevs 2019-09-29 03:57:57 --> skyrising (~skyrising@ppp-62-216-195-99.dynamic.mnet-online.de) a rejoint #mcdevs 2019-09-29 03:59:14 <-- pvpctutorials (~skyrising@185.229.59.179) a quitté (Ping timeout: 240 seconds) 2019-09-29 04:39:29 <-- skyrising (~skyrising@ppp-62-216-195-99.dynamic.mnet-online.de) a quitté (Remote host closed the connection) 2019-09-29 05:08:48 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-09-29 06:57:17 <-- niceplaces (~nplace@185.128.25.132) a quitté (Quit: ZNC 1.7.3 - https://znc.in) 2019-09-29 06:57:35 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-29 09:41:07 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Remote host closed the connection) 2019-09-29 09:44:00 --> kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a rejoint #mcdevs 2019-09-29 09:44:00 -- Mode #mcdevs [+v kev009] par ChanServ 2019-09-29 12:33:39 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-09-29 12:35:47 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-29 12:38:52 <-- niceplace (~nplace@185.128.25.132) a quitté (Excess Flood) 2019-09-29 12:39:13 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-29 13:21:28 --> VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a rejoint #mcdevs 2019-09-29 13:35:47 x10A94 Hey, what's the heightmap NBT data for? Can I just send nothing, or will the client refuse to load the chunk without it? 2019-09-29 13:37:17 timmyRS You need the MOTION_BLOCKING long array 2019-09-29 13:37:34 x10A94 ya, but what is it used for 2019-09-29 13:37:40 timmyRS Otherwise the client will ignore it 2019-09-29 13:37:55 timmyRS It contains the highest block at each X-Z coordinate 2019-09-29 13:38:08 x10A94 Is that necessary for the renderer, or what? 2019-09-29 13:38:30 timmyRS I don't know what Minecraft uses it for. I assume it's for lighting purposes. 2019-09-29 13:38:42 x10A94 man lol 2019-09-29 13:39:02 x10A94 I don't know why, but with each version lighting gets worse and worse in terms of performance 2019-09-29 13:40:15 timmyRS It's easy to write the 256 entries if you just have a "bitstring" that you write the Z coordinates to and then split it into 36 longs. 2019-09-29 13:40:44 x10A94 The server isn't really aware of what blocks the world contains 2019-09-29 13:40:55 timmyRS Why not? 2019-09-29 13:41:00 x10A94 Not necessary 2019-09-29 13:41:04 x10A94 The world is static 2019-09-29 13:41:49 timmyRS Then just extract the "MOTION_BLOCKING" data from the static world and write it to a static file so you can query that... 2019-09-29 13:41:58 x10A94 well 2019-09-29 13:42:10 x10A94 I just grab the packets via a proxy 2019-09-29 13:42:23 x10A94 I was mostly interested in whether I can omit it 2019-09-29 13:42:38 x10A94 just to cut down further on the network 2019-09-29 13:42:45 x10A94 maybe I should also pre-compress it 2019-09-29 13:43:40 timmyRS You're optimizing at the wrong point. The real performance issue in Minecraft is the Notchian client. ;) 2019-09-29 13:43:54 x10A94 wheeze 2019-09-29 13:44:42 x10A94 I got that much already when I sent the client ~200 block changes per second and it dropped down to 5fps 2019-09-29 13:45:45 x10A94 I'm definitely going to recommend that people install optifine if they wanna experience animated structures without the gigantic amounts of lag 2019-09-29 13:46:02 x10A94 also, why is it that there are bulk block changes but not bulk entity movements? mojang wyd 2019-09-29 13:46:11 timmyRS With 1.14, even particles drop the frame rate significantly. Your can easily crash/lag the client by accident... 2019-09-29 13:47:06 x10A94 I've never crashed the client per se, but sending it 1M packets per second definitely freezes it 2019-09-29 13:47:54 x10A94 https://i.selic.re/hW82EyRc.png < fun times 2019-09-29 13:48:21 timmyRS You can fix the "null" server by sending a minecraft:brand plugin message anytime after join game 2019-09-29 13:48:39 x10A94 yeah, I just don't have plugin messages implemented yet because I'm focusing on more important things 2019-09-29 13:48:45 x10A94 like players 2019-09-29 13:50:10 x10A94 also falling sand isn't interpolated when you teleport it and it sucks because I want to have more control over flying blocks 2019-09-29 13:50:29 x10A94 I guess I could try overwriting velocity but that can desync easily 2019-09-29 14:08:49 x10A94 Oh, also: can I assume that the NBT data sent by the vanilla server is constant size? 2019-09-29 14:09:08 x10A94 I don't wanna parse NBT because it's extremely inconvenient for me to do so 2019-09-29 14:13:59 timmyRS errrg, well, the vanilla server also sends a WORLD_SURFACE long array, which is not required, so some custom servers might not send it. But other than that, the NBT should be constant size. 2019-09-29 14:15:46 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-09-29 14:17:33 x10A94 okay nice good 2019-09-29 14:17:43 x10A94 I only care about the vanilla server 2019-09-29 15:39:44 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-29 15:58:37 x10A94 uhhh how do item IDs in inv slots work? 2019-09-29 15:59:26 timmyRS What exactly are you confused about? 2019-09-29 16:00:30 x10A94 I tried using the IDs in the minecraft:block registry and it didn't work at all 2019-09-29 16:00:47 x10A94 and the blocks.json IDs don't work either 2019-09-29 16:01:38 x10A94 oh wait 2019-09-29 16:01:49 x10A94 there's a minecraft:item registry which has the same entries, but.. different IDs 2019-09-29 16:01:51 x10A94 nice 2019-09-29 16:02:08 timmyRS ^^ 2019-09-29 16:02:11 x10A94 are any of these even supposed to be sent over the network? 2019-09-29 16:02:20 x10A94 like, the later ones 2019-09-29 16:02:34 timmyRS the items? 2019-09-29 16:02:59 x10A94 nah, like the structure stuff and the biome stuff 2019-09-29 16:03:09 x10A94 e.g. structure_piece 2019-09-29 16:04:00 x10A94 wait 2019-09-29 16:04:04 x10A94 it still doesn't work 2019-09-29 16:04:10 x10A94 it seems to be entirely random 2019-09-29 16:04:51 timmyRS They're never sent over the network I don't think, but they're still enumerated, I guess 2019-09-29 16:05:10 x10A94 item id 465 gives granite, something in the 8k range gives.. leaves? 2019-09-29 16:05:58 timmyRS these ids change per version 2019-09-29 16:06:09 timmyRS well, at least, theoretically they could 2019-09-29 16:06:21 x10A94 I'm using the 1.14.4 generated values 2019-09-29 16:06:56 x10A94 46500 is.. dark prismarine? 2019-09-29 16:07:40 x10A94 wait 2019-09-29 16:07:46 x10A94 am I supposed to multiply by 128 2019-09-29 16:10:15 timmyRS Yeah, I think some bit shifting is in fact going on there 2019-09-29 16:11:13 x10A94 that was it 2019-09-29 16:11:18 x10A94 aight I'm boutta head out 2019-09-29 16:11:30 x10A94 also someone should add that to the wiki to prevent future headdesks 2019-09-29 16:13:35 barneygale I don't think there's any bitshifting involved since 1.13 2019-09-29 16:15:40 x10A94 well, lo and behold 2019-09-29 16:17:21 timmyRS Well, looking at my code, there is indeed no more bitshifting in 1.13, but that is weird. Are you sure you have https://wiki.vg/Slot_Data implemented correctly? 2019-09-29 16:19:33 x10A94 oh fuck 2019-09-29 16:19:39 x10A94 how am I this blind 2019-09-29 16:19:44 x10A94 okay that explains it 2019-09-29 16:20:28 x10A94 right, I'm supposed to use an Option because it adds a boolean implicitly, I just never documented that 2019-09-29 16:20:28 timmyRS What did you do? 2019-09-29 16:20:46 timmyRS I see 2019-09-29 16:21:40 x10A94 I feel like I need to rewrite my (de)serializer because it has no support for multiple ways of deserializing the same thing 2019-09-29 16:40:01 x10A94 Apparently minecraft ignores teleport packets that don't contain any position changes entirely, even if the look angles change 2019-09-29 16:41:02 timmyRS That sounds wrong 2019-09-29 16:42:02 timmyRS What if you set X, Y, & Z to 0 and use the flags to mark them as relative? 2019-09-29 16:43:03 x10A94 entity teleport, not player teleport 2019-09-29 17:27:59 <-- csnxs (sean@unaffiliated/plussean) a quitté (Quit: I was wrong. It creeps up back; through coloured glass.) 2019-09-29 17:47:59 --> csnxs (sean@unaffiliated/plussean) a rejoint #mcdevs 2019-09-29 19:38:45 <-- Proximyst (~Proximyst@116.203.198.234) a quitté (Quit: Robbing a bank) 2019-09-29 19:40:08 --> Proximyst (~Proximyst@148.251.50.76) a rejoint #mcdevs 2019-09-29 20:23:14 <-- alexge50 (~alexge50@unaffiliated/alexge50) a quitté (Ping timeout: 240 seconds) 2019-09-29 20:26:57 --> alexge50 (~alexge50@unaffiliated/alexge50) a rejoint #mcdevs 2019-09-29 20:46:14 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Remote host closed the connection) 2019-09-29 20:55:44 MiniDigger has somebody implemented the declare commands packet as a server here? 2019-09-29 20:55:50 MiniDigger I fail to send the arguments 2019-09-29 20:57:50 timmyRS I have it implemented but it's spread across several classes 2019-09-29 20:58:53 timmyRS https://github.com/timmyRS/Phpcraft/blob/master/plugins/TabCompletion.php https://github.com/timmyRS/Phpcraft/tree/master/src/Packet/DeclareCommands 2019-09-29 20:59:56 MiniDigger ill take a look 2019-09-29 21:00:09 MiniDigger I think its failing for ArgumentCommandNodes 2019-09-29 21:00:38 MiniDigger oh wait 2019-09-29 21:00:54 timmyRS The relevant code for sending it is actually in "Node" 2019-09-29 21:01:21 MiniDigger I think its because I don't send properties for arguments 2019-09-29 21:02:00 MiniDigger since for string its actually not optional 2019-09-29 21:03:06 MiniDigger https://i.imgur.com/78tTRAx.png 2019-09-29 21:03:08 MiniDigger yes, that was it... 2019-09-29 21:03:18 MiniDigger uff 2019-09-29 21:04:04 MiniDigger thanks, looking at your argument provider make me realize that 2019-09-29 21:04:57 timmyRS Yeah, my arguments are a bit weird, but glad you could work with it ^^ 2019-09-29 21:05:34 MiniDigger now I need a good way to integrate the original brigadier providers (since I actually depend on the lib) into my code nicely, so that I get access to the properties. 2019-09-29 22:03:08 <-- csnxs (sean@unaffiliated/plussean) a quitté (Quit: I was wrong. It creeps up back; through coloured glass.) 2019-09-29 22:08:10 --> csnxs (sean@unaffiliated/plussean) a rejoint #mcdevs 2019-09-29 23:26:45 barneygale I think I've finished tweaking my chunk data implementation. It's here for the curious: https://github.com/barneygale/quarry/blob/master/quarry/types/chunk.py 2019-09-29 23:28:06 kashike ah yes, python 2019-09-29 23:28:09 kashike aka indentation hell 2019-09-29 23:30:05 barneygale you don't indent your code? 2019-09-29 23:30:36 kashike I do, but I have {} around it :P 2019-09-29 23:30:49 kashike (I like python, but the magic of indentation bothers me) 2019-09-29 23:31:23 barneygale if you indent your code anyway its no additional burden really 2019-09-29 23:33:10 barneygale there's definitely some objectionable magic in python though 2019-09-29 23:33:33 barneygale e.g. `pathlib` 2019-09-30 00:01:49 +ammar2 aww, I like pathlib 2019-09-30 00:01:52 +ammar2 it's a neat abstraction 2019-09-30 00:02:18 +ammar2 and being able to do `Path("abcd") / "xyz" / "file.txt"` is so magically intuitive 2019-09-30 00:03:02 barneygale That I'm fine with, but the implementation does all sorts of `__new__` wizardry to automatically choose an appropriate `Path` implementation 2019-09-30 00:03:22 barneygale And if you want to extend anything in pathlib you're in a world of pain ;_; 2019-09-30 00:03:41 +ammar2 yeah, but why would you want to extend it 2019-09-30 00:03:59 +ammar2 you wouldn't go extending level directory APIs in any other language 2019-09-30 00:04:09 barneygale e.g. https://github.com/Parallels/artifactory 2019-09-30 00:04:43 barneygale Artifactory is just a file store served over HTTP (some bastardisation of WebDAV I think) 2019-09-30 00:05:36 barneygale I wrote a similar thing for enumerating paths on a remote version control server 2019-09-30 00:09:22 barneygale If you're writing only for Linux, FUSE is probably a better idea. 2019-09-30 02:04:08 <-- RoboMWM (~RoboMWM@paper.robomwm.com) a quitté (Read error: Connection reset by peer) 2019-09-30 03:17:56 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Ping timeout: 265 seconds) 2019-09-30 04:10:23 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 276 seconds) 2019-09-30 05:11:31 <-- wvffle (~wvffle@host-46-175-47-49.wtvk.pl) a quitté (Ping timeout: 265 seconds) 2019-09-30 05:13:36 --> wvffle (~wvffle@host-46-175-47-49.wtvk.pl) a rejoint #mcdevs 2019-09-30 06:14:56 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-09-30 06:16:17 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 265 seconds) 2019-09-30 06:16:17 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-09-30 10:52:10 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-bgdwbolwhvhwjnhd) a rejoint #mcdevs 2019-09-30 12:13:46 --> Dadido3_ (~quassel@p200300D9DF265000C900C0E461E3EF7B.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-09-30 12:15:43 <-- Dadido3 (~quassel@p200300D9DF265000C900C0E461E3EF7B.dip0.t-ipconnect.de) a quitté (Ping timeout: 245 seconds) 2019-09-30 12:18:24 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-09-30 12:55:03 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-09-30 13:08:50 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-bgdwbolwhvhwjnhd) a quitté (Quit: Connection closed for inactivity) 2019-09-30 14:22:27 <-- niceplace (~nplace@185.128.25.132) a quitté (Quit: ZNC 1.7.3 - https://znc.in) 2019-09-30 14:27:21 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-09-30 15:43:47 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-lvdwdbbjtjguigau) a rejoint #mcdevs 2019-09-30 17:00:37 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Remote host closed the connection) 2019-09-30 18:04:18 --> PolarizedIons506 (polarizedi@169-0-101-241.ip.afrihost.co.za) a rejoint #mcdevs 2019-09-30 18:06:19 <-- PolarizedIons506 (polarizedi@169-0-101-241.ip.afrihost.co.za) a quitté (Client Quit) 2019-09-30 18:06:53 --> PolarizedIons506 (polarizedi@169-0-101-241.ip.afrihost.co.za) a rejoint #mcdevs 2019-09-30 18:58:10 <-- PolarizedIons506 (polarizedi@169-0-101-241.ip.afrihost.co.za) a quitté (Changing host) 2019-09-30 18:58:10 --> PolarizedIons506 (polarizedi@unaffiliated/polarizedions) a rejoint #mcdevs 2019-09-30 18:58:19 -- PolarizedIons506 est maintenant connu sous le nom PolarizedIons 2019-09-30 20:13:32 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-lvdwdbbjtjguigau) a quitté (Quit: Connection closed for inactivity) 2019-09-30 22:17:56 --> ItzKmaf (3309097a@122.9.9.51.dyn.plus.net) a rejoint #mcdevs 2019-09-30 22:21:14 ItzKmaf Hey So i narrowed down the chat packet issue down to my compressed packet handling. 2019-09-30 22:21:58 ItzKmaf Chat packets that do not pass over the encryption threshold are read correctly, Chat packets that pass the encryption threshold are read correctly 2019-09-30 22:22:19 ItzKmaf *are not read correctly 2019-09-30 22:23:22 ItzKmaf https://pastebin.com/8exHKSk8 2019-09-30 22:24:17 ItzKmaf That code outputs https://pastebin.com/kBBZ38T9 2019-09-30 22:25:29 ItzKmaf All of the numbers seem to be correct 2019-09-30 22:25:36 ItzKmaf So i don't see why it is not working 2019-09-30 22:25:51 ItzKmaf Packet Length: 147 2019-09-30 23:02:07 ItzKmaf If anyone could point me in the right direction that would be brilliant 2019-09-30 23:02:32 ItzKmaf Im gonna log off to go to bed but i can check chat logs if anyone does reply 2019-09-30 23:02:36 <-- ItzKmaf (3309097a@122.9.9.51.dyn.plus.net) a quitté (Remote host closed the connection) 2019-09-30 23:40:56 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-uplbbslryizmazrp) a rejoint #mcdevs 2019-10-01 01:11:15 +pokechu22 That code looks odd; it's missing the case for `dataIDLength == 0` for one (but it sounds like that's not the error case) 2019-10-01 01:14:42 +pokechu22 I'm not sure what you're doing with `handlePacket(data, packetID, in, dataLength)` -- `data` hasn't been initialized yet so it's just an array of 0s. You could do `in.readFully(data)`, but in that case, why do you have `in` as a parameter to it? It feels like you only need one or the other 2019-10-01 02:10:30 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-uplbbslryizmazrp) a quitté (Quit: Connection closed for inactivity) 2019-10-01 02:11:11 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 276 seconds) 2019-10-01 02:19:09 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-01 02:29:51 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-aiyyojmymizsqjqn) a rejoint #mcdevs 2019-10-01 04:18:02 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-01 07:05:29 --> RoboMWM (~RoboMWM@tf.robomwm.com) a rejoint #mcdevs 2019-10-01 08:31:43 <-- VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a quitté (Quit: left4dead) 2019-10-01 09:08:44 --> thekinrar (~thekinrar@cpc115984-dals23-2-0-cust217.20-2.cable.virginm.net) a rejoint #mcdevs 2019-10-01 11:11:53 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-01 11:17:38 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-01 12:13:08 --> VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a rejoint #mcdevs 2019-10-01 13:42:39 <-- Dadido3_ (~quassel@p200300D9DF265000C900C0E461E3EF7B.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-10-01 13:43:21 --> Dadido3 (~quassel@p200300D9DF380F001DFDEC4DF61CE95F.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-10-01 14:55:13 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-01 14:57:03 <-- someone_stole_my (~mrkirby15@mrkirby153.com) a quitté (Quit: ZNC - http://znc.in) 2019-10-01 14:57:13 --> mrkirby153 (~mrkirby15@mrkirby153.com) a rejoint #mcdevs 2019-10-01 15:54:56 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-rkfcifdvhjhqkqta) a rejoint #mcdevs 2019-10-01 16:19:30 <-- balrog (~balrog@unaffiliated/balrog) a quitté (Quit: Bye) 2019-10-01 16:25:01 --> balrog (~balrog@unaffiliated/balrog) a rejoint #mcdevs 2019-10-01 18:06:57 --> Nitwel (5c756990@92.117.105.144) a rejoint #mcdevs 2019-10-01 18:17:33 Nitwel Hello everybody, I'm trying to learn how the chunkData packet is structured (especialy the data section) but because I'm very new to this sort of programming, I'm not understanding it completly. I cant figure out what the meaning and use of these Palettes are and how they function. And yes, I've read the docs first ^^. Hope somebody can explain it 2019-10-01 18:17:33 Nitwel in a more simple way, and thank you for your time. :] 2019-10-01 18:28:24 timmyRS Which version and what exactly do you not understand? 2019-10-01 18:36:45 Nitwel Ah yes, version 1.14.4 and this section here: https://imgur.com/G3wsTAM 2019-10-01 18:39:33 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-aiyyojmymizsqjqn) a quitté (Quit: Connection closed for inactivity) 2019-10-01 18:40:22 Nitwel And are there any usefull tools to work with chunks when the bitsPerBlock is differend than 4 or 8? 2019-10-01 18:41:51 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-rkfcifdvhjhqkqta) a quitté (Quit: Connection closed for inactivity) 2019-10-01 18:51:18 timmyRS That's the palette definition. So, 4 bits per block, 2 blocks in the palette and then the blockstate IDs. Here's some example could that would write this over the network: https://github.com/timmyRS/Phpcraft/blob/master/plugins/FirstPackets.php#L155-L166 2019-10-01 18:52:33 <-- deltab (~deltab@95.154.230.49) a quitté (Ping timeout: 265 seconds) 2019-10-01 18:53:30 --> ItzKmaf (3309097a@122.9.9.51.dyn.plus.net) a rejoint #mcdevs 2019-10-01 18:56:42 ItzKmaf pokechu22 THe case for == 0 was below. I didn't include it because that code worked fine. 2019-10-01 18:57:14 ItzKmaf but yeah... I kinda forgot to Actually read the DataStream into data 2019-10-01 18:57:18 ItzKmaf So thanks so much 2019-10-01 18:57:57 ItzKmaf Im testing it right now to see if that fixed it. 2019-10-01 19:00:11 ItzKmaf It works pokechu22. Thank you so much i am a massive retard for not spotting that 2019-10-01 19:02:11 --> deltab (~deltab@95.154.230.49) a rejoint #mcdevs 2019-10-01 19:04:27 Nitwel timmyRS Ah, forgot to mark it but knew what the 3 Byte meant. And whats the use/meaning of the palette; what is meant by blockstateIDs? 2019-10-01 19:06:05 timmyRS Well, for example grass[snowy=true] has ID 8 in 1.14 but grass[snowy=false] has ID 9, and that blockstate ID is added to the palette and the index in the palette is used in the chunk data. 2019-10-01 19:11:11 Nitwel Okay, and how do I know how long this Palette will be / are there docs for all the possible blockstatesIDs? 2019-10-01 19:14:14 timmyRS You can use the https://wiki.vg/Data_Generators to generate this list for you: https://apimon.de/mcdata/1.14.4/blocks.json 2019-10-01 19:15:22 timmyRS The length of the palette is defined by the first varint, but you know, varints can vary in byte size. 2019-10-01 19:28:46 Nitwel So does the palette contain all the data for Blocks? Because I cant figure out what "02 00 01 80 02"(Hex) means then and the Blocks in the chunk start at column 08. 2019-10-01 19:30:51 timmyRS 80 02 would have to be a varint, but it seems odd for there to be that extra null byte 2019-10-01 19:36:17 Nitwel https://imgur.com/gallery/SCspDJT Here you can see the full chunk. There's not much more except for another stone_block in the chunkSection above 2019-10-01 19:51:43 timmyRS "Zoinks! You've taken a wrong turn." 2019-10-01 19:53:51 Nitwel Upsie. Its now visible. 2019-10-01 19:55:48 timmyRS Still the same error 2019-10-01 19:59:23 Nitwel https://drive.google.com/file/d/19WMLQmJvGkkgbqQErYqcqybVMYBNNVyd/view?usp=sharing 2019-10-01 20:05:20 ItzKmaf / =============================== 2019-10-01 20:05:54 Nitwel Hmm? 2019-10-01 20:06:34 ItzKmaf Sorry. Im misunderstanding exactly how we are meant to read that as Y_ROT and Y could be set 2019-10-01 20:06:51 ItzKmaf And that could also be read as X_ROT showing up as set instead 2019-10-01 20:07:08 ItzKmaf or do i misunderstand how to read the bitfield 2019-10-01 20:46:54 Nitwel timmyRS is the 2nd image link working? Also, am I right that BitsPerBlock means if it would be 4, a stone would be saved as "0001" but if it is 5 or 7, it would be "00001" or "0000001"? 2019-10-01 20:49:57 timmyRS No, the palette is in varints 2019-10-01 20:50:08 timmyRS But then in the chunk data it's the palette index in bitsperblock bits 2019-10-01 20:55:51 Nitwel Im getting really confused now. X) 2019-10-01 21:00:46 timmyRS Could you give me that .chunk file? Also, what exactly is it, the packet after the ID? 2019-10-01 21:02:37 Nitwel Well, its only the chunk-data section: https://drive.google.com/file/d/1GKwS_uK56I12CXsNLZG3rgKv-F9dnYiy/view?usp=sharing 2019-10-01 21:07:13 timmyRS Which chunk data section? 2019-10-01 21:09:02 Nitwel Didn't meant one of the 16 chunk sections, I meant the data section of the packet* 2019-10-01 21:11:20 timmyRS Alright, I'll try to parse it soon-ish-ly 2019-10-01 21:35:15 Nitwel Ahhh, now I understand VarInts... thought they where much simpler but they aren't at at. XD And bityPerBlock does refer to how many bytes are used for each block of the VarInt and not how many bytes are used to save a block. 2019-10-01 21:36:20 Nitwel ...to save a minecraft block* 2019-10-01 21:43:43 timmyRS I unforunately am able to work with your chunk file. Is it compressed or something like that? 2019-10-01 21:43:47 timmyRS unable* 2019-10-01 21:50:35 timmyRS This also generally seems wrong, are you sure this was sent by a 1.14.4 server? 2019-10-01 21:50:57 Nitwel It could be that the file isnt formattet correctly because I just printed it out for debugging. 2019-10-01 21:53:04 timmyRS Like, this is supposed to be the chunk data packet after it's length and ID have been sent? 2019-10-01 21:55:00 Nitwel Ähem, what? What length and Id and of what? 2019-10-01 21:55:19 timmyRS Of the packet 2019-10-01 21:58:25 Nitwel Give me a minute, maybe I'm just using the wrong ProtocolLib version. 2019-10-01 21:58:47 timmyRS Does protocollib not handle the chunk data packet? 2019-10-01 21:59:41 Nitwel Yep, and I'm just trying to manipulate it before sending it to the client. 2019-10-01 22:01:22 Nitwel Im using protocolLib 4.4.0 and I think I have to use a newer version. 2019-10-01 22:01:26 timmyRS So, you're writing a proxy? 2019-10-01 22:01:49 Nitwel Kinda, yea 2019-10-01 22:04:02 timmyRS Well, what do you wanna do to the chunk? 2019-10-01 22:04:30 Nitwel And the problem is that when loging in, no chunks are send to the client (or wrong formatted ones) and I'm trying to figure out why this is so because its code of a Dev who isn't interested in updating the plugin to 1.14 anymore. 2019-10-01 22:05:18 Nitwel Just change some specific block for sertain players (similar to an antiXray plugin) 2019-10-01 22:05:30 Nitwel blocks* 2019-10-01 22:08:20 timmyRS Your proxy would need serious protocol awareness to get that done. 2019-10-01 22:08:59 Nitwel protocol awareness? 2019-10-01 22:10:59 timmyRS Well, there's transparent proxies that literally just forward stuff, proxies that sorta know what's happening and maybe change stuff, but you esentially want a second server on top of the existing server. 2019-10-01 22:14:20 Nitwel Why a second server? Its just a standard spigot plugin which runs on the server, catches all packages with a eventListener, modifies them a bit and nothing more. Like any other eventListener for other stuff like breaking a block and then changing the Material type or such inside the eventListener. 2019-10-01 22:14:54 timmyRS I thought you're using protocollib to make an anti-xray? 2019-10-01 22:16:09 Nitwel not exactly an anti-xray, but similar. 2019-10-01 22:16:45 timmyRS Just make a spigot plugin instead writing a proxy 2019-10-01 22:17:17 Nitwel It is a spigot Plugin! XD 2019-10-01 22:17:32 timmyRS Right, so what exactly is the issue? 2019-10-01 22:19:35 Nitwel that I need to update the plugin to 1.14 from 1.10.2 and I'm trying to learn how it functions to be able to fix it. Thats why I'm trying to learn how a ChunkPackage is structured so I can debug it. 2019-10-01 22:52:08 Nitwel Btw, is there a propper way of seeing what has changed in the ChunkProtocoll of 1.14.4 compared to 1.10.2? 2019-10-01 23:03:22 timmyRS https://wiki.vg/index.php?title=Pre-release_protocol&oldid=8249 https://wiki.vg/index.php?title=Pre-release_protocol&direction=next&oldid=12924 https://wiki.vg/index.php?title=Pre-release_protocol&direction=next&oldid=14264 https://wiki.vg/index.php?title=Pre-release_protocol&oldid=14870 2019-10-01 23:29:56 <-- ItzKmaf (3309097a@122.9.9.51.dyn.plus.net) a quitté (Remote host closed the connection) 2019-10-01 23:46:51 <-- Nitwel (5c756990@92.117.105.144) a quitté (Ping timeout: 260 seconds) 2019-10-01 23:52:47 --> Nitwel (5c757e8d@92.117.126.141) a rejoint #mcdevs 2019-10-02 00:00:15 -- e est maintenant connu sous le nom deadk 2019-10-02 01:00:01 <-- Nitwel (5c757e8d@92.117.126.141) a quitté (Remote host closed the connection) 2019-10-02 01:33:21 peterix Enjoy this weird piece of arcane knowledge: https://wiki.vg/Mojang_API#Security_question-answer_flow 2019-10-02 01:33:49 peterix I had to reverse engineer it, because there was no documentation for it. 2019-10-02 01:34:12 peterix Might as well share that, I think :) 2019-10-02 02:15:56 +ammar2 peterix: thank you! that looks great 2019-10-02 04:36:36 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-02 06:23:30 <-- ddevault (znc@sourcehut/staff/ddevault) a quitté (Quit: Why do I even put this quit message in if I never quit) 2019-10-02 06:25:08 --> ddevault (znc@sourcehut/staff/ddevault) a rejoint #mcdevs 2019-10-02 06:25:08 -- Mode #mcdevs [+v ddevault] par ChanServ 2019-10-02 06:38:22 <-- ddevault (znc@sourcehut/staff/ddevault) a quitté (Ping timeout: 245 seconds) 2019-10-02 06:38:38 --> bigfoot548 (bigfoot@unaffiliated/bigfoot547) a rejoint #mcdevs 2019-10-02 06:38:47 <-- deltab (~deltab@95.154.230.49) a quitté (Ping timeout: 245 seconds) 2019-10-02 06:38:47 <-- bigfoot547 (bigfoot@unaffiliated/bigfoot547) a quitté (Ping timeout: 245 seconds) 2019-10-02 06:40:34 --> deltab (~deltab@95.154.230.49) a rejoint #mcdevs 2019-10-02 06:40:42 -- bigfoot548 est maintenant connu sous le nom bigfoot547 2019-10-02 06:41:14 <-- chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a quitté (Ping timeout: 240 seconds) 2019-10-02 06:42:08 --> ddevault (znc@sourcehut/staff/ddevault) a rejoint #mcdevs 2019-10-02 06:42:08 -- Mode #mcdevs [+v ddevault] par ChanServ 2019-10-02 06:43:37 --> chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a rejoint #mcdevs 2019-10-02 10:34:03 <-- Morrolan (morrolan@znc.morrolan.ch) a quitté (Quit: Goodbye) 2019-10-02 10:35:05 --> Morrolan (morrolan@znc.morrolan.ch) a rejoint #mcdevs 2019-10-02 10:50:45 <-- Morrolan (morrolan@znc.morrolan.ch) a quitté (Quit: Goodbye) 2019-10-02 10:51:02 --> Morrolan (morrolan@znc.morrolan.ch) a rejoint #mcdevs 2019-10-02 12:52:43 <-- Thinkofname (~Think@163.172.95.9) a quitté (Quit: Leaving) 2019-10-02 12:58:05 --> Thinkofname (~Think@163.172.95.9) a rejoint #mcdevs 2019-10-02 12:58:05 -- Mode #mcdevs [+v Thinkofname] par ChanServ 2019-10-02 13:07:39 <-- dan9er[m] (dan9ermatr@gateway/shell/matrix.org/x-bnhrizmrrjfavbsl) a quitté (Remote host closed the connection) 2019-10-02 13:07:46 <-- M-Processus42 (processus4@gateway/shell/matrix.org/x-mcydjdgjvfjypjjy) a quitté (Write error: Broken pipe) 2019-10-02 13:07:46 <-- yangm (yanyetanot@gateway/shell/matrix.org/x-krymizmgbzxzbnaj) a quitté (Write error: Connection reset by peer) 2019-10-02 13:09:15 <-- Krenair (~alex@wikimedia/Krenair) a quitté (Ping timeout: 240 seconds) 2019-10-02 13:09:38 <-- chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a quitté (Ping timeout: 240 seconds) 2019-10-02 13:10:02 <-- SpaceManiac (~SpaceMani@c-67-172-121-111.hsd1.ca.comcast.net) a quitté (Ping timeout: 240 seconds) 2019-10-02 13:12:22 --> SpaceManiac (~SpaceMani@c-67-172-121-111.hsd1.ca.comcast.net) a rejoint #mcdevs 2019-10-02 13:12:22 -- Mode #mcdevs [+v SpaceManiac] par ChanServ 2019-10-02 13:12:46 --> chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a rejoint #mcdevs 2019-10-02 13:15:28 --> Krenair (~alex@wikimedia/Krenair) a rejoint #mcdevs 2019-10-02 13:21:57 --> M-Processus42 (processus4@gateway/shell/matrix.org/x-ljpqxismvldbdrpx) a rejoint #mcdevs 2019-10-02 13:25:31 --> Nitwel (5c756621@92.117.102.33) a rejoint #mcdevs 2019-10-02 14:16:57 --> dan9er[m] (dan9ermatr@gateway/shell/matrix.org/x-szsnwsmlocscsrtn) a rejoint #mcdevs 2019-10-02 14:16:58 --> yangm (yanyetanot@gateway/shell/matrix.org/x-uvuvplcmgnlmeztj) a rejoint #mcdevs 2019-10-02 14:18:48 <-- simon816 (~simon816@ec2-52-43-110-46.us-west-2.compute.amazonaws.com) a quitté (Ping timeout: 245 seconds) 2019-10-02 14:21:51 --> simon816 (~simon816@ec2-52-43-110-46.us-west-2.compute.amazonaws.com) a rejoint #mcdevs 2019-10-02 14:25:40 Nitwel Hey, I'm still trying to figure out how a ChunkPacket is structured and I think I got it. Is it correct that a Palette works like a colorPalette for images? It defines which blocks/colors are present in the chunk/image? And a direct palette is just an varInt list of all blocks present where the varint describes the blocktype directly? 2019-10-02 14:49:15 timmyRS A direct palette is 14 bits per block and you put the blockstate ID directly into the chunk data, esentially not using any palette. 2019-10-02 14:52:37 Nitwel Ah, then finally, I understood what is meant by the palette. XD 2019-10-02 15:04:01 <-- thekinrar (~thekinrar@cpc115984-dals23-2-0-cust217.20-2.cable.virginm.net) a quitté (Read error: Connection reset by peer) 2019-10-02 16:14:01 Not-5e4d [McUpdates] Minecraft snapshot 19w40a has just been published to the launcher! 2019-10-02 16:14:10 Not-5e4d [McUpdates] Data generated by 19w40a: https://apimon.de/mcdata/19w40a/19w40a.zip 2019-10-02 16:14:16 Not-5e4d [minecraft-data] automatic-beyond-belief pushed 1 commit to master [+0/-0/±1] https://git.io/JecJr 2019-10-02 16:14:17 Not-5e4d [minecraft-data] automatic-beyond-belief 709651a - Add 19w40a to common/protocolVersions.json 2019-10-02 16:24:49 Not-5e4d [Burger] New data now avaliable for 19w40a: 2019-10-02 16:24:50 Not-5e4d [Burger] Diff from 19w39a: https://pokechu22.github.io/Burger/diff_19w39a_19w40a.html (https://pokechu22.github.io/Burger/diff_19w39a_19w40a.json) 2019-10-02 16:24:52 Not-5e4d [Burger] Full data: https://pokechu22.github.io/Burger/19w40a.html (https://pokechu22.github.io/Burger/19w40a.json) 2019-10-02 18:35:46 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-02 22:28:28 <-- Nitwel (5c756621@92.117.102.33) a quitté (Remote host closed the connection) 2019-10-02 23:53:56 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-jseflukowfdeztwe) a rejoint #mcdevs 2019-10-03 02:09:12 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 245 seconds) 2019-10-03 02:20:13 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-03 04:43:40 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-jseflukowfdeztwe) a quitté (Quit: Connection closed for inactivity) 2019-10-03 06:11:26 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-03 06:13:47 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 276 seconds) 2019-10-03 06:13:47 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-03 12:42:47 --> Dadido3_ (~quassel@p54A3A74D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-10-03 12:44:53 <-- Dadido3 (~quassel@p200300D9DF380F001DFDEC4DF61CE95F.dip0.t-ipconnect.de) a quitté (Ping timeout: 245 seconds) 2019-10-03 13:05:54 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Quit: mgrech) 2019-10-03 15:31:31 --> Ron36 (6d400345@bzq-109-64-3-69.red.bezeqint.net) a rejoint #mcdevs 2019-10-03 15:31:41 Ron36 hello 2019-10-03 15:32:25 <-- Ron36 (6d400345@bzq-109-64-3-69.red.bezeqint.net) a quitté (Remote host closed the connection) 2019-10-03 15:35:18 timmyRS "Didn't get a response after 40 seconds, guess I'm leaving." 2019-10-03 17:31:17 <-- PolarizedIons (polarizedi@unaffiliated/polarizedions) a quitté (Ping timeout: 240 seconds) 2019-10-03 17:46:32 --> PolarizedIons (~polarized@unaffiliated/polarizedions) a rejoint #mcdevs 2019-10-03 18:04:24 <-- PolarizedIons (~polarized@unaffiliated/polarizedions) a quitté (Ping timeout: 265 seconds) 2019-10-03 18:05:37 --> PolarizedIons (~polarized@unaffiliated/polarizedions) a rejoint #mcdevs 2019-10-03 19:40:20 VADemon Where do I find Moejangs official obfuscation mappings? I cant find them in the jsons 2019-10-03 19:41:52 timmyRS They started to be delivered a couple of snapshots ago, you'll see client_mappings & server_mappings in the version's JSON with their URL: https://launchermeta.mojang.com/v1/packages/6765b70650d8b7cc2d1f6518bac283d5229f4fb3/19w40a.json 2019-10-03 19:42:49 VADemon ah launcher meta. thanks 2019-10-03 19:59:50 MiniDigger They are also linked on the Minecraft wiki, might be slightly easier if you are just browsing 2019-10-03 22:10:02 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-kkqlytvvfxsbllqf) a rejoint #mcdevs 2019-10-03 22:53:29 <-- dexter0 (~dexter0@2601:647:4500:700:7c:10ff:fe00:110b) a quitté (Ping timeout: 276 seconds) 2019-10-03 23:06:24 --> dexter0 (~dexter0@c-73-222-1-210.hsd1.ca.comcast.net) a rejoint #mcdevs 2019-10-04 01:29:40 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-kkqlytvvfxsbllqf) a quitté (Quit: Connection closed for inactivity) 2019-10-04 01:37:09 timmyRS I list-pinged a LAN world and now I'm even more confused/intrigued: https://lava.st/z2et8.png 2019-10-04 01:38:09 timmyRS Note the 1/8 players. Also, I don't understand why MC-158582 is marked as "Won't Fix." Arg, this is such a minor part of the game yet I'm annoyed by its shortcomings :/ 2019-10-04 01:39:40 +pokechu22 Adding it to the UDP multicast wouldn't be backwards compatible (i.e. older versions still wouldn't display it), but I'm not sure why the game doesn't perform a normal ping once it's listed in the multicast... I assumed it did for some reason 2019-10-04 02:14:17 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 240 seconds) 2019-10-04 02:23:35 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-04 03:30:02 <-- SpaceManiac (~SpaceMani@c-67-172-121-111.hsd1.ca.comcast.net) a quitté (Ping timeout: 245 seconds) 2019-10-04 03:30:52 <-- saper (saper@wikipedia/saper) a quitté (Ping timeout: 245 seconds) 2019-10-04 03:31:22 --> saper (saper@wikipedia/saper) a rejoint #mcdevs 2019-10-04 03:32:53 --> SpaceManiac (~SpaceMani@2601:200:4400:f::103e) a rejoint #mcdevs 2019-10-04 03:32:53 -- Mode #mcdevs [+v SpaceManiac] par ChanServ 2019-10-04 05:07:17 <-- pokechu22 (~pokechu22@2601:602:900:860:816a:390b:fd19:1c1a) a quitté (Ping timeout: 246 seconds) 2019-10-04 05:11:53 --> pokechu22 (~pokechu22@2601:602:900:860:816a:390b:fd19:1c1a) a rejoint #mcdevs 2019-10-04 05:11:53 -- Mode #mcdevs [+v pokechu22] par ChanServ 2019-10-04 05:15:49 Andrio Would depend on specifically how the multicast packet is read 2019-10-04 05:16:00 Andrio Adding extra data to the end of it might work 2019-10-04 05:28:16 <-- niceplace (~nplace@185.128.25.132) a quitté (Quit: ZNC 1.7.3 - https://znc.in) 2019-10-04 05:28:38 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 09:52:53 <-- PolarizedIons (~polarized@unaffiliated/polarizedions) a quitté (Quit: Ping timeout (120 seconds)) 2019-10-04 09:53:22 --> PolarizedIons (~polarized@unaffiliated/polarizedions) a rejoint #mcdevs 2019-10-04 10:21:11 <-- SpaceManiac (~SpaceMani@2601:200:4400:f::103e) a quitté (Ping timeout: 276 seconds) 2019-10-04 10:51:40 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-10-04 10:53:15 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 11:47:30 <-- niceplace (~nplace@185.128.25.132) a quitté (Quit: ZNC 1.7.3 - https://znc.in) 2019-10-04 11:49:22 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 11:55:56 --> niceplaces (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 11:56:05 <-- niceplace (~nplace@185.128.25.132) a quitté (Ping timeout: 276 seconds) 2019-10-04 11:58:36 <-- niceplaces (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-10-04 11:59:32 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 12:00:34 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-10-04 12:02:26 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 12:03:35 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-10-04 12:06:41 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 12:10:31 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-10-04 12:11:58 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 12:25:22 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-10-04 12:39:11 --> Me4502__ (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-10-04 12:42:02 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Ping timeout: 240 seconds) 2019-10-04 13:13:08 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 268 seconds) 2019-10-04 13:15:35 <-- niceplace (~nplace@185.128.25.132) a quitté (Read error: Connection reset by peer) 2019-10-04 13:16:03 --> redstonehelper (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-04 13:16:09 --> niceplace (~nplace@185.128.25.132) a rejoint #mcdevs 2019-10-04 14:51:28 --> niceplaces (~nplace@titan.pathogen.is) a rejoint #mcdevs 2019-10-04 14:54:50 <-- niceplace (~nplace@185.128.25.132) a quitté (Ping timeout: 240 seconds) 2019-10-04 14:55:55 <-- niceplaces (~nplace@titan.pathogen.is) a quitté (Ping timeout: 250 seconds) 2019-10-04 15:27:11 --> niceplace (~nplace@45.89.174.102) a rejoint #mcdevs 2019-10-04 15:59:23 <-- Me4502__ (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-10-04 16:31:50 <-- niceplace (~nplace@45.89.174.102) a quitté (Read error: Connection reset by peer) 2019-10-04 16:34:41 --> niceplace (~nplace@titan.pathogen.is) a rejoint #mcdevs 2019-10-04 16:54:28 timmyRS You could also just announce the world twice, once in old format, and once in new format. And, since a player needs the exact version to join anyway, who cares for backward compatibility? 2019-10-04 17:30:22 --> PolarizedIons2 (~Polarized@ip4da49ab9.direct-adsl.nl) a rejoint #mcdevs 2019-10-04 17:30:30 <-- PolarizedIons2 (~Polarized@ip4da49ab9.direct-adsl.nl) a quitté (Client Quit) 2019-10-04 19:09:52 --> skyrising (~skyrising@89.43.126.17) a rejoint #mcdevs 2019-10-04 21:20:59 <-- PolarizedIons (~polarized@unaffiliated/polarizedions) a quitté (Quit: Ping timeout (120 seconds)) 2019-10-04 21:21:28 --> PolarizedIons (~polarized@unaffiliated/polarizedions) a rejoint #mcdevs 2019-10-04 21:56:19 --> Oatmeal (~Suzeanne@ip68-4-181-8.oc.oc.cox.net) a rejoint #mcdevs 2019-10-05 00:35:27 <-- Dadido3_ (~quassel@p54A3A74D.dip0.t-ipconnect.de) a quitté (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 2019-10-05 00:36:12 --> Dadido3 (~quassel@p200300D9DF380F006C17C6DCD98697EC.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-10-05 00:49:47 --> epicface92 (~epicface9@73.50.219.2) a rejoint #mcdevs 2019-10-05 02:02:12 --> caelunshun (~caelum@66.205.213.219) a rejoint #mcdevs 2019-10-05 02:06:17 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 245 seconds) 2019-10-05 02:18:54 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-05 02:35:25 <-- epicface92 (~epicface9@73.50.219.2) a quitté (Quit: Lost terminal) 2019-10-05 02:41:40 --> SpaceManiac (~SpaceMani@c-67-172-121-111.hsd1.ca.comcast.net) a rejoint #mcdevs 2019-10-05 02:41:49 -- Mode #mcdevs [+v SpaceManiac] par ChanServ 2019-10-05 03:51:25 <-- laxask (~lax@unaffiliated/laxask) a quitté (Ping timeout: 246 seconds) 2019-10-05 03:58:27 --> laxask (~lax@unaffiliated/laxask) a rejoint #mcdevs 2019-10-05 09:21:55 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-10-05 10:13:23 <-- VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a quitté (Read error: Connection reset by peer) 2019-10-05 11:10:17 --> killmePI (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-10-05 11:10:20 <-- killme (~killmePI@185.9.253.124) a quitté (Ping timeout: 276 seconds) 2019-10-05 16:04:59 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-10-05 18:50:40 caelunshun I'm having a problem where clients apply gravity to floating players. When a player flies up and then hovers, other clients perceive them to fall back down. Does anyone know what needs to be done to prevent this behavior? 2019-10-05 18:54:32 timmyRS I don't think the vanilla client does that sort of thing, unless it has something to do with the new "Pose" field in the entity metadata 2019-10-05 19:13:49 caelunshun Not sure what else it could be, though—and the behavior does look a lot like physics. 2019-10-05 19:18:35 +pokechu22 The vanilla client does do that, but it only should happen to players not marked as flying with creative flight... and now I'm not sure how that actually is sent 2019-10-05 19:21:05 +pokechu22 There is the pose enum, but I don't think that's responsible for physics calculations (and the only relevant entry is named `FALL_FLYING`, which makes me think it's used for both falling entities and entities that have flight) 2019-10-05 19:22:08 timmyRS I never saw the client predict other player's falls... maybe it has to do with the gamemode in the player list item? 2019-10-05 19:22:58 +pokechu22 Maybe, but I feel like it's not an issue when using /fly from essentials (but maybe the implementation of the relevant Bukkit method does something special there... I thought it just sent the player abilities packet though) 2019-10-05 19:24:04 timmyRS I think it's something new in 1.14. Maybe the pose, maybe something else. 2019-10-05 19:29:31 caelunshun Never mind, looks like I was applying physics to players on the server side on accident. Slight mistake. 2019-10-05 19:29:36 caelunshun Thanks for the help though 2019-10-05 19:29:54 timmyRS That was my second thought. lol. 2019-10-05 23:22:56 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-06 01:47:17 <-- Oatmeal (~Suzeanne@ip68-4-181-8.oc.oc.cox.net) a quitté (Ping timeout: 240 seconds) 2019-10-06 02:21:24 --> Oatmeal (~Suzeanne@ip68-4-181-8.oc.oc.cox.net) a rejoint #mcdevs 2019-10-06 08:46:23 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-10-06 13:51:50 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-10-06 13:54:08 <-- M-Processus42 (processus4@gateway/shell/matrix.org/x-ljpqxismvldbdrpx) a quitté (Read error: Connection reset by peer) 2019-10-06 13:54:40 <-- yangm (yanyetanot@gateway/shell/matrix.org/x-uvuvplcmgnlmeztj) a quitté (Write error: Connection reset by peer) 2019-10-06 13:54:46 <-- dan9er[m] (dan9ermatr@gateway/shell/matrix.org/x-szsnwsmlocscsrtn) a quitté (Read error: Connection reset by peer) 2019-10-06 14:06:16 --> M-Processus42 (processus4@gateway/shell/matrix.org/x-hyezsmiicbnadgvq) a rejoint #mcdevs 2019-10-06 14:15:35 timmyRS I can't move an entity of type shulker using "Entity Teleport" or "Entity Relative Move." It works on iron golem, so I don't think it has anything to do with it technically being a golem. Does anyone have any ideas? 2019-10-06 14:43:35 Andrio IIRC shulkers teleport themselves back to the coordinates specified in their NBT tags; that might be related. 2019-10-06 15:01:30 --> dan9er[m] (dan9ermatr@gateway/shell/matrix.org/x-snlhqkidovdczidu) a rejoint #mcdevs 2019-10-06 15:01:30 --> yangm (yanyetanot@gateway/shell/matrix.org/x-cgkchijgjkpllpac) a rejoint #mcdevs 2019-10-06 15:28:41 timmyRS That sounds reasonable, but I don't see any way to send the entity's NBT over the network. I've tried the "Attachment position" entity metadata, but that doesn't seem to have any effect either. 2019-10-06 15:29:13 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-06 15:31:08 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 245 seconds) 2019-10-06 15:31:08 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-06 15:31:15 timmyRS I can move it by sending spawn mob using the same EID, but that causes it to spin out, and also doesn't sound like a good solution. 2019-10-06 15:32:08 timmyRS Although this is by far the snappiest way to move an entity, no teleportation animation. Shame there's no way to do it that's not so... hacky? 2019-10-06 18:48:34 +pokechu22 timmyRS: It's the "attached block pos" entity metadata for shulkers it seems 2019-10-06 19:41:45 timmyRS Using the index + 2 worked. That article really needs to be merged. :/ 2019-10-06 19:58:50 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-06 20:12:28 <-- Guest24629 (~WizardCM@103.93.232.1) a quitté (Remote host closed the connection) 2019-10-06 20:12:50 --> Wizard (~WizardCM@103.93.232.1) a rejoint #mcdevs 2019-10-06 20:13:14 -- Wizard est maintenant connu sous le nom Guest36318 2019-10-06 21:06:38 timmyRS Am I going insane or is the "Position" section for the 1.8 < https://wiki.vg/index.php?title=Protocol&oldid=7368#Position > exactly the same as the current < https://wiki.vg/Protocol#Position >? 2019-10-06 21:09:38 timmyRS I'm pretty sure the 1.8 - 1.13 did not send positions in the 1.14 format, yet there it is on the old revisions of the protocol page?! 2019-10-06 21:11:27 +pokechu22 It's because it transcludes the most recent revision of the data types article... which means you see the most recent data types definitions, instead of the ones from back then 2019-10-06 21:12:15 timmyRS Ah, so it's an artice within an article. Trippy. 2019-10-06 21:26:51 +pokechu22 Tada: https://wiki.vg/index.php?title=Data_types&diff=15021&oldid=15020 (https://wiki.vg/index.php?title=Protocol&oldid=14889#Data_types) 2019-10-06 21:29:05 timmyRS Nice time traveller detection, don't tell the FBI about it ;P 2019-10-06 21:56:33 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-07 01:35:56 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-07 01:37:17 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 268 seconds) 2019-10-07 01:37:18 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-07 02:15:30 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 265 seconds) 2019-10-07 02:19:49 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-07 04:02:02 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-07 06:11:36 <-- alexge50 (~alexge50@unaffiliated/alexge50) a quitté (Read error: Connection reset by peer) 2019-10-07 06:13:24 --> alexge50 (~alexge50@188.25.126.81) a rejoint #mcdevs 2019-10-07 06:19:39 <-- alexge50 (~alexge50@188.25.126.81) a quitté (Read error: Connection reset by peer) 2019-10-07 06:20:57 --> alexge50 (~alexge50@188.25.126.81) a rejoint #mcdevs 2019-10-07 06:28:28 <-- alexge50 (~alexge50@188.25.126.81) a quitté (Read error: Connection reset by peer) 2019-10-07 11:23:39 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-07 11:29:59 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-10-07 15:17:06 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-10-07 16:19:00 <-- dan9er[m] (dan9ermatr@gateway/shell/matrix.org/x-snlhqkidovdczidu) a quitté (Read error: Connection reset by peer) 2019-10-07 16:19:06 <-- yangm (yanyetanot@gateway/shell/matrix.org/x-cgkchijgjkpllpac) a quitté (Read error: Connection reset by peer) 2019-10-07 16:19:21 <-- M-Processus42 (processus4@gateway/shell/matrix.org/x-hyezsmiicbnadgvq) a quitté (Read error: Connection reset by peer) 2019-10-07 16:43:31 --> alexge50 (~alexge50@188.25.126.81) a rejoint #mcdevs 2019-10-07 17:36:18 <-- caelunshun (~caelum@66.205.213.219) a quitté (Quit: WeeChat 1.9.1) 2019-10-07 18:08:17 <-- Oatmeal (~Suzeanne@ip68-4-181-8.oc.oc.cox.net) a quitté (Ping timeout: 240 seconds) 2019-10-07 18:34:52 --> dan9er[m] (dan9ermatr@gateway/shell/matrix.org/x-qsuudtxnvwkvreiy) a rejoint #mcdevs 2019-10-07 18:39:12 --> Oatmeal (~Suzeanne@2600:8802:1500:1a1:e040:aac9:8384:7c94) a rejoint #mcdevs 2019-10-07 19:31:00 --> yangm (yanyetanot@gateway/shell/matrix.org/x-pvvvqarivbhqbejw) a rejoint #mcdevs 2019-10-07 19:31:00 --> M-Processus42 (processus4@gateway/shell/matrix.org/x-xqfkgszjqvfoxnig) a rejoint #mcdevs 2019-10-07 20:53:32 <-- Tknoguyfication (~Tknoguyfi@184.103.118.55) a quitté (Ping timeout: 268 seconds) 2019-10-07 20:53:59 --> Tknoguyf- (~Tknoguyfi@75-167-61-77.phnx.qwest.net) a rejoint #mcdevs 2019-10-07 20:54:02 -- Tknoguyf- est maintenant connu sous le nom Tknoguyfication 2019-10-07 22:17:37 --> PolarizedIons3 (~polarized@169-0-111-232.ip.afrihost.co.za) a rejoint #mcdevs 2019-10-07 22:18:31 --> PolarizedIons31 (~polarized@169-0-101-165.ip.afrihost.co.za) a rejoint #mcdevs 2019-10-07 22:18:45 <-- PolarizedIons3 (~polarized@169-0-111-232.ip.afrihost.co.za) a quitté (Read error: Connection reset by peer) 2019-10-07 22:21:25 <-- PolarizedIons (~polarized@unaffiliated/polarizedions) a quitté (Ping timeout: 265 seconds) 2019-10-07 23:56:14 --> hornta (5ae63259@90-230-50-89-no31.tbcn.telia.com) a rejoint #mcdevs 2019-10-07 23:59:28 hornta hello. i'm working on the flying-squid javascript minecraft server trying to get it working with 1.13.2 right now. i'm stuck having the client crash as soon as i send a chunk data packet to it. i believe the packet i'm sending follows this format: https://wiki.vg/index.php?title=Protocol&oldid=14204#Chunk_Data but the client still crashes as soon 2019-10-07 23:59:29 hornta as the chunk is delivered. how can i debug and find out if the chunk buffer data is incorrect? 2019-10-08 00:04:32 timmyRS Maybe this helps: https://wiki.vg/index.php?title=Pre-release_protocol&direction=next&oldid=14264#Chunk_Data 2019-10-08 00:07:56 rom1504 is there any implementation for 1.13 ? 2019-10-08 00:08:36 rom1504 ah I see https://github.com/caelunshun/feather/blob/develop/core/src/world/chunk.rs 2019-10-08 00:08:52 rom1504 hornta maybe this one ^ 2019-10-08 00:09:13 rom1504 if anybody has some 1.13 chunk implementation, it would be useful to test against 2019-10-08 00:09:23 hornta rom1504 that is the one i followed whrn writing the 1.13 chunk impl. for prismarinejs 2019-10-08 00:09:30 hornta rom1504 that is the one i followed when writing the 1.13 chunk impl. for prismarinejs 2019-10-08 00:09:50 rom1504 ok 2019-10-08 00:10:09 rom1504 maybe compile it and try to check if the chunk you dump can be read with the rust implem 2019-10-08 00:10:21 -- Le titre pour #mcdevs est "A haunt for developers working on projects related to Minecraft | Website & Rules: http://wiki.vg/MCDevs/rules | Wiki: http://wiki.vg | Channel is publicly logged as of Feb.25/13 https://logs.rom1504.fr/" 2019-10-08 00:10:21 -- Titre défini par tktech (~tktech@ec2-52-70-105-60.compute-1.amazonaws.com) le jeu., 11 mai 2017 00:28:31 2019-10-08 00:11:53 timmyRS I could provide a PHP implementation that can write it but if the lazy dev timmyRS is to be believed it will so be able to read it as well 2019-10-08 00:19:15 <-- killmePI (~killmePI@185.9.253.124) a quitté (Ping timeout: 264 seconds) 2019-10-08 00:29:20 <-- hornta (5ae63259@90-230-50-89-no31.tbcn.telia.com) a quitté (Remote host closed the connection) 2019-10-08 01:39:54 --> VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a rejoint #mcdevs 2019-10-08 02:15:21 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 265 seconds) 2019-10-08 02:23:36 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-08 02:29:35 <-- _123DMWM (~123DMWM@c-73-60-129-142.hsd1.ma.comcast.net) a quitté (Quit: _123DMWM) 2019-10-08 02:31:26 --> _123DMWM (~123DMWM@2601:18d:580:3870:1c9a:47fe:54ad:3265) a rejoint #mcdevs 2019-10-08 03:22:53 <-- Oatmeal (~Suzeanne@2600:8802:1500:1a1:e040:aac9:8384:7c94) a quitté (Ping timeout: 250 seconds) 2019-10-08 04:04:43 --> Oatmeal (~Suzeanne@2600:8802:1500:80e:e040:aac9:8384:7c94) a rejoint #mcdevs 2019-10-08 04:37:57 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-08 05:56:38 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-xbwwbqvhwihdqsdh) a rejoint #mcdevs 2019-10-08 09:04:42 <-- Guest36318 (~WizardCM@103.93.232.1) a quitté (Remote host closed the connection) 2019-10-08 09:05:00 --> Wizard (~WizardCM@103.93.232.1) a rejoint #mcdevs 2019-10-08 09:05:23 -- Wizard est maintenant connu sous le nom Guest83359 2019-10-08 10:29:50 --> killme (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-10-08 11:18:18 <-- PolarizedIons31 (~polarized@169-0-101-165.ip.afrihost.co.za) a quitté (Quit: Ping timeout (120 seconds)) 2019-10-08 11:18:43 --> PolarizedIons31 (~polarized@169-0-101-165.ip.afrihost.co.za) a rejoint #mcdevs 2019-10-08 11:35:53 --> mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-08 15:04:14 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-xbwwbqvhwihdqsdh) a quitté (Quit: Connection closed for inactivity) 2019-10-08 18:05:03 <-- PolarizedIons31 (~polarized@169-0-101-165.ip.afrihost.co.za) a quitté (Changing host) 2019-10-08 18:05:03 --> PolarizedIons31 (~polarized@unaffiliated/polarizedions) a rejoint #mcdevs 2019-10-08 18:05:08 -- PolarizedIons31 est maintenant connu sous le nom PolarizedIons 2019-10-08 18:13:23 --> vert3xo (~vert3xo@gateway/tor-sasl/vert3xo) a rejoint #mcdevs 2019-10-08 18:21:49 --> vert3xo_ (~vert3xo@gateway/tor-sasl/vert3xo) a rejoint #mcdevs 2019-10-08 18:25:28 <-- vert3xo (~vert3xo@gateway/tor-sasl/vert3xo) a quitté (Ping timeout: 260 seconds) 2019-10-08 18:38:38 --> O47m341 (~Suzeanne@2600:8802:1500:80e:e040:aac9:8384:7c94) a rejoint #mcdevs 2019-10-08 18:54:16 --> vert3xo__ (~vert3xo@gateway/tor-sasl/vert3xo) a rejoint #mcdevs 2019-10-08 18:58:08 <-- vert3xo_ (~vert3xo@gateway/tor-sasl/vert3xo) a quitté (Ping timeout: 260 seconds) 2019-10-08 19:28:00 <-- vert3xo__ (~vert3xo@gateway/tor-sasl/vert3xo) a quitté (Ping timeout: 260 seconds) 2019-10-08 20:53:20 <-- alexge50 (~alexge50@188.25.126.81) a quitté (Changing host) 2019-10-08 20:53:20 --> alexge50 (~alexge50@unaffiliated/alexge50) a rejoint #mcdevs 2019-10-08 21:05:17 <-- PolarizedIons (~polarized@unaffiliated/polarizedions) a quitté (Quit: Ping timeout (120 seconds)) 2019-10-08 21:05:47 --> PolarizedIons (~polarized@unaffiliated/polarizedions) a rejoint #mcdevs 2019-10-08 21:16:50 --> PolarizedIons6 (~polarized@169-0-101-165.ip.afrihost.co.za) a rejoint #mcdevs 2019-10-08 21:17:48 <-- PolarizedIons (~polarized@unaffiliated/polarizedions) a quitté (Ping timeout: 245 seconds) 2019-10-08 22:05:21 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-vlilkumprizhbprt) a rejoint #mcdevs 2019-10-09 00:25:01 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-vlilkumprizhbprt) a quitté (Quit: Connection closed for inactivity) 2019-10-09 00:34:47 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-cxcsixmzgpkamvln) a rejoint #mcdevs 2019-10-09 01:03:32 <-- mgrech (~mgrech@213-240-103-103.adsl.highway.telekom.at) a quitté (Ping timeout: 246 seconds) 2019-10-09 02:09:17 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 240 seconds) 2019-10-09 02:19:18 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-09 02:55:01 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-cxcsixmzgpkamvln) a quitté (Quit: Connection closed for inactivity) 2019-10-09 03:00:30 --> mgrech (~mgrech@194-166-232-167.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-09 03:44:55 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-09 03:46:33 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 265 seconds) 2019-10-09 03:46:33 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-09 04:53:37 <-- mgrech (~mgrech@194-166-232-167.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-09 05:20:08 <-- levifig (~levi@hakr.io) a quitté (Quit: Farewell) 2019-10-09 05:21:13 --> levifig (~levi@hakr.io) a rejoint #mcdevs 2019-10-09 06:31:05 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-09 06:33:47 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 265 seconds) 2019-10-09 06:33:47 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-09 14:32:21 <-- yangm (yanyetanot@gateway/shell/matrix.org/x-pvvvqarivbhqbejw) a quitté (Ping timeout: 250 seconds) 2019-10-09 14:39:00 --> yangm (yanyetanot@gateway/shell/matrix.org/x-rwihvxkowkrgcoac) a rejoint #mcdevs 2019-10-09 14:57:08 <-- M-Processus42 (processus4@gateway/shell/matrix.org/x-xqfkgszjqvfoxnig) a quitté (Ping timeout: 248 seconds) 2019-10-09 14:57:47 --> M-Processus42 (processus4@gateway/shell/matrix.org/x-unadasyyriwssrxz) a rejoint #mcdevs 2019-10-09 15:50:58 --> RoboMWM_ (~RoboMWM@tf.robomwm.com) a rejoint #mcdevs 2019-10-09 15:53:11 --> Techcable_ (znc@irc.techcable.net) a rejoint #mcdevs 2019-10-09 15:53:40 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-09 15:53:53 --> doopqoob (~doop@colostomy.club) a rejoint #mcdevs 2019-10-09 15:54:22 --> Plancke_ (~Plancke@2604:a880:400:d0::d58:e001) a rejoint #mcdevs 2019-10-09 15:55:01 --> someone_stole_my (~mrkirby15@mrkirby153.com) a rejoint #mcdevs 2019-10-09 15:55:15 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:15 <-- Guest92473 (~jamie@vista.jamiemansfield.me) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:15 <-- Techcable (znc@irc.techcable.net) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:15 <-- mundus (~mundus201@unaffiliated/mundus2018) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:16 <-- ddevault (znc@sourcehut/staff/ddevault) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:16 <-- RoboMWM (~RoboMWM@tf.robomwm.com) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:16 <-- Byteflux (~byte@byteflux.net) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:16 <-- Plancke (~Plancke@159.203.185.60) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:16 -- Plancke_ est maintenant connu sous le nom Plancke 2019-10-09 15:55:17 <-- mrkirby153 (~mrkirby15@mrkirby153.com) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:17 <-- Proximyst (~Proximyst@148.251.50.76) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:17 <-- peterix (~peterix@quassel.woboq.com) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:17 <-- Adam (Adam@unaffiliated/adam-) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:17 <-- x10A94 (~x@207.154.230.175) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:17 <-- doop (~doop@colostomy.club) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:17 <-- darngeek (~darngeek@bouncer.pocketmine.net) a quitté (Ping timeout: 268 seconds) 2019-10-09 15:55:21 -- RoboMWM_ est maintenant connu sous le nom RoboMWM 2019-10-09 15:55:23 --> x1365C (~x@207.154.230.175) a rejoint #mcdevs 2019-10-09 15:55:28 --> Adam (Adam@sigterm.info) a rejoint #mcdevs 2019-10-09 15:55:32 <-- Adam (Adam@sigterm.info) a quitté (Changing host) 2019-10-09 15:55:32 --> Adam (Adam@unaffiliated/adam-) a rejoint #mcdevs 2019-10-09 15:55:37 --> Byteflux (~byte@byteflux.net) a rejoint #mcdevs 2019-10-09 15:55:37 --> Proximyst (~Proximyst@148.251.50.76) a rejoint #mcdevs 2019-10-09 15:55:39 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-09 15:55:41 --> dranghek (~darngeek@bouncer.pocketmine.net) a rejoint #mcdevs 2019-10-09 15:55:47 --> jamierocks (~jamie@vista.jamiemansfield.me) a rejoint #mcdevs 2019-10-09 15:56:35 --> peterix (ogoffart@quassel.woboq.de) a rejoint #mcdevs 2019-10-09 15:56:38 --> ddevault (znc@sourcehut/staff/ddevault) a rejoint #mcdevs 2019-10-09 15:56:48 -- Mode #mcdevs [+v ddevault] par ChanServ 2019-10-09 15:57:12 --> mundus2018 (~mundus201@unaffiliated/mundus2018) a rejoint #mcdevs 2019-10-09 16:06:02 <-- killme (~killmePI@185.9.253.124) a quitté (Ping timeout: 240 seconds) 2019-10-09 16:06:29 --> killme (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-10-09 17:34:31 --> Merlin_O (~Merlin_O@p200300D7CF0D3500E5D9ED94111DFFF0.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-10-09 17:37:11 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-rtudwieufnuaxpkt) a rejoint #mcdevs 2019-10-09 17:57:02 Not-5e4d [McUpdates] Minecraft snapshot 19w41a has just been published to the launcher! 2019-10-09 17:57:10 Not-5e4d [McUpdates] Data generated by 19w41a: https://apimon.de/mcdata/19w41a/19w41a.zip 2019-10-09 17:57:16 Not-5e4d [minecraft-data] automatic-beyond-belief pushed 1 commit to master [+0/-0/±1] https://git.io/JeWMg 2019-10-09 17:57:18 Not-5e4d [minecraft-data] automatic-beyond-belief 1e5ef65 - Add 19w41a to common/protocolVersions.json 2019-10-09 18:05:20 Not-5e4d [Burger] New data now avaliable for 19w41a: 2019-10-09 18:05:21 Not-5e4d [Burger] Diff from 19w40a: https://pokechu22.github.io/Burger/diff_19w40a_19w41a.html (https://pokechu22.github.io/Burger/diff_19w40a_19w41a.json) 2019-10-09 18:05:23 Not-5e4d [Burger] Full data: https://pokechu22.github.io/Burger/19w41a.html (https://pokechu22.github.io/Burger/19w41a.json) 2019-10-09 18:15:02 Not-5e4d [McUpdates] An article about Minecraft Snapshot 19w41a was just published: https://www.minecraft.net/en-us/article/minecraft-snapshot-19w41a 2019-10-09 19:06:57 --> barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a rejoint #mcdevs 2019-10-09 19:14:36 <-- VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a quitté (Quit: left4dead) 2019-10-09 19:32:27 <-- Merlin_O (~Merlin_O@p200300D7CF0D3500E5D9ED94111DFFF0.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-10-09 20:02:14 --> mgrech (~mgrech@194-166-232-167.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-09 20:42:29 <-- O47m341 (~Suzeanne@2600:8802:1500:80e:e040:aac9:8384:7c94) a quitté (Quit: Suzie says, "TTFNs!") 2019-10-09 20:42:35 <-- Oatmeal (~Suzeanne@2600:8802:1500:80e:e040:aac9:8384:7c94) a quitté (Quit: Suzie says, "TTFNs!") 2019-10-09 20:57:32 --> mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-09 20:58:53 <-- mgrech (~mgrech@194-166-232-167.adsl.highway.telekom.at) a quitté (Ping timeout: 250 seconds) 2019-10-09 21:09:47 <-- PolarizedIons6 (~polarized@169-0-101-165.ip.afrihost.co.za) a quitté (Quit: Ping timeout (120 seconds)) 2019-10-09 21:10:19 --> PolarizedIons6 (~polarized@169-0-101-165.ip.afrihost.co.za) a rejoint #mcdevs 2019-10-09 21:28:16 <-- barneygale (~barneygal@cpc93782-hari17-2-0-cust1406.20-2.cable.virginm.net) a quitté (Remote host closed the connection) 2019-10-09 23:36:29 -- Guest83359 est maintenant connu sous le nom WizardCM 2019-10-10 00:38:52 <-- skyrising (~skyrising@89.43.126.17) a quitté (Read error: Connection reset by peer) 2019-10-10 00:39:02 --> skyrising (~skyrising@89.43.126.17) a rejoint #mcdevs 2019-10-10 00:43:14 <-- skyrising (~skyrising@89.43.126.17) a quitté (Ping timeout: 240 seconds) 2019-10-10 02:06:02 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 240 seconds) 2019-10-10 02:20:37 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-10 02:22:37 -- x1365C est maintenant connu sous le nom x10A94 2019-10-10 02:50:14 --> VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a rejoint #mcdevs 2019-10-10 03:19:24 <-- Dadido3 (~quassel@p200300D9DF380F006C17C6DCD98697EC.dip0.t-ipconnect.de) a quitté (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 2019-10-10 03:20:09 --> Dadido3 (~quassel@p200300D9DF380F0035B990AF6EA60EA2.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-10-10 03:23:02 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-10 03:24:26 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 240 seconds) 2019-10-10 03:24:26 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-10 04:56:03 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-rtudwieufnuaxpkt) a quitté (Quit: Connection closed for inactivity) 2019-10-10 05:04:28 <-- mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a quitté (Ping timeout: 245 seconds) 2019-10-10 07:33:29 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-fpzmqlmjswwvzxxj) a rejoint #mcdevs 2019-10-10 09:51:13 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-fpzmqlmjswwvzxxj) a quitté (Quit: Connection closed for inactivity) 2019-10-10 12:12:22 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-pyreiiizreeeblzt) a rejoint #mcdevs 2019-10-10 12:57:30 --> skyrising (~skyrising@89.43.126.17) a rejoint #mcdevs 2019-10-10 14:12:10 --> niceplaces (~nplace@174.128.245.152) a rejoint #mcdevs 2019-10-10 14:12:32 <-- niceplace (~nplace@titan.pathogen.is) a quitté (Ping timeout: 252 seconds) 2019-10-10 14:54:35 --> mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-10 17:56:00 --> mgrech (~mgrech@194-166-233-181.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-10 17:56:55 <-- mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a quitté (Ping timeout: 268 seconds) 2019-10-10 18:05:45 <-- VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a quitté (Read error: Connection reset by peer) 2019-10-10 18:16:41 --> VADemon (~VADemon@2a01:4f8:212:2f1d:88::41) a rejoint #mcdevs 2019-10-10 19:15:11 --> mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-10 19:17:05 <-- mgrech (~mgrech@194-166-233-181.adsl.highway.telekom.at) a quitté (Ping timeout: 268 seconds) 2019-10-10 19:18:02 <-- peterix (ogoffart@quassel.woboq.de) a quitté (Ping timeout: 240 seconds) 2019-10-10 19:23:07 <-- bildramer (~bildramer@p200300CF370C160098CE5C5602619B5F.dip0.t-ipconnect.de) a quitté (Remote host closed the connection) 2019-10-10 19:23:39 --> bildramer (~bildramer@p200300CF370C160098CE5C5602619B5F.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-10-10 19:33:51 --> peterix (quassel@quassel.woboq.de) a rejoint #mcdevs 2019-10-10 20:58:26 <-- mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a quitté (Ping timeout: 240 seconds) 2019-10-10 21:01:41 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-pyreiiizreeeblzt) a quitté (Quit: Connection closed for inactivity) 2019-10-10 21:13:33 Proximyst What category of sound does the wither spawn go under? 2019-10-10 22:58:50 --> mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-10 23:50:53 <-- mgrech_ (~mgrech@194-166-233-181.adsl.highway.telekom.at) a quitté (Ping timeout: 268 seconds) 2019-10-10 23:55:17 --> gabrielchihongle (uid274900@gateway/web/irccloud.com/x-jutulnkgmodlpokp) a rejoint #mcdevs 2019-10-11 00:17:52 timmyRS Never sent sounds before, but I'd go with the Entity Sound Effect packet and use the category hostile. 2019-10-11 00:19:45 +pokechu22 For the wither it looks like you actually should use Effect (with ID 1023) -- it's also worth noting that it's broadcast to all players in the world... https://wiki.vg/Protocol#Effect 2019-10-11 00:20:39 +pokechu22 I think that that internally goes into the hostile category though (but the client is the one that actually triggers the sound on receiving that effect) 2019-10-11 02:17:17 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 240 seconds) 2019-10-11 02:22:15 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-10-11 02:44:27 <-- gabrielchihongle (uid274900@gateway/web/irccloud.com/x-jutulnkgmodlpokp) a quitté (Quit: Connection closed for inactivity) 2019-10-11 06:21:57 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-10-11 06:23:38 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 240 seconds) 2019-10-11 06:23:38 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-10-11 06:32:06 --> cheakoirccloud (uid293319@gateway/web/irccloud.com/x-sfkziuyyrwaufxtw) a rejoint #mcdevs 2019-10-11 07:47:44 --> Yamakaja_ (~yamakaja@vps.pub.yamakaja.me) a rejoint #mcdevs 2019-10-11 07:52:59 --> chibill_ (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a rejoint #mcdevs 2019-10-11 07:54:35 <-- chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a quitté (Ping timeout: 245 seconds) 2019-10-11 07:54:35 <-- Yamakaja (~yamakaja@vps.pub.yamakaja.me) a quitté (Remote host closed the connection) 2019-10-11 09:10:09 <-- cheakoirccloud (uid293319@gateway/web/irccloud.com/x-sfkziuyyrwaufxtw) a quitté (Quit: Connection closed for inactivity) 2019-10-11 09:37:46 Proximyst The MC client doesn't let you turn it down on hostile at least, according to a few I've talked to.. sounds like the client actually plays it as master 2019-10-11 11:41:12 --> mgrech (~mgrech@194-166-233-181.adsl.highway.telekom.at) a rejoint #mcdevs 2019-10-11 12:42:26 <-- skyrising (~skyrising@89.43.126.17) a quitté (Ping timeout: 240 seconds) 2019-10-11 13:11:28 --> skyrising (~skyrising@85.220.133.61) a rejoint #mcdevs 2019-10-11 15:10:22 --> pvpctutorials (~skyrising@89.43.120.128) a rejoint #mcdevs 2019-10-11 15:10:46 <-- skyrising (~skyrising@85.220.133.61) a quitté (Ping timeout: 268 seconds) 2019-10-11 15:57:19 -- pvpctutorials est maintenant connu sous le nom skyrising