2019-02-26 13:27:36 --> electroniccat (~electroni@atlas.valaria.pw) a rejoint #mcdevs 2019-02-26 13:27:49 --> Byteflux_ (~byte@byteflux.net) a rejoint #mcdevs 2019-02-26 13:28:46 <-- Byteflux (~byte@byteflux.net) a quitté (Disconnected by services) 2019-02-26 13:28:54 -- Byteflux_ est maintenant connu sous le nom Byteflux 2019-02-26 13:29:10 --> killmePI (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-02-26 13:29:20 +Amaranth6 What the... 2019-02-26 13:29:53 <-- Amaranth (~Amaranth@ubuntu/member/Amaranth) a quitté (Disconnected by services) 2019-02-26 13:29:54 Andrio Netsplat 2019-02-26 13:29:58 -- Amaranth6 est maintenant connu sous le nom Amaranth 2019-02-26 13:30:24 <-- takenbacon (~takenbaco@c-98-246-68-121.hsd1.wa.comcast.net) a quitté (Ping timeout: 246 seconds) 2019-02-26 13:30:24 <-- saper (saper@wikipedia/saper) a quitté (Ping timeout: 246 seconds) 2019-02-26 13:30:25 --> some02 (~lax@unaffiliated/laxask) a rejoint #mcdevs 2019-02-26 13:30:28 <-- redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 255 seconds) 2019-02-26 13:30:29 <-- sudden (~lax@unaffiliated/laxask) a quitté (Ping timeout: 255 seconds) 2019-02-26 13:30:29 <-- Unarelith (~Quent4234@40.238.7.109.rev.sfr.net) a quitté (Ping timeout: 255 seconds) 2019-02-26 13:30:29 <-- electronicboy (~electroni@atlas.valaria.pw) a quitté (Ping timeout: 255 seconds) 2019-02-26 13:30:29 <-- masterdonx (~mas@162.243.120.25) a quitté (Ping timeout: 255 seconds) 2019-02-26 13:30:30 <-- killme (~killmePI@185.9.253.124) a quitté (Ping timeout: 255 seconds) 2019-02-26 13:30:39 --> MasterdonY (~mas@162.243.120.25) a rejoint #mcdevs 2019-02-26 13:35:02 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 250 seconds) 2019-02-26 13:39:25 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-02-26 14:04:37 --> Craftplacer_ (~Craftplac@p200300F813D249ABA8DDC607942BA6C2.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-26 14:08:18 <-- Craftplacer (~Craftplac@p200300F813D24924793CB0694AAF3193.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-02-26 14:10:10 -- killmePI est maintenant connu sous le nom killme 2019-02-26 14:44:12 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-02-26 15:01:08 --> Craftplacer (~Craftplac@p200300F813D249ABA8DDC607942BA6C2.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-26 15:04:42 <-- Craftplacer_ (~Craftplac@p200300F813D249ABA8DDC607942BA6C2.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-02-26 15:12:27 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-02-26 15:35:40 --> Craftplacer_ (~Craftplac@p200300F813D249ABA8DDC607942BA6C2.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-26 15:38:54 <-- Craftplacer (~Craftplac@p200300F813D249ABA8DDC607942BA6C2.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-02-26 15:51:02 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Quit: Leaving) 2019-02-26 15:52:39 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-02-26 16:59:48 -- some02 est maintenant connu sous le nom sudden 2019-02-26 21:23:42 --> blackdog476 (~notquasse@2a01:4f8:200:11e1::2) a rejoint #mcdevs 2019-02-26 21:26:34 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Quit: Leaving) 2019-02-26 22:25:38 <-- takenbacon_ (~takenbaco@c-98-246-68-121.hsd1.wa.comcast.net) a quitté (Read error: Connection reset by peer) 2019-02-26 22:30:14 --> takenbacon (~takenbaco@c-98-246-68-121.hsd1.wa.comcast.net) a rejoint #mcdevs 2019-02-26 23:57:33 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-02-26 23:57:55 <-- Unarelith_ (~Quent4234@40.238.7.109.rev.sfr.net) a quitté (Remote host closed the connection) 2019-02-26 23:58:14 --> Unarelith_ (~Quent4234@40.238.7.109.rev.sfr.net) a rejoint #mcdevs 2019-02-27 03:44:41 --> KernelFreeze (kernel@wikimedia/KernelFreeze) a rejoint #mcdevs 2019-02-27 04:06:49 --> Unarelith (~Quent4234@40.238.7.109.rev.sfr.net) a rejoint #mcdevs 2019-02-27 04:07:41 <-- Unarelith_ (~Quent4234@40.238.7.109.rev.sfr.net) a quitté (Ping timeout: 255 seconds) 2019-02-27 06:18:40 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-02-27 06:20:46 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 268 seconds) 2019-02-27 06:20:46 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-02-27 07:50:01 x10A94 Wait, does minecraft use unix sockets for local connections? 2019-02-27 07:50:42 timmyRS Whut 2019-02-27 07:50:46 x10A94 at least the class that complained is listed as io.netty.channel.unix.FileDescriptor 2019-02-27 08:00:47 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-02-27 08:44:12 <-- Unarelith (~Quent4234@40.238.7.109.rev.sfr.net) a quitté (Ping timeout: 245 seconds) 2019-02-27 11:56:13 -- saper_ est maintenant connu sous le nom saper 2019-02-27 13:07:10 --> tachyon_ (5bc768f4@gateway/web/cgi-irc/kiwiirc.com/ip.91.199.104.244) a rejoint #mcdevs 2019-02-27 13:46:59 <-- tachyon_ (5bc768f4@gateway/web/cgi-irc/kiwiirc.com/ip.91.199.104.244) a quitté (Remote host closed the connection) 2019-02-27 14:42:49 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Remote host closed the connection) 2019-02-27 14:45:59 --> kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a rejoint #mcdevs 2019-02-27 14:46:05 -- Mode #mcdevs [+v kev009] par ChanServ 2019-02-27 15:39:10 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-02-27 16:23:09 PolarizedIons *beep boop* 19w09a has been released 2019-02-27 16:23:30 timmyRS >:( 2019-02-27 16:23:51 * PolarizedIons waves at timmyRS 2019-02-27 16:23:56 PolarizedIons Sowwy, I'll stop 2019-02-27 16:24:06 PolarizedIons Bloc post: https://minecraft.net/en-us/article/minecraft-snapshot-19w09a 2019-02-27 16:24:10 timmyRS You're taking our jobs!!! 2019-02-27 16:25:02 Not-e6c6 [New-Mc-Version] Minecraft snapshot 19w09a has just been released! 2019-02-27 16:25:25 timmyRS I wonder if a US server would be able to beat you 2019-02-27 16:26:15 PolarizedIons The bot is hosted an ovh in Canada, so maaaaybe 2019-02-27 16:26:49 PolarizedIons my bot* 2019-02-27 16:27:03 timmyRS I wonder if they're using Amazon AWS or Azure because they're MS and all 2019-02-27 16:33:33 Not-e6c6 [Burger] New data now avaliable for 19w09a: 2019-02-27 16:33:34 Not-e6c6 [Burger] Diff from 19w08b: https://pokechu22.github.io/Burger/diff_19w08b_19w09a.html (https://pokechu22.github.io/Burger/diff_19w08b_19w09a.json) 2019-02-27 16:33:36 Not-e6c6 [Burger] Full data: https://pokechu22.github.io/Burger/19w09a.html (https://pokechu22.github.io/Burger/19w09a.json) 2019-02-27 16:42:32 <-- saper (saper@wikipedia/saper) a quitté (Ping timeout: 245 seconds) 2019-02-27 18:00:39 <-- rtjure (~rtjure@87.246.31.42) a quitté (Quit: ZNC 1.6.5 - http://znc.in) 2019-02-27 18:05:11 AlexNagy moarcowbell 2019-02-27 18:10:29 PolarizedIons *clonk* 2019-02-27 18:40:59 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Quit: Leaving) 2019-02-27 20:20:09 rom1504 timmyRS: just cron every 5s, you'll surely beat him 2019-02-27 20:46:59 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-02-27 21:00:28 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Remote host closed the connection) 2019-02-27 21:19:16 timmyRS rom1504, I cron every minute, but there is just inherit delay of ~2 minutes with the storage service. 2019-02-27 21:52:21 --> Mutter (~Mutter@2607:fb90:6488:9b5e:74e4:af12:f4c7:c3d4) a rejoint #mcdevs 2019-02-27 21:56:30 <-- Mutter (~Mutter@2607:fb90:6488:9b5e:74e4:af12:f4c7:c3d4) a quitté (Client Quit) 2019-02-27 22:54:14 --> barneygale (~barneygal@host86-130-229-144.range86-130.btcentralplus.com) a rejoint #mcdevs 2019-02-27 23:00:01 --> Craftplacer (~Craftplac@p200300F813D2493D19C13C85F656FDA9.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-27 23:00:24 <-- Craftplacer (~Craftplac@p200300F813D2493D19C13C85F656FDA9.dip0.t-ipconnect.de) a quitté (Client Quit) 2019-02-27 23:00:26 <-- Craftplacer_ (~Craftplac@p200300F813D249ABA8DDC607942BA6C2.dip0.t-ipconnect.de) a quitté (Quit: Leaving) 2019-02-27 23:00:52 --> Craftplacer (~Craftplac@p200300F813D2493D19C13C85F656FDA9.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-27 23:06:44 rom1504 What storage service ? 2019-02-27 23:07:52 timmyRS I don't know what they're using but it seems to take 2 minutes for its european slaves to get updated 2019-02-27 23:09:44 timmyRS Btw., did you get my PRs to minecraft-data, rom1504? 2019-02-27 23:32:31 <-- tktech (~tktech@ec2-52-70-105-60.compute-1.amazonaws.com) a quitté #mcdevs ("Leaving") 2019-02-27 23:32:42 --> tktech (~tktech@ec2-52-70-105-60.compute-1.amazonaws.com) a rejoint #mcdevs 2019-02-28 00:18:32 --> pvpctutorials (~skyrising@89.43.124.59) a rejoint #mcdevs 2019-02-28 00:19:19 <-- skyrising (~skyrising@89.43.124.59) a quitté (Ping timeout: 268 seconds) 2019-02-28 00:59:13 Not-e6c6 [minecraft-data] rom1504 pushed 2 commits to master [+0/-0/±4] https://git.io/fhNDm 2019-02-28 00:59:14 Not-e6c6 [minecraft-data] timmyrs 6cf29ab - Fix armor being stackable (fixes #223) 2019-02-28 00:59:16 Not-e6c6 [minecraft-data] rom1504 938890d - Merge pull request #226 from timmyrs/patch-armor Fix armor being stackable (fixes #223) 2019-02-28 01:00:09 Not-e6c6 [minecraft-data] rom1504 pushed 2 commits to master [+0/-0/±4] https://git.io/fhNDY 2019-02-28 01:00:10 Not-e6c6 [minecraft-data] timmyrs f36976a - Fix music disc display names 2019-02-28 01:00:12 Not-e6c6 [minecraft-data] rom1504 1c4be5f - Merge pull request #227 from timmyrs/patch-records Fix music disc display names 2019-02-28 01:01:54 timmyRS Where are the scripts for automatic generation anyway? I don't see them on minecraft-data. Am I blind? 2019-02-28 01:02:54 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-02-28 01:03:14 timmyRS Ah, I assume its those external extractor projects. :/ 2019-02-28 02:03:52 --> Craftplacer_ (~Craftplac@p200300F813D2493D19C13C85F656FDA9.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-28 02:07:06 <-- Craftplacer (~Craftplac@p200300F813D2493D19C13C85F656FDA9.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-02-28 05:58:22 <-- barneygale (~barneygal@host86-130-229-144.range86-130.btcentralplus.com) a quitté (Ping timeout: 245 seconds) 2019-02-28 06:16:32 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-02-28 06:19:28 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 250 seconds) 2019-02-28 06:19:29 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-02-28 06:26:09 <-- Craftplacer_ (~Craftplac@p200300F813D2493D19C13C85F656FDA9.dip0.t-ipconnect.de) a quitté (Ping timeout: 268 seconds) 2019-02-28 06:31:01 --> Craftplacer (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-28 08:59:13 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-02-28 09:55:51 --> Craftplacer_ (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-28 09:59:18 <-- Craftplacer (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-02-28 10:16:27 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-02-28 10:30:26 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-02-28 10:48:42 --> Melluh (50651ba0@gateway/web/cgi-irc/kiwiirc.com/ip.80.101.27.160) a rejoint #mcdevs 2019-02-28 10:48:52 <-- Thinkofname (~Think@thinkof.name) a quitté (Quit: Leaving) 2019-02-28 10:50:49 --> Thinkofname (~Think@5.135.185.23) a rejoint #mcdevs 2019-02-28 10:50:49 -- Mode #mcdevs [+v Thinkofname] par ChanServ 2019-02-28 11:07:39 <-- Melluh (50651ba0@gateway/web/cgi-irc/kiwiirc.com/ip.80.101.27.160) a quitté (Remote host closed the connection) 2019-02-28 11:25:22 --> Craftplacer (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-28 11:28:42 <-- Craftplacer_ (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-02-28 12:49:02 --> barneygale (~barneygal@host86-130-229-144.range86-130.btcentralplus.com) a rejoint #mcdevs 2019-02-28 12:55:02 <-- sudden (~lax@unaffiliated/laxask) a quitté (Ping timeout: 245 seconds) 2019-02-28 14:01:12 --> sudden (~lax@unaffiliated/laxask) a rejoint #mcdevs 2019-02-28 14:17:51 --> rtjure (~rtjure@87.246.31.42) a rejoint #mcdevs 2019-02-28 14:38:29 <-- sudden (~lax@unaffiliated/laxask) a quitté (Ping timeout: 258 seconds) 2019-02-28 14:45:41 --> sudden (~lax@unaffiliated/laxask) a rejoint #mcdevs 2019-02-28 16:06:09 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-02-28 17:26:59 --> tachyon_ (5bc768f4@gateway/web/cgi-irc/kiwiirc.com/ip.91.199.104.244) a rejoint #mcdevs 2019-02-28 18:21:17 <-- tachyon_ (5bc768f4@gateway/web/cgi-irc/kiwiirc.com/ip.91.199.104.244) a quitté (Remote host closed the connection) 2019-02-28 18:26:20 --> Craftplacer_ (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-02-28 18:27:56 <-- barneygale (~barneygal@host86-130-229-144.range86-130.btcentralplus.com) a quitté (Remote host closed the connection) 2019-02-28 18:29:54 <-- Craftplacer (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-02-28 20:15:27 <-- Tuxel (~tux@mailer.tuxelcode.de) a quitté (Ping timeout: 245 seconds) 2019-02-28 20:31:22 --> Tuxel (~tux@mailer.tuxelcode.de) a rejoint #mcdevs 2019-02-28 21:34:10 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Quit: Leaving) 2019-03-01 00:04:03 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-01 06:02:58 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-03-01 06:23:01 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-01 06:33:04 <-- matthewprenger (~matt@irc.prenger.co) a quitté (Quit: update time) 2019-03-01 06:42:19 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-03-01 06:50:15 --> matthewprenger (~matt@irc.prenger.co) a rejoint #mcdevs 2019-03-01 07:11:09 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-01 07:53:00 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-03-01 09:43:19 --> killmePI (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-03-01 09:43:24 <-- killme (~killmePI@185.9.253.124) a quitté (Ping timeout: 272 seconds) 2019-03-01 09:44:52 <-- _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a quitté (Ping timeout: 246 seconds) 2019-03-01 09:45:47 --> _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a rejoint #mcdevs 2019-03-01 13:18:22 <-- pvpctutorials (~skyrising@89.43.124.59) a quitté (Remote host closed the connection) 2019-03-01 15:37:52 --> skyrising (~skyrising@ppp-62-216-198-244.dynamic.mnet-online.de) a rejoint #mcdevs 2019-03-01 15:45:50 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-03-01 18:00:28 rom1504 Yeah 2019-03-01 18:00:54 rom1504 In particular we're using burger extractor lastly 2019-03-01 18:00:58 rom1504 For 1.13 2019-03-01 18:06:16 rom1504 If you want to solve that problem (post correction) I wanted to have a manual_corrections folder somewhere (in the extractor repo or in minecraft data or a third repo) and make a small program to merge that with the generated versions 2019-03-01 18:06:45 rom1504 It would make it possible to make as many post correction as necessary without losing the ability to automatically generate some new data 2019-03-01 18:07:00 rom1504 I think that's a good pattern 2019-03-01 18:08:02 rom1504 (of course fixing any bug in the automatic generator is also nice, but it's not always trivial) 2019-03-01 18:08:48 rom1504 timmyRS: are you using minecraft data for your php project ? Cool if you are ! Feel free to add your projects in minecraft data users in the readme ;) 2019-03-01 19:04:04 --> janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-01 19:40:42 <-- janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-01 19:49:15 --> janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-01 20:41:35 <-- takenbacon (~takenbaco@c-98-246-68-121.hsd1.wa.comcast.net) a quitté (Remote host closed the connection) 2019-03-01 20:41:49 --> takenbacon (~takenbaco@c-98-246-68-121.hsd1.wa.comcast.net) a rejoint #mcdevs 2019-03-01 21:16:56 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Quit: Leaving) 2019-03-01 22:02:54 <-- janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-01 23:43:14 --> NickG365_ (~NickG365@2607:5300:60:6e29:472:6425:3733:0) a rejoint #mcdevs 2019-03-01 23:45:09 --> GingerGeek (~Zed@2a03:b0c0:1:d0::8e:1000) a rejoint #mcdevs 2019-03-01 23:45:10 <-- GingerGeek (~Zed@2a03:b0c0:1:d0::8e:1000) a quitté (Changing host) 2019-03-01 23:45:10 --> GingerGeek (~Zed@unaffiliated/gingergeek) a rejoint #mcdevs 2019-03-01 23:47:24 --> DemonWav_ (~DemonWav@unaffiliated/demonwav) a rejoint #mcdevs 2019-03-01 23:51:27 --> AndrewPH_ (Butts@omega.classicube.net) a rejoint #mcdevs 2019-03-01 23:52:36 <-- Starz0r (~quassel@138.197.214.219) a quitté (*.net *.split) 2019-03-01 23:52:36 <-- DemonWav (~DemonWav@unaffiliated/demonwav) a quitté (*.net *.split) 2019-03-01 23:52:36 <-- Deaygo (Deaygo@i.let.this.bloody.dropbear.in) a quitté (*.net *.split) 2019-03-01 23:52:36 <-- AndrewPH (Butts@omega.classicube.net) a quitté (*.net *.split) 2019-03-01 23:52:37 <-- NickG365 (~NickG365@2607:5300:60:6e29:472:6425:3733:0) a quitté (*.net *.split) 2019-03-01 23:52:37 <-- GingerGeek_ (~Zed@unaffiliated/gingergeek) a quitté (*.net *.split) 2019-03-01 23:52:41 -- NickG365_ est maintenant connu sous le nom NickG365 2019-03-01 23:54:51 --> Deaygo (Deaygo@i.let.this.bloody.dropbear.in) a rejoint #mcdevs 2019-03-01 23:55:41 <-- Thinkofname (~Think@5.135.185.23) a quitté (Ping timeout: 255 seconds) 2019-03-01 23:58:31 --> Thinkofname (~Think@5.135.185.23) a rejoint #mcdevs 2019-03-01 23:58:31 -- Mode #mcdevs [+v Thinkofname] par ChanServ 2019-03-02 00:06:03 <-- yawkat (~yawkat@cats.coffee) a quitté (Quit: No Ping reply in 180 seconds.) 2019-03-02 00:07:05 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-03-02 01:59:06 --> Starz0r (~quassel@138.197.214.219) a rejoint #mcdevs 2019-03-02 02:18:30 timmyRS rom1504, I was planning on using it but I'm not quite there yet. Certainly will add it when I am tho :) 2019-03-02 03:27:41 --> charims (~quassel@wsip-24-234-28-130.lv.lv.cox.net) a rejoint #mcdevs 2019-03-02 03:37:00 --> Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a rejoint #mcdevs 2019-03-02 03:37:00 <-- Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a quitté (Changing host) 2019-03-02 03:37:00 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-03-02 03:56:20 <-- charims (~quassel@wsip-24-234-28-130.lv.lv.cox.net) a quitté (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 2019-03-02 03:57:01 --> charims (~quassel@wsip-24-234-28-130.lv.lv.cox.net) a rejoint #mcdevs 2019-03-02 06:16:16 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-03-02 06:17:32 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 245 seconds) 2019-03-02 06:17:32 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-03-02 07:08:07 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-02 07:08:35 Tknoguyfication okay.. over three months later and i'm going to try and figure out protocol encryption again 2019-03-02 07:08:36 Tknoguyfication wish me luck 2019-03-02 07:16:26 timmyRS Which language are you using? 2019-03-02 07:18:29 Tknoguyfication C# and Unity3D. I'm taking a look at a chat client to see how they're handling crypto and authentication 2019-03-02 07:18:43 Tknoguyfication I'm able to auth the user so far and get a token and session, just working on joining the server 2019-03-02 07:19:24 timmyRS You even have an example implementation to look at? It doesn't get any easier. 2019-03-02 07:29:41 Tknoguyfication unity has a tendency of making things 10x harder than they need to be lol. i'm so rusty with this code too. i'm hoping to get it working by the end of the night(or morning) 2019-03-02 07:30:32 timmyRS It's 07:30 2019-03-02 07:30:46 Tknoguyfication 10:30PM for me in the US 2019-03-02 07:30:58 Tknoguyfication 11:30 actually whoops 2019-03-02 07:31:46 timmyRS Well, that's plenty of tme 2019-03-02 07:31:48 timmyRS time* 2019-03-02 07:47:43 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-03-02 07:48:05 --> Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a rejoint #mcdevs 2019-03-02 07:48:05 <-- Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a quitté (Changing host) 2019-03-02 07:48:05 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-03-02 08:38:33 --> janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 09:14:05 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 2019-03-02 10:03:31 <-- charims (~quassel@wsip-24-234-28-130.lv.lv.cox.net) a quitté (Read error: Connection reset by peer) 2019-03-02 11:01:33 <-- janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a quitté (Ping timeout: 250 seconds) 2019-03-02 12:02:47 --> janis_ (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 12:02:47 --> janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 12:03:17 <-- janis (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a quitté (Client Quit) 2019-03-02 12:58:35 <-- dotStart (~Akkarin@hyperion.torchmind.com) a quitté (Remote host closed the connection) 2019-03-02 13:04:17 --> Akkarin (~Akkarin@hyperion.torchmind.com) a rejoint #mcdevs 2019-03-02 13:11:25 timmyRS So, how's it going, Tknoguyfication? 2019-03-02 13:18:03 <-- Craftplacer_ (~Craftplac@p200300F813C53D551C05B33697C2A1FB.dip0.t-ipconnect.de) a quitté (Ping timeout: 250 seconds) 2019-03-02 13:20:46 --> Craftplacer (~Craftplac@p4FF060CE.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 13:54:27 <-- janis_ (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a quitté (Ping timeout: 250 seconds) 2019-03-02 14:03:31 --> janis (~janis@p4FF7F368.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 14:03:35 --> janis_ (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 14:05:54 <-- janis (~janis@p4FF7F368.dip0.t-ipconnect.de) a quitté (Client Quit) 2019-03-02 14:40:45 <-- janis_ (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a quitté (Remote host closed the connection) 2019-03-02 14:43:15 --> janis_ (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 16:26:01 <-- __0x277F (~Hex@four.out.of.five.doctors.recommend.hex.lc) a quitté (Remote host closed the connection) 2019-03-02 16:26:34 <-- janis_ (~janis@p200300EDCF34C235211FCE3A4C129610.dip0.t-ipconnect.de) a quitté (Ping timeout: 258 seconds) 2019-03-02 18:07:20 --> janis_ (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 19:22:54 <-- janis_ (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Ping timeout: 258 seconds) 2019-03-02 20:23:36 Tknoguyfication timmyRS haha I fell asleep but I'm working on it now. Just going to revert my repo to before i started working on crypto and start from scratch haha 2019-03-02 20:24:12 --> janis_ (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 20:31:49 --> janis (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 20:31:50 <-- janis (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Client Quit) 2019-03-02 20:34:53 -- janis_ est maintenant connu sous le nom janisp 2019-03-02 20:34:58 -- janisp est maintenant connu sous le nom janis 2019-03-02 20:35:33 -- janis est maintenant connu sous le nom Evanry 2019-03-02 21:22:13 <-- Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Remote host closed the connection) 2019-03-02 21:22:32 --> Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-02 22:09:09 Tknoguyfication Got it to work! I hate crypto now 2019-03-02 22:24:36 <-- Luck (~Luck@2a01:4f8:1c0c:687a::1) a quitté (Ping timeout: 257 seconds) 2019-03-02 22:30:37 --> Luck (~Luck@static.85.81.69.159.clients.your-server.de) a rejoint #mcdevs 2019-03-02 22:37:23 <-- Luck (~Luck@static.85.81.69.159.clients.your-server.de) a quitté (Ping timeout: 255 seconds) 2019-03-02 22:48:13 --> Luck (~Luck@2a01:4f8:1c0c:687a::1) a rejoint #mcdevs 2019-03-02 22:59:29 <-- Luck (~Luck@2a01:4f8:1c0c:687a::1) a quitté (Ping timeout: 259 seconds) 2019-03-02 23:01:42 --> Luck (~Luck@static.85.81.69.159.clients.your-server.de) a rejoint #mcdevs 2019-03-02 23:19:42 <-- Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-02 23:25:03 <-- Luck (~Luck@static.85.81.69.159.clients.your-server.de) a quitté (Ping timeout: 245 seconds) 2019-03-02 23:40:03 --> Luck (~Luck@static.85.81.69.159.clients.your-server.de) a rejoint #mcdevs 2019-03-02 23:44:13 <-- Luck (~Luck@static.85.81.69.159.clients.your-server.de) a quitté (Ping timeout: 245 seconds) 2019-03-03 00:46:59 --> Luck (~Luck@static.85.81.69.159.clients.your-server.de) a rejoint #mcdevs 2019-03-03 01:09:49 --> Hex__ (~quassel@four.out.of.five.doctors.recommend.hex.lc) a rejoint #mcdevs 2019-03-03 01:10:23 -- Hex__ est maintenant connu sous le nom __0x277F 2019-03-03 01:18:24 <-- Jonathan- (~Jonathan@5.1.85.173) a quitté (Read error: Connection reset by peer) 2019-03-03 01:28:37 x10A94 So I'm assuming that in 1.13 the chunk format is the same as described on the wiki.vg page, just without the 4 data bits at the end of each block? 2019-03-03 01:30:25 +pokechu22 The chunk format article is mostly up to date, actually, with the only exception being the references to the 4 metadata bits 2019-03-03 01:31:09 +pokechu22 However, block IDs are different now due to the flattening, and it's important to remember that there are blocks with multiple states (though the flattening eliminated a lot of uses of states, too; states are now only used for things that don't persist into the inventory) 2019-03-03 01:31:10 x10A94 figured, ty 2019-03-03 01:32:11 +pokechu22 There _is_ one other change if you're porting a 1.12 implementation, which is that the direct format doesn't write any fields anymore, instead of writing a 0 that was ignored 2019-03-03 01:32:29 x10A94 I'm writing one from scratch 2019-03-03 01:33:01 +pokechu22 Everything should be good, then; if you run into issues let me know though :3 2019-03-03 01:33:13 x10A94 ty 2019-03-03 01:35:26 +pokechu22 Oh, right, I also generated some sample chunks a while back for 1.13.2; they might be helpful: https://gist.github.com/Pokechu22/0b89f928b381dede0387fe5f88faf8c0 (though I haven't actually done anything with that data yet; I meant to put it on the wiki but didn't get around to it) 2019-03-03 01:35:57 x10A94 Oh, I have my own stored. 2019-03-03 06:13:13 --> redstonehelper_ (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-03-03 06:15:01 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Ping timeout: 246 seconds) 2019-03-03 06:15:01 -- redstonehelper_ est maintenant connu sous le nom redstonehelper 2019-03-03 06:34:52 --> charims (~quassel@wsip-24-234-28-130.lv.lv.cox.net) a rejoint #mcdevs 2019-03-03 07:46:30 --> Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a rejoint #mcdevs 2019-03-03 07:46:30 <-- Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a quitté (Changing host) 2019-03-03 07:46:30 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-03-03 07:58:18 --> Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 08:07:58 <-- Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Quit: Leaving) 2019-03-03 08:14:45 --> janis (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 08:15:47 -- janis est maintenant connu sous le nom Evanry 2019-03-03 08:46:54 <-- redstonehelper (~redstoneh@unaffiliated/redstonehelper) a quitté (Quit: redstonehelper) 2019-03-03 09:13:11 <-- Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Ping timeout: 250 seconds) 2019-03-03 09:41:42 --> Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 10:29:18 <-- Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-03 10:57:00 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Read error: Connection reset by peer) 2019-03-03 12:04:32 --> anli (~anli@81-236-137-96-no279.tbcn.telia.com) a rejoint #mcdevs 2019-03-03 12:04:35 anli hi 2019-03-03 12:07:08 anli public void registerSounds(Register event) does not trigger for me, why not? https://github.com/AndersBillLinden/magic-wand-mod/blob/master/main/java/sounds/Sounds.java#L16 2019-03-03 12:08:27 timmyRS Wrong channel 2019-03-03 12:17:53 anli Sorry, which channel should it be? 2019-03-03 12:19:13 <-- anli (~anli@81-236-137-96-no279.tbcn.telia.com) a quitté #mcdevs ("Leaving") 2019-03-03 12:22:22 timmyRS The magic wand channel? 2019-03-03 13:42:02 --> Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 13:49:47 --> Unarelith (~Quent4234@static-176-158-117-112.ftth.abo.bbox.fr) a rejoint #mcdevs 2019-03-03 13:51:42 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-03-03 15:55:50 <-- Craftplacer (~Craftplac@p4FF060CE.dip0.t-ipconnect.de) a quitté (Read error: Connection reset by peer) 2019-03-03 16:58:58 --> janis_ (~janis@p200300EDCF34C27832ECB74D593C5E48.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 17:01:06 <-- Evanry (~janis@p200300EDCF34C2855D10DF39373FD182.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-03 17:06:54 timmyRS I've just encountered invalid JSON in a resource pack's blockstates and Minecraft just accepted it. Is it lenient? Does it ignore invalid files? 2019-03-03 17:08:10 timmyRS Nothing in the game output log. :/ 2019-03-03 17:10:35 timmyRS Looks like it's lenient 2019-03-03 17:23:27 --> janis__ (~janis@p200300EDCF34C25798261CD4E249958E.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 17:26:18 <-- janis_ (~janis@p200300EDCF34C27832ECB74D593C5E48.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-03 17:26:21 <-- janis__ (~janis@p200300EDCF34C25798261CD4E249958E.dip0.t-ipconnect.de) a quitté (Client Quit) 2019-03-03 18:04:03 +pokechu22 Some things are lenient; I thought they made it strict in 1.13ish though... 2019-03-03 18:04:54 timmyRS Seems like all JSON aspects of resource packs are parsed leniently 2019-03-03 18:05:04 timmyRS Probably because less tech savvy people are creating them 2019-03-03 18:08:46 <-- Unarelith (~Quent4234@static-176-158-117-112.ftth.abo.bbox.fr) a quitté (Remote host closed the connection) 2019-03-03 18:09:09 +pokechu22 RIP :/ -- I thought they did fix that because I remember seeing some horribly messed up packs that stopped working after an update 2019-03-03 18:10:38 timmyRS I tried messing up pack.mcmeta and blockstates json and still accepted it as valid 2019-03-03 18:10:52 timmyRS obviously, not messing it up totally unparsably 2019-03-03 18:59:11 +Amaranth Isn't gson's lenient mode basically just JSON5? 2019-03-03 19:14:54 timmyRS Isn't JSON5 basically just lenient JSON? 2019-03-03 21:16:20 --> Dadido3_ (~quassel@p200300D9DF21A700C92C4BF4398B22B5.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 21:19:27 <-- Dadido3 (~quassel@p200300D9DF21A70005DD85109F2F7C96.dip0.t-ipconnect.de) a quitté (Ping timeout: 268 seconds) 2019-03-03 21:25:25 --> Unarelith (~Quent4234@static-176-158-117-112.ftth.abo.bbox.fr) a rejoint #mcdevs 2019-03-03 22:13:19 --> Dadido3 (~quassel@p200300D9DF21A700C92C4BF4398B22B5.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-03 22:16:06 <-- Dadido3_ (~quassel@p200300D9DF21A700C92C4BF4398B22B5.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-03 22:54:15 <-- Unarelith (~Quent4234@static-176-158-117-112.ftth.abo.bbox.fr) a quitté (Remote host closed the connection) 2019-03-03 23:20:18 <-- Starz0r (~quassel@138.197.214.219) a quitté (Ping timeout: 252 seconds) 2019-03-03 23:21:12 --> Starz0r (~quassel@138.197.214.219) a rejoint #mcdevs 2019-03-04 00:09:38 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-04 00:44:08 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-04 02:44:49 <-- takenbacon (~takenbaco@c-98-246-68-121.hsd1.wa.comcast.net) a quitté (Read error: Connection reset by peer) 2019-03-04 03:04:55 <-- _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a quitté (Read error: Connection reset by peer) 2019-03-04 03:29:14 --> _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a rejoint #mcdevs 2019-03-04 04:52:25 Tknoguyfication What's the difference between Pitch and Head Pitch in the spawn mob packet? 2019-03-04 04:52:34 Tknoguyfication I assume pitch doesn't change and it's just the head? 2019-03-04 05:03:28 timmyRS I think they're the same for players but different for mobs. 2019-03-04 06:05:52 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Ping timeout: 245 seconds) 2019-03-04 07:49:04 <-- kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a quitté (Ping timeout: 246 seconds) 2019-03-04 08:07:33 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Ping timeout: 245 seconds) 2019-03-04 08:28:54 --> janispritzkau (~janisprit@smtpout.eepos.de) a rejoint #mcdevs 2019-03-04 08:29:57 -- janispritzkau est maintenant connu sous le nom Evanry 2019-03-04 08:40:23 <-- Evanry (~janisprit@smtpout.eepos.de) a quitté (Quit: Quit) 2019-03-04 08:40:30 --> Evanry (~Evanry@62.225.185.130) a rejoint #mcdevs 2019-03-04 12:53:46 --> Unarelith (~Quent4234@static-176-158-117-112.ftth.abo.bbox.fr) a rejoint #mcdevs 2019-03-04 12:54:24 <-- Unarelith (~Quent4234@static-176-158-117-112.ftth.abo.bbox.fr) a quitté (Remote host closed the connection) 2019-03-04 13:50:00 <-- SpaceManiac (~SpaceMani@c-67-172-121-111.hsd1.ca.comcast.net) a quitté (Ping timeout: 250 seconds) 2019-03-04 13:55:30 --> SpaceManiac (~SpaceMani@c-67-172-121-111.hsd1.ca.comcast.net) a rejoint #mcdevs 2019-03-04 13:55:30 -- Mode #mcdevs [+v SpaceManiac] par ChanServ 2019-03-04 17:00:03 <-- Evanry (~Evanry@62.225.185.130) a quitté (Ping timeout: 245 seconds) 2019-03-04 17:00:37 --> Evanry (~Evanry@x59cc99a3.dyn.telefonica.de) a rejoint #mcdevs 2019-03-04 17:11:42 <-- Evanry (~Evanry@x59cc99a3.dyn.telefonica.de) a quitté (Ping timeout: 245 seconds) 2019-03-04 17:11:58 --> Evanry (~Evanry@nexus.vfn-nrw.de) a rejoint #mcdevs 2019-03-04 17:26:07 <-- Evanry (~Evanry@nexus.vfn-nrw.de) a quitté (Ping timeout: 240 seconds) 2019-03-04 17:28:02 --> Evanry (~Evanry@x59cc99cf.dyn.telefonica.de) a rejoint #mcdevs 2019-03-04 17:46:27 <-- Evanry (~Evanry@x59cc99cf.dyn.telefonica.de) a quitté (Ping timeout: 240 seconds) 2019-03-04 18:05:36 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-04 18:25:39 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-03-04 18:49:47 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-04 18:50:26 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-04 20:28:56 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Read error: Connection reset by peer) 2019-03-04 20:30:11 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-04 20:37:32 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-04 20:38:08 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Read error: Connection reset by peer) 2019-03-04 20:38:21 --> Evanry (~Evanry@x59cc9a2a.dyn.telefonica.de) a rejoint #mcdevs 2019-03-04 20:42:27 <-- Evanry (~Evanry@x59cc9a2a.dyn.telefonica.de) a quitté (Ping timeout: 240 seconds) 2019-03-04 20:43:11 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-04 20:46:08 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Read error: Connection reset by peer) 2019-03-04 20:46:26 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-04 20:53:21 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Remote host closed the connection) 2019-03-04 21:06:36 <-- levifig (~levi@hakr.io) a quitté (Quit: Farewell) 2019-03-04 21:09:09 --> levifig (~levi@hakr.io) a rejoint #mcdevs 2019-03-04 22:39:02 <-- skyrising (~skyrising@ppp-62-216-198-244.dynamic.mnet-online.de) a quitté (Remote host closed the connection) 2019-03-04 22:39:22 --> skyrising (~skyrising@ppp-62-216-198-244.dynamic.mnet-online.de) a rejoint #mcdevs 2019-03-04 22:51:41 <-- RoboMWM (~RoboMWM@dim.sum.is.better.than.tacos.approved-by.robomwm.com) a quitté (Read error: Connection reset by peer) 2019-03-04 22:51:59 <-- Amaranth (~Amaranth@ubuntu/member/Amaranth) a quitté (Quit: Ping timeout (120 seconds)) 2019-03-04 22:52:02 --> RoboMWM (~RoboMWM@xn--rh8h.xn--13h07alb18952afak11dq1gkm46v.robomwm.com) a rejoint #mcdevs 2019-03-04 22:52:19 --> Amaranth (~Amaranth@ubuntu/member/Amaranth) a rejoint #mcdevs 2019-03-04 22:52:19 -- Mode #mcdevs [+v Amaranth] par ChanServ 2019-03-04 23:36:57 -- killmePI est maintenant connu sous le nom killme 2019-03-05 00:19:52 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-05 01:12:40 -- irc : déconnecté du serveur 2019-03-05 01:13:04 --> rom1504 (rom1504@rom1504.fr) a rejoint #mcdevs 2019-03-05 01:13:04 -- 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-03-05 01:13:04 -- Titre défini par tktech (~tktech@ec2-52-70-105-60.compute-1.amazonaws.com) le jeu., 11 mai 2017 00:28:31 2019-03-05 01:13:04 -- Canal #mcdevs : 110 pseudos (1 op, 10 voices, 99 normaux) 2019-03-05 01:15:03 -- Canal créé le lun., 06 déc. 2010 12:22:40 2019-03-05 01:23:11 <-- __0x277F (~quassel@four.out.of.five.doctors.recommend.hex.lc) a quitté (Remote host closed the connection) 2019-03-05 01:23:31 --> Hex__ (~Hex@four.out.of.five.doctors.recommend.hex.lc) a rejoint #mcdevs 2019-03-05 02:34:59 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 255 seconds) 2019-03-05 02:38:53 --> cc0 (~cc0@2a03:b0c0:0:1010::28:e001) a rejoint #mcdevs 2019-03-05 02:39:48 cc0 hello, which packet is sent by the client when requesting to open a chest/furnace/...? 2019-03-05 02:50:55 rom1504 cc0: https://github.com/PrismarineJS/mineflayer/blob/6ae68d3bc754ac165e658cd8c64ce32e22a1706f/lib/plugins/inventory.js#L103 2019-03-05 02:51:44 cc0 rom1504: thanks 2019-03-05 03:04:50 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-03-05 03:07:16 rom1504 cc0: if you have other such questions about which packets are used by the vanilla client, you could use https://github.com/PrismarineJS/node-minecraft-protocol/tree/master/examples/proxy 2019-03-05 03:07:31 rom1504 It displays all the packet from and to the vanilla client 2019-03-05 03:12:32 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 250 seconds) 2019-03-05 03:17:12 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-03-05 03:55:41 -- Hex__ est maintenant connu sous le nom __0x277F 2019-03-05 04:52:14 --> Technoguy (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-05 05:55:28 <-- Technoguy (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Quit: Leaving) 2019-03-05 05:55:32 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Quit: Leaving) 2019-03-05 05:55:41 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-05 05:58:12 Tknoguyfication This is some creepy shit right here https://u.technoguyfication.com/fs2/b644cb/82b352de2ccebb520013be403d5f6f6f.gif 2019-03-05 06:19:42 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Ping timeout: 252 seconds) 2019-03-05 06:44:09 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Read error: Connection reset by peer) 2019-03-05 06:45:25 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 06:49:27 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-05 06:49:37 --> kev009 (~kev009@ip72-222-200-117.ph.ph.cox.net) a rejoint #mcdevs 2019-03-05 06:49:37 -- Mode #mcdevs [+v kev009] par ChanServ 2019-03-05 06:50:11 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 07:40:27 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Read error: Connection reset by peer) 2019-03-05 07:40:47 --> Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 07:49:27 <-- Evanry (~Evanry@p200300EDCF34C23204BA3B2074E4058D.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-05 07:49:44 --> Evanry (~Evanry@x59cc9b8b.dyn.telefonica.de) a rejoint #mcdevs 2019-03-05 08:21:25 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-03-05 08:26:25 <-- _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a quitté (Ping timeout: 246 seconds) 2019-03-05 08:26:51 --> _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a rejoint #mcdevs 2019-03-05 08:30:56 <-- Evanry (~Evanry@x59cc9b8b.dyn.telefonica.de) a quitté (Ping timeout: 255 seconds) 2019-03-05 08:33:54 --> Evanry (~Evanry@smtpout.eepos.de) a rejoint #mcdevs 2019-03-05 08:38:09 <-- Evanry (~Evanry@smtpout.eepos.de) a quitté (Client Quit) 2019-03-05 09:03:14 timmyRS Wouldn't it be less confusing if "full chunk" were renamed to "new chunk"? 2019-03-05 10:08:00 --> bildramer1 (~bildramer@p2003004CEA0A9C00D41172C1EFA84350.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 10:08:26 <-- bildramer (~bildramer@p5B01029A.dip0.t-ipconnect.de) a quitté (Ping timeout: 268 seconds) 2019-03-05 10:39:09 <-- Grum (~grum@irc.grum.nl) a quitté (Quit: ZNC - http://znc.in) 2019-03-05 13:20:30 --> bildramer (~bildramer@p2003004CEA0E4000D41172C1EFA84350.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 13:20:54 <-- bildramer1 (~bildramer@p2003004CEA0A9C00D41172C1EFA84350.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-05 15:50:13 timmyRS I've set up an automated website with the data generated by the data generators at https://mcje.dev/data/ -- maybe adding it to https://wiki.vg/Data_Generators would be useful? 2019-03-05 15:53:48 --> Evanry (~Evanry@smtpout.eepos.de) a rejoint #mcdevs 2019-03-05 15:55:16 Evanry I've implemented the Protocol in TypeScript: https://gitlab.com/janispritzkau/mcproto 2019-03-05 15:57:37 --> bildramer1 (~bildramer@p2003004CEA0E400094F24F6F4D074092.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 16:01:03 <-- bildramer (~bildramer@p2003004CEA0E4000D41172C1EFA84350.dip0.t-ipconnect.de) a quitté (Ping timeout: 258 seconds) 2019-03-05 16:16:24 x10A94 Has anyone figured out if you can hide the hunger bar the same way you can hide the health bar? 2019-03-05 16:17:35 +Amaranth You can hide the health bar? 2019-03-05 16:17:45 +Amaranth I thought that was only via creative and spectator mode 2019-03-05 16:19:03 timmyRS How do you hide the health bar? 2019-03-05 16:58:24 <-- Evanry (~Evanry@smtpout.eepos.de) a quitté (Ping timeout: 252 seconds) 2019-03-05 17:47:36 --> Evanry (~Evanry@p200300EDCF34C215B4BC5ED07DA2538B.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 17:56:04 x10A94 Amaranth: set max health attribute to zero 2019-03-05 17:56:27 <-- Evanry (~Evanry@p200300EDCF34C215B4BC5ED07DA2538B.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-05 17:56:41 x10A94 On a vanilla server, this will really screw you over by not letting you respawn, but on a modified server it's perfectly valid 2019-03-05 17:56:56 --> Evanry (~Evanry@p200300EDCF34C215B4BC5ED07DA2538B.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 17:57:49 timmyRS I assume max health is changable because of potion effects but I don't think there are any potion effects to change hunger. 2019-03-05 17:58:40 x10A94 Not potion effects, attributes 2019-03-05 17:58:54 x10A94 iirc the potion effect can't decrease your health unless I'm misremembering 2019-03-05 17:59:18 timmyRS I know, but I mean there are potion effects which would change the max health 2019-03-05 17:59:27 x10A94 ah 2019-03-05 17:59:49 x10A94 Also when should I send the set compression packet? The wiki doesn't say anything about ordering 2019-03-05 18:00:43 timmyRS https://wiki.vg/Protocol#Login 2019-03-05 18:00:50 timmyRS Right before "Login Success" 2019-03-05 18:01:08 x10A94 Oh huh, I guess they have 3 separate graphs like this, and each of them is different 2019-03-05 18:01:10 x10A94 nice one 2019-03-05 18:01:19 x10A94 (other two in faq and encryption) 2019-03-05 18:01:34 x10A94 Thank you! 2019-03-05 18:03:04 timmyRS I assume it's not present in those two graphs because it's optional. So, technically, they're all valid. 2019-03-05 18:03:53 x10A94 Yeah, true 2019-03-05 18:12:47 <-- Evanry (~Evanry@p200300EDCF34C215B4BC5ED07DA2538B.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-05 18:13:06 --> Evanry (~Evanry@p200300EDCF34C215B4BC5ED07DA2538B.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 18:15:57 x10A94 welp, I gotta rewrite all of my handling to implement compression properly oops 2019-03-05 18:16:45 timmyRS How did you implement encryption? 2019-03-05 18:17:44 x10A94 Encryption was okay because there's no packet for it that the server has to send _immediately_ 2019-03-05 18:18:05 x10A94 I used an async channel to send packets to the client 2019-03-05 18:18:39 x10A94 Which is fine for an initial implementation, but not very good, especially that I lose access to the underlying codec 2019-03-05 18:19:43 x10A94 https://hyper.is-a.cat/gogs/x10A94/mcproto/src/master/src/server.rs < here's my (arguably kinda terrible) implementation 2019-03-05 18:20:22 --> janis (~Evanry@p200300EDCF34C21576C2B220C2DF8872.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 18:23:06 <-- Evanry (~Evanry@p200300EDCF34C215B4BC5ED07DA2538B.dip0.t-ipconnect.de) a quitté (Quit: Quit) 2019-03-05 18:23:23 -- janis est maintenant connu sous le nom Evanry 2019-03-05 18:40:23 <-- tassu (~tassu@tassu.me) a quitté (Quit: The Lounge - https://thelounge.chat) 2019-03-05 18:40:35 --> tassu (~tassu@tassu.me) a rejoint #mcdevs 2019-03-05 19:20:11 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-03-05 20:32:26 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-05 20:42:57 Tknoguyfication x10A94 I can probably help you with encryption, I just wrote my implementation this weekend so it's still fresh in my memory 2019-03-05 20:44:59 x10A94 Tknoguyfication: actually I got encryption to work nicely 2019-03-05 20:45:13 x10A94 it's compression that required a rewrite, which I just did, and it works much better now in general 2019-03-05 21:07:22 <-- Evanry (~Evanry@p200300EDCF34C21576C2B220C2DF8872.dip0.t-ipconnect.de) a quitté (Remote host closed the connection) 2019-03-05 21:09:51 x10A94 well, alright, now it gives me a more decent error message 2019-03-05 21:10:24 x10A94 which is "size of 120 below server threshold of 256", even though I never even sent any packets with that size 2019-03-05 21:11:09 x10A94 oh nvm I'm silly 2019-03-05 21:12:21 --> bildramer (~bildramer@p2003004CEA16C20094F24F6F4D074092.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-05 21:12:27 <-- bildramer1 (~bildramer@p2003004CEA0E400094F24F6F4D074092.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-05 21:13:14 x10A94 it works \o/ 2019-03-05 21:32:05 x10A94 well, it uses 10 times more CPU than bungee, but at least it works 2019-03-05 21:45:47 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Ping timeout: 240 seconds) 2019-03-06 00:07:47 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-06 01:01:10 <-- _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a quitté (Read error: Connection reset by peer) 2019-03-06 01:01:36 --> _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a rejoint #mcdevs 2019-03-06 01:31:18 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-03-06 01:37:44 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-06 01:38:32 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Client Quit) 2019-03-06 01:49:24 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-06 02:18:47 <-- PolarizedIons (~Polarized@unaffiliated/polarizedions) a quitté (Ping timeout: 240 seconds) 2019-03-06 02:25:39 --> PolarizedIons (~Polarized@unaffiliated/polarizedions) a rejoint #mcdevs 2019-03-06 04:09:29 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-06 06:27:27 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Ping timeout: 240 seconds) 2019-03-06 06:49:26 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-03-06 06:52:45 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-06 06:54:41 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-03-06 10:20:06 timmyRS At least you're not using PHP where you have to poll on encrypted streams :) 2019-03-06 12:09:56 x10A94 Apparently the client says "Timed out" every time a friend of mine moves a fishing rod inside his inventory 2019-03-06 12:09:59 x10A94 this isn't good 2019-03-06 12:10:41 timmyRS Have you implemented the heartbeat/keep alive? 2019-03-06 12:10:45 x10A94 yes 2019-03-06 12:11:04 x10A94 he can stay there for like 10 minutes and it'll be fine, then move a rod and it kicks him 2019-03-06 12:11:23 timmyRS Is he in survival mode? 2019-03-06 12:11:25 x10A94 Yes 2019-03-06 12:11:35 timmyRS It might be that the client expects a transaction confirmation 2019-03-06 12:11:48 x10A94 Yeah, but it routes packets to a vanilla server 2019-03-06 12:12:02 x10A94 I'm writing a proxy thing right now 2019-03-06 12:12:36 timmyRS You're proxying all packets? 2019-03-06 12:12:40 x10A94 Yes 2019-03-06 12:12:44 x10A94 Except for keepalives themselves 2019-03-06 12:14:51 x10A94 I don't have this issue, however. 2019-03-06 12:19:48 timmyRS Begs the question what differenciates you two. 2019-03-06 12:20:10 x10A94 hmm 2019-03-06 12:20:16 x10A94 I'll try to log in as him 2019-03-06 12:39:32 --> pvpctutorials (~skyrising@ppp-62-216-198-244.dynamic.mnet-online.de) a rejoint #mcdevs 2019-03-06 12:39:47 <-- skyrising (~skyrising@ppp-62-216-198-244.dynamic.mnet-online.de) a quitté (Ping timeout: 240 seconds) 2019-03-06 15:11:45 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-03-06 15:31:41 <-- killme (~killmePI@185.9.253.124) a quitté (Ping timeout: 255 seconds) 2019-03-06 15:32:00 --> killme (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-03-06 15:41:51 tyteen4a03 oo 2019-03-06 16:05:45 --> Raqbit (~Raqbit@unaffiliated/raqbit) a rejoint #mcdevs 2019-03-06 16:38:05 kashike uu 2019-03-06 16:38:39 MiniDigger aa 2019-03-06 16:39:03 Raqbit Hi! I am trying to encode VarInt's for creating a simple Server List Ping library in Go. Working with raw bytes isn't my strongest suit and I'm getting stuck: https://gist.github.com/Raqbit/0aeebd4e326be2c015301727609db5c1 . I'm trying to replicate the example pseudocode but it is getting into an infinite loop of adding 18 to the specified buffer 2019-03-06 16:39:03 Raqbit . Does anyone know what I'm doing wrong? Thanks! 2019-03-06 16:39:22 Raqbit *128 2019-03-06 16:40:27 Raqbit Example pseudocode on the wiki: https://wiki.vg/Protocol#VarInt_and_VarLong 2019-03-06 16:41:15 timmyRS I thought go doesn't have exceptions? 2019-03-06 16:43:28 Raqbit it does not, you do have the error type though, which a function will return if an error occurrs 2019-03-06 16:43:54 timmyRS What are your Unicode boxes always supposed to mean? 2019-03-06 16:45:08 Raqbit monospace 2019-03-06 16:45:19 timmyRS I see 2019-03-06 16:47:34 timmyRS `value` is never updated 2019-03-06 16:48:05 Raqbit aha, I see 2019-03-06 16:48:10 Raqbit I override temp insted 2019-03-06 16:48:13 Raqbit *instead 2019-03-06 16:51:02 Raqbit Yup, that did the trick 2019-03-06 16:51:11 Raqbit thanks! 2019-03-06 16:52:00 timmyRS No problem 2019-03-06 17:14:07 <-- bildramer (~bildramer@p2003004CEA16C20094F24F6F4D074092.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-06 17:14:13 --> bildramer1 (~bildramer@p2003004CEA16C20094F24F6F4D074092.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-06 18:28:46 cc0 Raqbit: https://pastebin.com/pvGPhrYy my go varint implementation that i wrote a few days ago (readVarInt also returns the count of bytes read because i need it at some point) 2019-03-06 18:42:03 Raqbit nice :) 2019-03-06 19:08:15 -- pvpctutorials est maintenant connu sous le nom skyrising 2019-03-06 19:59:23 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-06 20:50:07 --> Evanry (~Evanry@p200300EDCF34C210B82DE4541EF0745D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-06 20:52:21 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Quit: Leaving) 2019-03-06 20:56:15 Evanry I made a npm package for formatting, translating chat components. It includes the original translation file (en_us.json) of Minecraft. Is there a problem with the license or copyright? 2019-03-06 20:57:09 Evanry Here's the link: https://www.npmjs.com/package/mc-chat-format 2019-03-06 21:10:04 <-- Evanry (~Evanry@p200300EDCF34C210B82DE4541EF0745D.dip0.t-ipconnect.de) a quitté (Remote host closed the connection) 2019-03-06 21:10:41 --> Evanry (~Evanry@p200300EDCF34C210B82DE4541EF0745D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-06 21:46:24 <-- Evanry (~Evanry@p200300EDCF34C210B82DE4541EF0745D.dip0.t-ipconnect.de) a quitté (Remote host closed the connection) 2019-03-06 21:47:47 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Ping timeout: 240 seconds) 2019-03-06 21:49:07 --> Evanry (~Evanry@p200300EDCF34C210B82DE4541EF0745D.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-06 22:08:51 --> janis (~Evanry@p200300EDCF4FA468C2A89C0B7BA6928C.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-06 22:11:07 <-- Evanry (~Evanry@p200300EDCF34C210B82DE4541EF0745D.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-06 22:14:43 -- janis est maintenant connu sous le nom Evanry 2019-03-06 22:59:27 <-- Evanry (~Evanry@p200300EDCF4FA468C2A89C0B7BA6928C.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-06 23:07:01 --> Evanry (~Evanry@p200300EDCF4FA468C2A89C0B7BA6928C.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-07 00:08:07 <-- Evanry (~Evanry@p200300EDCF4FA468C2A89C0B7BA6928C.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-07 00:22:06 --> bildramer (~bildramer@p2003004CEA16C20014112BC7F70E1C35.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-07 00:23:27 <-- bildramer1 (~bildramer@p2003004CEA16C20094F24F6F4D074092.dip0.t-ipconnect.de) a quitté (Ping timeout: 240 seconds) 2019-03-07 01:59:55 --> Human (~Human@2605:e000:ab46:c200:8417:c676:673f:fee9) a rejoint #mcdevs 2019-03-07 02:04:27 <-- Human (~Human@2605:e000:ab46:c200:8417:c676:673f:fee9) a quitté (Ping timeout: 252 seconds) 2019-03-07 02:07:02 --> Human (~Human@2605:e000:ab46:c200:8417:c676:673f:fee9) a rejoint #mcdevs 2019-03-07 02:09:29 <-- Human (~Human@2605:e000:ab46:c200:8417:c676:673f:fee9) a quitté (Read error: Connection reset by peer) 2019-03-07 03:19:32 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Ping timeout: 255 seconds) 2019-03-07 04:10:42 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-07 04:17:54 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Ping timeout: 250 seconds) 2019-03-07 05:26:31 <-- killme (~killmePI@185.9.253.124) a quitté (*.net *.split) 2019-03-07 05:26:32 <-- Thinkofname (~Think@5.135.185.23) a quitté (*.net *.split) 2019-03-07 05:26:32 <-- MasterdonY (~mas@162.243.120.25) a quitté (*.net *.split) 2019-03-07 05:26:32 <-- Proximyst (~proximyst@proximyst.com) a quitté (*.net *.split) 2019-03-07 05:26:33 <-- chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a quitté (*.net *.split) 2019-03-07 05:26:33 <-- mrkirby153 (~mrkirby15@mrkirby153.com) a quitté (*.net *.split) 2019-03-07 05:26:34 <-- ashka (~postmaste@pdpc/supporter/active/ashka) a quitté (*.net *.split) 2019-03-07 05:26:34 <-- peterix (~peterix@quassel.woboq.com) a quitté (*.net *.split) 2019-03-07 05:26:34 <-- vemacs (~vemacs@unaffiliated/vemacs) a quitté (*.net *.split) 2019-03-07 05:53:38 --> killme (~killmePI@185.9.253.124) a rejoint #mcdevs 2019-03-07 05:53:38 --> Thinkofname (~Think@5.135.185.23) a rejoint #mcdevs 2019-03-07 05:53:38 --> MasterdonY (~mas@162.243.120.25) a rejoint #mcdevs 2019-03-07 05:53:38 --> Proximyst (~proximyst@proximyst.com) a rejoint #mcdevs 2019-03-07 05:53:38 --> chibill (~chibill@108-228-59-57.lightspeed.cicril.sbcglobal.net) a rejoint #mcdevs 2019-03-07 05:53:38 --> mrkirby153 (~mrkirby15@mrkirby153.com) a rejoint #mcdevs 2019-03-07 05:53:38 --> ashka (~postmaste@pdpc/supporter/active/ashka) a rejoint #mcdevs 2019-03-07 05:53:38 --> peterix (~peterix@quassel.woboq.com) a rejoint #mcdevs 2019-03-07 05:53:38 --> vemacs (~vemacs@unaffiliated/vemacs) a rejoint #mcdevs 2019-03-07 05:53:38 -- Mode #mcdevs [+v Thinkofname] par adams.freenode.net 2019-03-07 08:03:02 MiniDigger mmmmh 2019-03-07 08:03:21 MiniDigger I mean, its mojang property, so generally its a nono to distribute it 2019-03-07 08:03:48 MiniDigger however translation in particular are crowdsource so maybe there is a more permissive license for that? idk 2019-03-07 08:07:06 MiniDigger the safest way would be to get that file from the offical source and cache it somewhere 2019-03-07 08:07:55 MiniDigger buuuut iirc en_us is not in the asset index :D 2019-03-07 08:09:10 MiniDigger yeah, it isn't 2019-03-07 08:09:23 MiniDigger you can use http://resources.download.minecraft.net/6a/6a4e260a97756e2a8182a4ce24296323e64d23e3 to download the 1.14 en_gb file tho 2019-03-07 08:10:44 MiniDigger (if you don't know how to get such urls, https://launchermeta.mojang.com/mc/game/version_manifest.json (main file with all versions) -> https://launchermeta.mojang.com/v1/packages/c1c7dd946f1063943adc577cf9ccd941a83e1888/19w09a.json (file for latest snapshot) -> https://launchermeta.mojang.com/v1/packages/f97fe85940964a86d29fdb2d417d5fa93210c451/1. 2019-03-07 08:10:44 MiniDigger 14.json (asset index for that file) ->http://resources.download.minecraft.net/6a/6a4e260a97756e2a8182a4ce24296323e64d23e3 (download url for that file) 2019-03-07 08:10:53 MiniDigger https://wiki.vg/Game_files 2019-03-07 08:17:24 timmyRS Jesus, that article was full of outdated, striked-through information. Edited that to make it much easier to read. 2019-03-07 08:18:31 MiniDigger meh, I would argue it had its point since it told ppl to stop using the old stuff 2019-03-07 08:19:16 timmyRS I think people using the old stuff will realize they should stop using it when the version_manifest doesn't include the latest versions any more 2019-03-07 08:19:47 timmyRS And at the very latest, when everything breaks, when the old endpoints are finally offline 2019-03-07 08:20:27 timmyRS All jokes aside, the 1.13 is out for probably a year now, and it's not in that old version_manifest 2019-03-07 08:20:43 timmyRS If someone even maintaines their project once a year, it has been updated 2019-03-07 08:20:56 timmyRS If not, it's dustware and will never be updated. 2019-03-07 08:21:54 MiniDigger I bet plenty ppl still use the s3 urls to download client and server since they are easier 2019-03-07 08:22:20 MiniDigger I mean, you can tell just by the fact that they are not disabled yet 2019-03-07 08:23:06 timmyRS Maybe there's keeping it up forever? 2019-03-07 08:23:24 timmyRS I imagine storing those couple of MB costs less than 1€/mo 2019-03-07 08:23:41 MiniDigger bone said he wants to remove them by the end of last year 🤷‍♂️ 2019-03-07 08:24:06 MiniDigger since he didn't, I am assuming he either forgot/doesnt care, or there is still too much load on them and it would piss ppl off 2019-03-07 08:25:51 timmyRS https://github.com/search?q=%22https%3A%2F%2Fs3.amazonaws.com%2FMinecraft.Download%22&type=Code 2019-03-07 08:27:21 timmyRS From what I see here it's pretty much unmaintained county population 2000 2019-03-07 08:27:34 MiniDigger see, just look at all the dockerfiles that would break 2019-03-07 08:27:58 timmyRS which dockerfiles? 2019-03-07 08:29:02 MiniDigger https://github.com/search?l=Dockerfile&q=%22https%3A%2F%2Fs3.amazonaws.com%2FMinecraft.Download%22&type=Code 2019-03-07 08:30:10 MiniDigger or like ppl doing this https://github.com/nmarus/docker-minecraft/blob/a21698bd5d61cb91325e8b1f85950f7965e36bf7/start.sh#L40-L53 2019-03-07 08:31:26 timmyRS Yeah, but that's last updated 2015, and the latest version there is incurrate 2019-03-07 08:31:48 MiniDigger ideally there would be an easy rest api, like paper just got this: https://papermc.io/api/v1/paper/1.13/latest/download/ 2019-03-07 08:36:05 timmyRS Yeah. I've added a warning to the Game files article about the old endpoint, tho I think it's useless as the Github projects I saw are all dustware. 2019-03-07 08:37:49 MiniDigger > last indexed 22 days ago 2019-03-07 08:37:58 MiniDigger even supports 1.13, by hardcoding the url 😂 2019-03-07 08:37:59 MiniDigger https://github.com/bentsherman/minecraft-server/blob/8bbfebed811e7d377e804781159d5edf65169527/scripts/download.sh 2019-03-07 08:38:13 timmyRS oof 2019-03-07 08:55:44 Raqbit Interesting how WireShark does not have support for the Minecraft protocol but it does for MCPE 2019-03-07 08:56:26 Raqbit (Or bedrock, rather, the protocol in wireshark is called mcpe) 2019-03-07 08:56:39 --> Evanry (~Evanry@62.225.185.130) a rejoint #mcdevs 2019-03-07 08:59:35 +pokechu22 Is the MCPE protocol encrypted by default? I feel like it isn't, which would explain that 2019-03-07 08:59:45 +pokechu22 just judging off of what I've seen of raknet 2019-03-07 09:37:58 <-- yawkat (~yawkat@cats.coffee) a quitté (Ping timeout: 245 seconds) 2019-03-07 09:41:07 <-- Evanry (~Evanry@62.225.185.130) a quitté (Ping timeout: 240 seconds) 2019-03-07 09:44:35 --> yawkat (~yawkat@cats.coffee) a rejoint #mcdevs 2019-03-07 09:51:24 --> tachyon_ (d5e954f6@gateway/web/cgi-irc/kiwiirc.com/ip.213.233.84.246) a rejoint #mcdevs 2019-03-07 10:26:08 <-- tachyon_ (d5e954f6@gateway/web/cgi-irc/kiwiirc.com/ip.213.233.84.246) a quitté (Remote host closed the connection) 2019-03-07 11:13:45 --> Evanry (~Evanry@p4FF7FE10.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-07 11:53:39 --> Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a rejoint #mcdevs 2019-03-07 11:53:39 <-- Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a quitté (Changing host) 2019-03-07 11:53:39 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-03-07 12:08:10 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 2019-03-07 12:57:59 <-- Evanry (~Evanry@p4FF7FE10.dip0.t-ipconnect.de) a quitté (Remote host closed the connection) 2019-03-07 13:00:28 --> Evanry (~Evanry@62.225.185.130) a rejoint #mcdevs 2019-03-07 13:46:48 --> janis (~Evanry@p4FF7FE10.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-07 13:47:18 <-- Evanry (~Evanry@62.225.185.130) a quitté (Ping timeout: 250 seconds) 2019-03-07 13:50:06 --> Evanry (~Evanry@62.225.185.130) a rejoint #mcdevs 2019-03-07 13:50:06 <-- janis (~Evanry@p4FF7FE10.dip0.t-ipconnect.de) a quitté (Read error: Connection reset by peer) 2019-03-07 13:50:24 <-- Evanry (~Evanry@62.225.185.130) a quitté (Remote host closed the connection) 2019-03-07 13:55:28 --> Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a rejoint #mcdevs 2019-03-07 13:55:28 <-- Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a quitté (Changing host) 2019-03-07 13:55:28 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-03-07 14:44:38 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-03-07 15:07:50 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-03-07 20:06:23 --> badepe (~badepe@BC246DB2.dsl.pool.telekom.hu) a rejoint #mcdevs 2019-03-07 20:27:52 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Remote host closed the connection) 2019-03-07 21:14:52 --> PLG (9eae718c@h-113-140.A444.priv.bahnhof.se) a rejoint #mcdevs 2019-03-07 21:15:10 PLG Hello all. 2019-03-07 21:15:32 PLG I'm interested to know if someone can help me with a mc protocol question. 2019-03-07 21:16:00 timmyRS Sorry, this is the cooking IRC channel. No "mc protocol" 2019-03-07 21:17:21 PLG "A haunt for developers working on projects related to Minecraft". 2019-03-07 21:17:36 timmyRS Yes, I was making a joke. 2019-03-07 21:18:08 timmyRS Go ahead, ask your question. 2019-03-07 21:18:45 PLG I will shoot. The code for the Login procedure says an EncryptionRequest follows a LoginStart. But, if the server is in offline mode, then it should just skip that. 2019-03-07 21:19:11 PLG I'm trying to figure out what tells the client to skip expecting the EncryptionRequest. 2019-03-07 21:19:26 PLG cheers. I should have read the rules first, duh. 2019-03-07 21:20:29 +pokechu22 I'm pretty sure you just send login success and it's good to go; let me double check that 2019-03-07 21:21:07 PLG Using Forge, the EnumConnectionState class says: SPacketDisconnect, SPacketEncryptionRequest, SPacketLoginSuccess ... 2019-03-07 21:22:02 PLG But, when I debug, code throws an error when it receives a LoginSuccess instead of a EncryptionRequest. 2019-03-07 21:22:05 +pokechu22 EnumConnectionState defines the list of packets in each state -- where state is "handshaking", "login", "play", or "status" (not exactly in that order I think) 2019-03-07 21:22:13 timmyRS You just follow the login start packet with a login success using a UUIDv4 and the provided username 2019-03-07 21:22:25 PLG Yeah, I do that. 2019-03-07 21:22:34 timmyRS But..? 2019-03-07 21:22:48 PLG I get this: [20:55:21] [Client thread/INFO]: Upstream server disconnected: Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Packet 2/0 (SPacketDisconnect) was larger than I expected, found 42 bytes extra whilst reading packet 0 2019-03-07 21:23:09 timmyRS Then you're probably sending something wrong. 2019-03-07 21:23:21 timmyRS Mind sending over a TCPdump? 2019-03-07 21:23:46 +pokechu22 Which Minecraft version are you using? 2019-03-07 21:24:02 PLG The server never sent the EncryptionRequest since it is an offline server. It seems the Decoder expects EncryptionRequest but is decoding the LoginSuccess wrong. 2019-03-07 21:24:28 PLG When I remove SPacketDisconnect, SPacketEncryptionRequest, from EnumConnectionState::LOGIN, it doesn't throw. 2019-03-07 21:24:34 PLG 1.12. 2019-03-07 21:24:43 timmyRS Sorry, what exactly are you programming? A server or a client? 2019-03-07 21:25:15 PLG proxy server and client. 2019-03-07 21:25:27 +pokechu22 Alright, make sure you're using the 1.12 page (https://wiki.vg/index.php?title=Protocol&oldid=14204) and not the current one which is for 1.13... though in this case it shouldn't matter. In some of the 1.13 snapshots login plugin request had a different ID and that shifted things, but it doesn't apply here I think 2019-03-07 21:26:01 timmyRS And your custom client is having an issue with the login? 2019-03-07 21:26:51 PLG For the moment, I am just forwarding packets that I get from an authentic client. 2019-03-07 21:27:14 PLG I will see if I can get you a tcpdump. 2019-03-07 21:27:29 timmyRS And the authentic client is having that issue when connecting to your proxy? 2019-03-07 21:29:26 PLG Yes, 2019-03-07 21:29:54 +pokechu22 The error you're getting says that it's getting a malformed disconnect packet (the 2 indicates login, 0 indicates the actual packet ID). 42 extra bytes on it seems particularly odd since both of them start with a string (of a sort at least) and the second string on login success would normally only be 16 chars at max 2019-03-07 21:29:57 PLG The full explanation is a bit longer. 2019-03-07 21:30:09 timmyRS I assume your proxy is trying to get the client to authenticate with the proxy? 2019-03-07 21:30:24 PLG What I have so far.... 2019-03-07 21:31:40 PLG authentic client connects to downstream component. That component forward packets to upstream component via custom protocol. Upstream component forwards the packet to an authentic server. When I go backward downstream to the client, I get the throw. 2019-03-07 21:32:06 PLG Works fine for the PING. 2019-03-07 21:32:17 PLG The STATUS, I mean. 2019-03-07 21:32:18 timmyRS And all you do is proxy packets from an authentic client to an authentic server and back? 2019-03-07 21:32:28 PLG yes. 2019-03-07 21:32:38 PLG Like I said: When I remove SPacketDisconnect, SPacketEncryptionRequest, from EnumConnectionState::LOGIN, it doesn't throw. 2019-03-07 21:32:59 timmyRS Is your project open-source? 2019-03-07 21:33:44 PLG I was expecting the server to pass some info to the client on whether to skip the SPacketEncryptionRequest or not. 2019-03-07 21:34:04 timmyRS The server just sends Login Success 2019-03-07 21:34:11 PLG Where is the protocol login that says to the client whether the server is an online or offline server? 2019-03-07 21:34:40 timmyRS When the server immediately authenticates the client and skips the encryption request? 2019-03-07 21:35:35 PLG Yes, the server skips the SPacketEncryptionRequest, but how does the client know to skip it? 2019-03-07 21:35:54 timmyRS When it receives Login Success instead of an Encryption Request. 2019-03-07 21:36:07 PLG The packets listed in EnumConnectionState::LOGIN must be read in order, no? 2019-03-07 21:36:19 PLG Hmmmm. 2019-03-07 21:36:34 +pokechu22 No, the order in EnumConnectionState is only the order used to determine packet IDs 2019-03-07 21:36:37 timmyRS I mean, Encryption Request -> Encryption Response -> Login Success is important to be kept in order 2019-03-07 21:36:39 PLG Yes, my project is open-source, but not published anywhere yet. 2019-03-07 21:36:53 +pokechu22 (if the order in EnumConnectionState mattered for the other states, play would be very weird :P) 2019-03-07 21:37:14 timmyRS Usually, you can mess around with order, tho I wouldn't recommend it. 2019-03-07 21:37:15 PLG good point :P 2019-03-07 21:37:36 timmyRS Chunk Data is completely ignored when it comes after a teleport 2019-03-07 21:37:48 timmyRS So, yeah, keep that order 2019-03-07 21:37:55 PLG Hmmm. Then I have to figure out some other reason why the packet is corrupting during decode. 2019-03-07 21:38:20 +pokechu22 It does make some expectations about order (though the server does more of those), but those are found in net.minecraft.client.network.NetHandlerLoginClient and net.minecraft.network.NetHandlerLoginServer 2019-03-07 21:38:29 PLG Ok, well, thanks for clearing that up. I will keep debugging. 2019-03-07 21:38:39 timmyRS Wait, your proxy decodes and re-encodes the packets before forwarding them? 2019-03-07 21:39:17 PLG Yes, since I use the standard mojang code until I hit channelRead0. 2019-03-07 21:40:16 PLG so the downstream proxy uses the mojang code to talk to the authentic client. I intercept during channelRead0. 2019-03-07 21:40:36 timmyRS What exactly does your intercepting do? 2019-03-07 21:40:39 PLG In the NetworkManager. 2019-03-07 21:40:56 PLG The intercept takes the packet and sends it to the upstream component. 2019-03-07 21:41:03 PLG which is talking to the server. 2019-03-07 21:41:37 timmyRS Yes, but why create a proxy using Mojang's code? 2019-03-07 21:42:34 PLG Because, I need compatibility when the client talks to the proxy. I thought that would be the shortest way to building the bridge. 2019-03-07 21:43:26 timmyRS If you need compatibility then I think you'd be better off doing it yourself 2019-03-07 21:43:33 PLG authentic client <-> (mojang code) downstream component (custom) <-> (custom) upstream component (mojang) <-> authentic server. 2019-03-07 21:43:37 timmyRS And a self-made proxy is actually feasable 2019-03-07 21:43:59 PLG Hmmm. 2019-03-07 21:44:47 PLG So, you think I should drop the mojang code entirely? 2019-03-07 21:45:43 timmyRS That's your decision to make. Just saying that Mojang's code is not concerned about compatibility between versions. 2019-03-07 21:46:41 PLG I just thought I would get some work done for free by reusing their code when talking to the authentic instances. 2019-03-07 21:46:49 timmyRS Of course, if you really want to take the short path to building the bridge, just use Bungeecord :P 2019-03-07 21:47:32 PLG I looked at Bungeecord, but I don't think it suits my needs and it would be just as much work tweaking that code instead of Mojangs. 2019-03-07 21:48:19 timmyRS You can maybe have a look at https://wiki.vg/Library_List if you don't want to get too low-level on the Minecraft protocol. 2019-03-07 21:49:16 PLG Interesting hit: Phpcraft 2019-03-07 21:49:22 timmyRS That's mine :P 2019-03-07 21:49:55 PLG =))) 2019-03-07 21:50:05 PLG php proxy.php — A proxy allowing you to play as another account ??? 2019-03-07 21:50:19 PLG how does that work exactly> 2019-03-07 21:50:30 timmyRS You run it, authenticate, then connect to the proxy 2019-03-07 21:52:42 PLG So, you had to write the same proxy code for both dealing with client and server too? 2019-03-07 21:53:09 timmyRS No, Phpcraft is a library which I used in the proxy to do most of the protocol stuff 2019-03-07 21:53:51 PLG Ok, well, I think I have enough info to chew on for a while. 2019-03-07 21:54:22 timmyRS Feel free to dive into my PHP code. It's very well written :P 2019-03-07 21:54:29 PLG Thanks all. I felt quite isolated while coding. Nice to finally have found a place that has people code on the same level. 2019-03-07 21:54:39 PLG No doubt! =)) 2019-03-07 21:54:54 PLG I might take a look see. 2019-03-07 22:10:08 <-- PLG (9eae718c@h-113-140.A444.priv.bahnhof.se) a quitté (Remote host closed the connection) 2019-03-07 22:10:48 --> PLG (~plg@h-113-140.A444.priv.bahnhof.se) a rejoint #mcdevs 2019-03-07 22:11:08 Raqbit Is there an easy way to get the byte-size of a varint via the value? 2019-03-07 22:11:35 timmyRS If the first bit is a 1, there's a next byte. 2019-03-07 22:12:03 <-- PLG (~plg@h-113-140.A444.priv.bahnhof.se) a quitté (Client Quit) 2019-03-07 22:13:19 Raqbit Right, but that would mean I'd have to encode it first. Is there a way to get the size without encoding the varint? 2019-03-07 22:14:16 timmyRS Based on the size of the number probably 2019-03-07 22:15:02 Raqbit Context is that I'm trying to use a struct encoding library which has my custom types implement an interface which should return their encoded binary size. Looking if I can satisfy this interface without having to encode it (That would result in having to encode the varint twice: size & actual encoding) 2019-03-07 22:15:32 timmyRS Why would you even need the size before encoding it? 2019-03-07 22:17:14 --> PLG23 (~plg@h-113-140.A444.priv.bahnhof.se) a rejoint #mcdevs 2019-03-07 22:18:23 Raqbit Apparently it's used for allocation 2019-03-07 22:18:55 timmyRS Apparently? 2019-03-07 22:19:15 Raqbit Yes, that's what the documentation states 2019-03-07 22:19:29 timmyRS Which document? 2019-03-07 22:21:18 <-- PLG23 (~plg@h-113-140.A444.priv.bahnhof.se) a quitté (Client Quit) 2019-03-07 22:21:48 Raqbit The documentation of the struct encoding library I'm trying to use. (https://godoc.org/github.com/go-restruct/restruct#Sizer) 2019-03-07 22:22:17 Raqbit I might have to go look for a different library which has better support for dynamically sized encodings 2019-03-07 22:23:26 timmyRS Why would you even need a library for data structures as simple as Minecraft's in the first place? 2019-03-07 22:23:36 timmyRS VarInt is just another way of writing an integer of the network 2019-03-07 22:25:10 +pokechu22 You can either have a bunch of `>` checks (also `< 0`) or just do a loop that effectively writes it to count... but I don't think there's a cleaner way of doing it. Maybe logarithms, but that's probably overcomplicating it 2019-03-07 22:25:37 Raqbit Yes, but a library like that one could make it a lot easier to write packet definitions: Instead of having to write a function per packet, I can have the the library encode the packet based on the types. 2019-03-07 22:27:15 timmyRS I think using a library for that is a bit overkill 2019-03-07 22:37:26 <-- electroniccat (~electroni@atlas.valaria.pw) a quitté (Read error: Connection reset by peer) 2019-03-07 22:41:14 <-- bildramer (~bildramer@p2003004CEA16C20014112BC7F70E1C35.dip0.t-ipconnect.de) a quitté (Ping timeout: 258 seconds) 2019-03-07 22:42:00 --> bildramer (~bildramer@p5B010A55.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-07 23:12:17 --> electronicboy (~electroni@atlas.valaria.pw) a rejoint #mcdevs 2019-03-08 01:47:52 --> redstonehelper (~redstoneh@unaffiliated/redstonehelper) a rejoint #mcdevs 2019-03-08 02:01:00 <-- Thinkofname (~Think@5.135.185.23) a quitté (Quit: Leaving) 2019-03-08 02:03:33 --> Thinkofname (~Think@5.135.185.23) a rejoint #mcdevs 2019-03-08 02:03:33 -- Mode #mcdevs [+v Thinkofname] par ChanServ 2019-03-08 09:13:00 --> maybe0 (~plg@h-113-140.A444.priv.bahnhof.se) a rejoint #mcdevs 2019-03-08 10:30:05 --> Evanry (~Evanry@p4FF7FE10.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-08 10:38:18 Evanry This is probably as simple as a functional Minecraft chat server can get: https://gitlab.com/janispritzkau/mcproto/blob/master/examples/chat-server.ts 2019-03-08 10:42:00 timmyRS Define simple 2019-03-08 10:45:34 Evanry Minimal number of packets required and not many lines of code 2019-03-08 10:45:42 Evanry (with encryption) 2019-03-08 10:47:00 timmyRS Errg, well mcproto is a library which is used in that server 2019-03-08 10:48:03 timmyRS Of course, if we go by minimal packets with encryption then mcverify is probably the "simplest" because it disconnects directly after you join, but it also depends on a library: https://github.com/timmyrs/mcverify 2019-03-08 11:23:16 <-- Evanry (~Evanry@p4FF7FE10.dip0.t-ipconnect.de) a quitté (Ping timeout: 255 seconds) 2019-03-08 12:16:53 <-- Dykam (~Dykam@2a03:b0c0:0:1010::1c5:4001) a quitté (Remote host closed the connection) 2019-03-08 12:17:43 --> Dadido3_ (~quassel@p54A3A7D7.dip0.t-ipconnect.de) a rejoint #mcdevs 2019-03-08 12:20:27 <-- Dadido3 (~quassel@p200300D9DF21A700C92C4BF4398B22B5.dip0.t-ipconnect.de) a quitté (Ping timeout: 264 seconds) 2019-03-08 12:35:36 maybe0 timmyRS+pokechu22, last nights mystery about the packet being corrupted in the decoder has been solved. Due to my debug statement being on the wrong level, I missed the SPacketEnableCompression being sent. 2019-03-08 12:35:58 maybe0 Since, I didn't enable compression as a result, the next packet threw the error. 2019-03-08 12:37:32 timmyRS Poor Enable Compression packet :( 2019-03-08 12:38:16 maybe0 Always the forgotten one, I'm sure. 2019-03-08 13:34:46 <-- ashka (~postmaste@pdpc/supporter/active/ashka) a quitté (Ping timeout: 268 seconds) 2019-03-08 13:35:08 --> ashka (~postmaste@baptiste-huve.fr) a rejoint #mcdevs 2019-03-08 13:35:09 <-- ashka (~postmaste@baptiste-huve.fr) a quitté (Changing host) 2019-03-08 13:35:09 --> ashka (~postmaste@pdpc/supporter/active/ashka) a rejoint #mcdevs 2019-03-08 14:44:25 <-- ashka (~postmaste@pdpc/supporter/active/ashka) a quitté (Ping timeout: 255 seconds) 2019-03-08 14:56:19 --> ashka (~postmaste@baptiste-huve.fr) a rejoint #mcdevs 2019-03-08 14:56:19 <-- ashka (~postmaste@baptiste-huve.fr) a quitté (Changing host) 2019-03-08 14:56:19 --> ashka (~postmaste@pdpc/supporter/active/ashka) a rejoint #mcdevs 2019-03-08 15:21:51 --> AlexNagy (~jnagyjr@69.8.163.48) a rejoint #mcdevs 2019-03-08 16:41:28 <-- maybe0 (~plg@h-113-140.A444.priv.bahnhof.se) a quitté (Remote host closed the connection) 2019-03-08 17:06:00 <-- Morrolan (morrolan@znc.morrolan.ch) a quitté (Quit: Goodbye) 2019-03-08 17:08:23 --> Morrolan (morrolan@znc.morrolan.ch) a rejoint #mcdevs 2019-03-08 19:28:39 --> maybe0 (~plg@h-113-140.A444.priv.bahnhof.se) a rejoint #mcdevs 2019-03-08 20:24:11 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-03-08 20:56:39 <-- AlexNagy (~jnagyjr@69.8.163.48) a quitté (Quit: Leaving) 2019-03-08 22:28:43 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-08 22:44:07 <-- maybe0 (~plg@h-113-140.A444.priv.bahnhof.se) a quitté #mcdevs 2019-03-09 01:02:33 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Ping timeout: 245 seconds) 2019-03-09 03:17:10 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Ping timeout: 250 seconds) 2019-03-09 03:34:09 --> Me4502 (~Me4502@unaffiliated/me4502) a rejoint #mcdevs 2019-03-09 03:46:31 <-- Me4502 (~Me4502@unaffiliated/me4502) a quitté (Quit: My MacBook has gone to sleep. ZZZzzz…) 2019-03-09 03:59:49 -- 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-03-09 03:59:49 -- Titre défini par tktech (~tktech@ec2-52-70-105-60.compute-1.amazonaws.com) le jeu., 11 mai 2017 00:28:31 2019-03-09 05:05:45 <-- Starz0r (~quassel@138.197.214.219) a quitté (Ping timeout: 252 seconds) 2019-03-09 05:07:28 --> Starz0r (~quassel@138.197.214.219) a rejoint #mcdevs 2019-03-09 05:09:25 --> C4K3 (~C4K3@0127801301.0.fullrate.ninja) a rejoint #mcdevs 2019-03-09 05:47:07 <-- Pyker (pyker@pyker.net) a quitté (Quit: Quit) 2019-03-09 05:50:35 --> Pyker (pyker@pyker.net) a rejoint #mcdevs 2019-03-09 09:52:22 <-- rtjure (~rtjure@87.246.31.42) a quitté (Ping timeout: 250 seconds) 2019-03-09 09:54:20 --> rtjure (~rtjure@87.246.31.42) a rejoint #mcdevs 2019-03-09 10:39:14 <-- _MrGr33n_ (~None@BSN-142-194-111.static.siol.net) a quitté (Read error: Connection reset by peer) 2019-03-09 10:40:22 --> _MrGr33n_ (~None@2a00:ee2:2702:ee00:1519:6907:22b5:3e8c) a rejoint #mcdevs 2019-03-09 11:09:29 <-- _MrGr33n_ (~None@2a00:ee2:2702:ee00:1519:6907:22b5:3e8c) a quitté (Read error: Connection reset by peer) 2019-03-09 11:11:12 --> _MrGr33n_ (~None@2a00:ee2:2702:ee00:981:e9a6:9412:7f68) a rejoint #mcdevs 2019-03-09 12:06:41 <-- _MrGr33n_ (~None@2a00:ee2:2702:ee00:981:e9a6:9412:7f68) a quitté (Read error: Connection reset by peer) 2019-03-09 12:17:36 --> _MrGr33n_ (~None@2a00:ee2:2702:ee00:dce3:8709:f8cf:651e) a rejoint #mcdevs 2019-03-09 12:18:15 --> Dykam (~Dykam@37.139.10.7) a rejoint #mcdevs 2019-03-09 12:20:57 --> Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a rejoint #mcdevs 2019-03-09 12:20:57 <-- Me4502 (~quassel@167-179-190-91.a7b3be.bne.nbn.aussiebb.net) a quitté (Changing host) 2019-03-09 12:20:57 --> Me4502 (~quassel@unaffiliated/me4502) a rejoint #mcdevs 2019-03-09 12:25:41 <-- _MrGr33n_ (~None@2a00:ee2:2702:ee00:dce3:8709:f8cf:651e) a quitté (Read error: Connection reset by peer) 2019-03-09 12:27:01 --> _MrGr33n_ (~None@2a00:ee2:2702:ee00:9d9b:9246:8304:a732) a rejoint #mcdevs 2019-03-09 13:12:00 <-- Dykam (~Dykam@37.139.10.7) a quitté (Read error: Connection reset by peer) 2019-03-09 13:12:25 --> Dykam (~Dykam@37.139.10.7) a rejoint #mcdevs 2019-03-09 13:14:35 <-- Dykam (~Dykam@37.139.10.7) a quitté (Client Quit) 2019-03-09 13:24:06 --> Dykam_ (~Dykam@37.139.10.7) a rejoint #mcdevs 2019-03-09 13:38:03 -- Dykam_ est maintenant connu sous le nom Dykam 2019-03-09 14:37:36 <-- Me4502 (~quassel@unaffiliated/me4502) a quitté (Read error: Connection reset by peer) 2019-03-09 16:27:22 <-- _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a quitté (Quit: _123DMWM) 2019-03-09 16:28:59 --> millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a rejoint #mcdevs 2019-03-09 16:28:59 --> _123DMWM (~123DMWM@pool-96-252-55-56.bstnma.fios.verizon.net) a rejoint #mcdevs 2019-03-09 18:39:07 <-- millerti (~millerti@cpe-66-24-91-119.stny.res.rr.com) a quitté (Ping timeout: 240 seconds) 2019-03-09 18:40:31 <-- skyrising (~skyrising@ppp-62-216-198-244.dynamic.mnet-online.de) a quitté (Remote host closed the connection) 2019-03-09 18:40:47 --> skyrising (~skyrising@ppp-62-216-198-244.dynamic.mnet-online.de) a rejoint #mcdevs 2019-03-09 19:00:57 --> Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-09 19:01:16 --> Technoguy (~Hayden@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-09 19:02:01 <-- Technoguy (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Client Quit) 2019-03-09 19:04:26 <-- Tknoguyfication (~Hayden@75-167-41-151.phnx.qwest.net) a quitté (Client Quit) 2019-03-09 19:06:12 --> Tknoguyfication (~Hayden@2602:47:df69:d400:4dc7:38dc:7b84:bd75) a rejoint #mcdevs 2019-03-09 19:08:20 Tknoguyfication So I'm wondering if there could be any copyright disputes with what I'm doing. I'm rewriting the entire client in Unity3D and C#, and I'm not reusing or redistributing any assets from the game at all. And of course I require the user to sign in thru Mojang. Is there anything else I should do to cover my ass? 2019-03-09 19:08:34 Tknoguyfication Or any other legal disputes ^^ 2019-03-09 20:05:52 --> maybe0 (~plg@h-113-140.A444.priv.bahnhof.se) a rejoint #mcdevs 2019-03-09 20:07:22 +pokechu22 I wouldn't worry about it much; I'd mention that Minecraft is by mojang and probably that's about it. If you're not doing anything commercial there shouldn't be any problems; if you're doing something commercial they have more strict rules. Check https://account.mojang.com/terms#brand 2019-03-09 20:46:07 <-- Tknoguyfication (~Hayden@2602:47:df69:d400:4dc7:38dc:7b84:bd75) a quitté (Quit: Leaving) 2019-03-09 20:46:12 --> Technoguy (~Tknoguyfi@75-167-41-151.phnx.qwest.net) a rejoint #mcdevs 2019-03-09 21:01:08 -- Technoguy est maintenant connu sous le nom Tknoguyfication 2019-03-09 21:04:29 <-- csnxs (sean@unaffiliated/plussean) a quitté (Quit: I was wrong. It creeps up back; through coloured glass.) 2019-03-09 21:11:57 <-- EvilJStoker (jstoker@unaffiliated/jstoker) a quitté (Ping timeout: 252 seconds) 2019-03-09 21:14:22 --> EvilJStoker (jstoker@unaffiliated/jstoker) a rejoint #mcdevs 2019-03-09 21:14:54 --> csnxs (sean@unaffiliated/plussean) a rejoint #mcdevs 2019-03-09 21:24:47 <-- csnxs (sean@unaffiliated/plussean) a quitté (Quit: I was wrong. It creeps up back; through coloured glass.) 2019-03-09 21:27:20 --> csnxs (sean@unaffiliated/plussean) a rejoint #mcdevs 2019-03-09 21:31:02 <-- csnxs (sean@unaffiliated/plussean) a quitté (Client Quit) 2019-03-09 21:31:17 --> csnxs (~sean@unaffiliated/plussean) a rejoint #mcdevs 2019-03-09 21:53:47 <-- csnxs (~sean@unaffiliated/plussean) a quitté (Quit: I was wrong. It creeps up back; through coloured glass.) 2019-03-09 21:53:58 --> csnxs (sean@unaffiliated/plussean) a rejoint #mcdevs 2019-03-09 22:50:48 x10A94 So I have an issue where connecting through my custom proxy sometimes makes items not spawn. Is this a frequent bug? 2019-03-09 22:50:59 x10A94 Always fine in e.g. bungeecord. 2019-03-09 22:53:28 maybe0 How are people supposed to know if it is a frequent bug, if it is your own custom code? 2019-03-09 22:55:32 timmyRS Have you tried turning it off and on again? 2019-03-09 22:55:57 +pokechu22 By spawn, do you mean the dropped item entity or within the inventory? 2019-03-09 22:56:06 maybe0 I recognize a pattern of humor here timmyRS. 2019-03-09 22:58:37 +pokechu22 Oh, if it's an item drop entity, is there something like "item entity #### has no item" written in the log? I'd expect that to render as stone, but it is a vanilla thing or at least was in the past -- caused by missing entity metadata if I recall correctly 2019-03-09 23:03:19 +pokechu22 I'm not actually sure if that message is still logged, but it still could be a metadata issue in theory 2019-03-09 23:03:32 maybe0 I have a quick question. What does the client or server do when there is a network overload? drop packets? or something else? 2019-03-09 23:04:48 timmyRS Serve come, first served 2019-03-09 23:04:59 timmyRS First come, first served* I'm so done 2019-03-09 23:06:17 timmyRS Afaik, there's no special handling. It just deals with everything in order. 2019-03-09 23:07:51 x10A94 maybe0: frequent as in does this show up in a lot of naïve implementations. 2019-03-09 23:08:31 x10A94 pokechu22: it shows up on the vanilla server and does spawn in the world, the client just isn't aware of its existance until you pick it up 2019-03-09 23:09:22 +pokechu22 Do you see an animation with the item moving towards you as it's being picked up, or does it just suddenly appear in the inventory? 2019-03-09 23:09:51 x10A94 Yes, I do see the animation. 2019-03-09 23:10:21 x10A94 I can record this happening, it does this semi-consistently. 2019-03-09 23:10:49 +Amaranth Do you have the client console open? 2019-03-09 23:11:11 x10A94 Yes, and it prints nothing in there. 2019-03-09 23:11:26 +pokechu22 Alright, because of how the collect item packet works by moving the item entity towards you (https://wiki.vg/Protocol#Collect_Item), that means the client knows the item entity exists... but it's positioned in some weird place. I'd like to see video if possible 2019-03-09 23:11:58 +Amaranth Wait it's up to the client whether they pick the item up or not now? 2019-03-09 23:12:31 +pokechu22 No, that packet is sent from the server to start an animation... which is actually implemented as a particle effect internally, interestingly 2019-03-09 23:12:56 timmyRS and that packet only works if the client knows the item exists 2019-03-09 23:13:39 +Amaranth Ah yeah because it just has the entity id 2019-03-09 23:13:48 x10A94 https://hyper.is-a.cat/s/item-pickup.mp4 2019-03-09 23:14:02 x10A94 the first half of this is supremely laggy for whatever reason but it doesn't matter 2019-03-09 23:14:15 timmyRS Btw, "The server only checks for items to be picked up after each Player Position (and Player Position And Look) packet sent by the client." I think that was removed in 1.9 or so 2019-03-09 23:14:47 timmyRS Because my PHP client could pickup items on 1.13 but not in 1.8 when I threw something to it when it doesn't report movement 2019-03-09 23:15:35 <-- maybe0 (~plg@h-113-140.A444.priv.bahnhof.se) a quitté #mcdevs 2019-03-09 23:16:01 +pokechu22 Yeah, I feel like that might be wrong too, but I'm not 100% sure; it might accept any player-related packet (the look-only one and the ground-only one?) but even that seems odd 2019-03-09 23:16:29 timmyRS My client used to be pretty bare, so no Player packets at all 2019-03-09 23:16:33 x10A94 I mean, that would mean that every time someone threw something at you, you wouldn't be able to pick it up. 2019-03-09 23:16:40 x10A94 + unless you moved 2019-03-09 23:16:46 timmyRS reporting Player with just on ground every tick or so did the trick for picking up items 2019-03-09 23:16:53 timmyRS on 1.8 at least, in 1.13 it was not required 2019-03-09 23:17:03 +Amaranth We had patched various things to not be dependent on packets from the player in CraftBukkit, would be nice if vanilla was now too 2019-03-09 23:17:42 timmyRS picking up items at least is no longer be dependent on it 2019-03-09 23:19:43 +pokechu22 Oh, worth noting that arrows also use collect item (looking at the code)... I wonder if it can be used on all entities? 2019-03-09 23:19:43 x10A94 This is just a regular vanilla server patched to accept the UUID in the handshake packet. 2019-03-09 23:19:48 +Amaranth In the past you wouldn't lose air or take damage without movement packets either, meant you could do silly cheats but also meant if you had a network hiccup you'd just die all of the sudden as your client "spammed" the server with movement packets and it ticked your air down for each one until you drowned 2019-03-09 23:21:25 timmyRS That's also how "god mode" worked, so you regenerated real quick 2019-03-09 23:21:44 x10A94 I can also try making a packet dump, but I don't have every packet implemented 2019-03-09 23:21:53 timmyRS Aren't we all glad the clearly inferior 1.8 is no longer used? 2019-03-09 23:22:04 x10A94 Uh huh. 2019-03-09 23:22:54 +pokechu22 Hmm, closest thing I can find: https://bugs.mojang.com/browse/MC-111978 -- without steps to reproduce, but on vanilla 2019-03-09 23:23:12 +Amaranth To be fair those were things I fixed in CraftBukkit in either 1.6 or 1.7 so the people still playing 1.8 don't have that either :P 2019-03-09 23:23:22 x10A94 I have not seen this on bungeecord, though. 2019-03-09 23:23:24 x10A94 Unless I'm blind. 2019-03-09 23:24:05 +pokechu22 It might be some kind of weird timing-sensitive issue or something... though I'd hope not 2019-03-09 23:24:27 x10A94 That would be quite silly. 2019-03-09 23:24:34 timmyRS But I'm sure you're just relaying everything byte-per-byte, right? 2019-03-09 23:25:33 x10A94 -ish, I handle encryption and compression as well as translate a few chat packets 2019-03-09 23:25:48 x10A94 But other than that I don't even re-encode packets most of the time 2019-03-09 23:29:04 +pokechu22 Hm, looking further, the collect item packet is also used by vanilla for other entities collecting items (e.g. zombies, dolphins) -- not something I've ever noticed ingame but I didn't think to look for it 2019-03-09 23:29:06 x10A94 If I force a crash, does it give you any info about the state of the entity? 2019-03-09 23:29:41 +pokechu22 Yes 2019-03-09 23:29:49 +pokechu22 F3+C for 10 seconds to do that 2019-03-09 23:30:09 +pokechu22 Well, not about the state exactly, but it does give position among other things 2019-03-09 23:30:10 x10A94 hah, it does a countdown now 2019-03-09 23:30:53 x10A94 https://hyper.is-a.cat/s/item-crash.txt 2019-03-09 23:32:39 timmyRS "VanillaCord" I guess you're sticking with using Mojang code :/ 2019-03-09 23:32:43 x10A94 ok I have no idea why it gives you 243 entities instead of just the two I have in the world 2019-03-09 23:33:15 +pokechu22 amm is EntityItemFrame... and I don't see it listed in there. Hm. 2019-03-09 23:33:36 +pokechu22 https://bugs.mojang.com/browse/MC-121152... I thought they fixed that, huh 2019-03-09 23:33:50 x10A94 timmyRS: I dislike using spigot because it messes with some of the more obscure mechanics or bugs and I want it to be 100% authentic 2019-03-09 23:33:55 timmyRS But it's an item and not an item frame? 2019-03-09 23:34:11 timmyRS You're writing a proxy... 2019-03-09 23:34:12 x10A94 I can force another one without all the noise 2019-03-09 23:34:34 x10A94 timmyRS: I mean, yeah, but it's a general-purpose library 2019-03-09 23:34:37 +pokechu22 gah, EntityItem = amm, that was a mistake on my part. I'd passed over EntityItemFrame = amb but it was still in my mind 2019-03-09 23:35:59 x10A94 https://hyper.is-a.cat/s/item-crash-2.txt < huh, it says that there's only 1 entity 2019-03-09 23:36:15 x10A94 this is me logging in and dropping an item until it disappears 2019-03-09 23:39:00 +pokechu22 It's worth noting that there are actually several lists of entities; "Forced entities" is a HashSet of entities in the world, "Retry entities" is a spawn queue and can be ignored for the most part, and there's also entitiesById which isn't included on there but lists entities by entity id. 2019-03-09 23:39:33 +pokechu22 So... I think what that report shows is that the entity didn't get added to the main entity list used for rendering and stuff, but the fact that the collect item packet can find it indicates it was added into entitiesById 2019-03-09 23:39:51 x10A94 So this is a client bug, huh. 2019-03-09 23:40:33 +pokechu22 It's either a direct client bug or something your server is doing that exposes a client bug that wouldn't be hit in vanilla... but given that there is a report of something like that for vanilla, I think it might be a rare client bug 2019-03-09 23:42:48 +Amaranth if vanilla rarely or never hits it but your proxy regularly does then even if the client is doing things wrong the bug is in your proxy :D 2019-03-09 23:43:45 +pokechu22 There's one other entity list which has a size shown on F3, with the "all" label. I'm checking the video to see what happened with that... 2019-03-09 23:44:01 x10A94 Doesn't increment at all. 2019-03-09 23:44:23 x10A94 The P actually increments while the entity is being picked up, but everything else stays at 0. 2019-03-09 23:44:30 x10A94 (or 1, rather) 2019-03-09 23:44:57 x10A94 wait surely the item being picked up isn't a particle 2019-03-09 23:45:04 +pokechu22 It is, internally :D 2019-03-09 23:45:10 x10A94 holy shit lmao 2019-03-09 23:45:26 x10A94 surprised it has a bounding box though 2019-03-09 23:45:30 +pokechu22 It's somewhat sane in that it's a lightweight entity that needs to be ticked each frame and goes away after a bit 2019-03-09 23:46:00 +pokechu22 Ah, you see, it actually works by rendering the _real_ entity at a different position each frame, and _that_ is what has the bounding box... at least I think. 2019-03-09 23:46:11 +pokechu22 Same way that the guardian over your screen animation has a bounding box 2019-03-09 23:46:23 x10A94 Man, minecraft's internals sure are something. 2019-03-09 23:46:40 timmyRS What about the totem of dying animation? 2019-03-09 23:46:52 timmyRS undying* xD 2019-03-09 23:47:46 x10A94 Doesn't seem to have a hitbox shown 2019-03-09 23:47:51 +pokechu22 I haven't actually messed with that but I think it's also rendering an entity at offset positions... maybe? It's been a while since I looked into that and I don't think I've actually tested ingame at all... 2019-03-09 23:48:43 timmyRS I'd still love to be able to change the item shown in that animation for things like kit selection :D 2019-03-09 23:51:47 timmyRS ex.: https://storage.hell.sh/img/totem%20of%20undying.mp4 2019-03-09 23:56:03 x10A94 Doesn't happen with bungeecord at all. 2019-03-09 23:56:51 x10A94 The only thing I can think of is that it's miscompressing the packet and the client stops caring. 2019-03-09 23:57:10 x10A94 But I'm pretty sure the client would complain if the packet wasn't compressed properly? 2019-03-09 23:57:19 timmyRS Yes, it would disconnect 2019-03-09 23:58:05 +pokechu22 Can you log when spawn object, collect item, and Destroy Entities packets are going through your proxy? (I don't think the content of it will matter too much, though I guess logging the entity id might be helpful too if you've got parsers for them already) 2019-03-09 23:58:38 x10A94 Yeah, implementing the packets for me is as easy as declaring the struct fields. 2019-03-10 00:06:25 x10A94 pokechu22: https://hyper.is-a.cat/s/Zt387yQr.txt < the item was spawned 2 times and failed to spawn once 2019-03-10 00:09:51 +pokechu22 ... oh my, I forgot that the way that the client tells the server to drop the current item is with the player digging packet 2019-03-10 00:10:09 x10A94 yeah I was confused too at first 2019-03-10 00:10:12 x10A94 I should make that an enum 2019-03-10 00:10:57 +pokechu22 Probably that and player block placement should be renamed since they're a bit more general... but it's still messy 2019-03-10 00:12:30 +pokechu22 Nothing on that log looks particularly anomalous though 2019-03-10 00:14:43 x10A94 I'm quite confused as to why this would even happen 2019-03-10 00:15:57 +pokechu22 Yeah, it doesn't make any sense 2019-03-10 00:16:04 x10A94 Happens to a friend of mine as well. 2019-03-10 00:16:43 x10A94 But then again, maybe there's something else in my codec that drops packets for whatever reason, although I did make sure to panic on anything unexpected 2019-03-10 00:19:10 x10A94 ..But if it's rendered once the item gets picked up, surely the client received the packet about it spawning. It shows the correct block type, so 2019-03-10 00:19:11 +pokechu22 One possibility... and the only one that would make sense to me... is that it's a race condition between the item spawning and receiving its metadata. It looks like items remove themselves now if they haven't gotten metadata yet, which could mean a delay would cause it to be removed... but what exactly that kind of removal means I don't know 2019-03-10 00:19:41 x10A94 Hm. I don't think my proxy would rearrange packets at all? 2019-03-10 00:20:09 timmyRS I think he means that it might be too slow 2019-03-10 00:20:23 x10A94 I mean, idk, it's only twice slower than bungee 2019-03-10 00:20:26 +pokechu22 Yeah, it happens when the client ticks the item I think... but I don't know when that happens exactly 2019-03-10 00:21:15 +pokechu22 The spawn object packet is total jank anyways... especially since items _need_ metadata to make sense but that's a separate packet (it's not included in spawn object), yet spawn mob _does_ include the entity metadata with it 2019-03-10 00:21:42 x10A94 this is pretty weird 2019-03-10 00:22:37 +pokechu22 Can you add a sleep call when you receive entity metadata, delaying all packets by -- say -- a 10th of a second? 2019-03-10 00:23:01 x10A94 I can try, not sure how well it'd work given it's all async 2019-03-10 00:23:41 --> saper (saper@wikipedia/saper) a rejoint #mcdevs 2019-03-10 00:25:49 x10A94 Well, this sure is weird, huh. I saw the bounding box and then it disappeared 2019-03-10 00:25:59 x10A94 Otherwise, the item kinda snaps to its position 2019-03-10 00:28:15 x10A94 Adding a delay after SpawnObject makes it disappear consistently. Well, huh, I guess you were correct. Maybe I need to make buffering less aggressive? 2019-03-10 00:29:37 +pokechu22 Yeah, or do some janky buffering logic so that spawn object and the entity metadata packet right after it are always sent together... maybe. I'm not sure if that'd work for sure, though I think it would 2019-03-10 00:30:10 x10A94 yeeeah I don't think I wanna do that 2019-03-10 00:30:33 x10A94 I'm gonna try disabling all buffering on the TcpSocket entirely 2019-03-10 00:30:59 x10A94 TcpStream* 2019-03-10 00:34:47 x10A94 Hey look that worked 2019-03-10 00:34:55 x10A94 Thank you for your help! 2019-03-10 00:35:23 x10A94 The issue is that now I need to explicitly buffer my packets when I need to 2019-03-10 00:36:08 +pokechu22 Thanks for pointing this out too... it's a very interesting issue, and I'm guessing it _can_ still affect vanilla if you have a really bad connection (hence those reports) 2019-03-10 00:36:25 +Amaranth Time to update the jira ticket