2024-02-08 09:13:17	<--	BratishkaErik (fd46852e72@user/BratishkaErik) a quitté (Remote host closed the connection)
2024-02-08 09:13:58	<--	vismie (c8b263ae0e@2a03:6000:1812:100::fb8) a quitté (Remote host closed the connection)
2024-02-08 09:20:31	-->	caleb_ (ca329e08ca@user/ace) a rejoint #mcdevs
2024-02-08 09:20:41	-->	vismie (c8b263ae0e@2a03:6000:1812:100::fb8) a rejoint #mcdevs
2024-02-08 09:20:42	-->	BratishkaErik (fd46852e72@user/BratishkaErik) a rejoint #mcdevs
2024-02-08 15:50:23	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 264 seconds)
2024-02-08 16:33:52	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-09 12:51:40	-->	craftxbox (craftxbox@2001:bc8:650:730::1) a rejoint #mcdevs
2024-02-09 12:52:37	<--	snep (craftxbox@2001:bc8:650:730::1) a quitté (Ping timeout: 276 seconds)
2024-02-09 14:07:40	-->	parsa (~parsa@2a01:5ec0:d008:5115:c50:66b1:6ace:de07) a rejoint #mcdevs
2024-02-09 14:07:52	parsa	Hello There
2024-02-09 14:09:17	parsa	i have some questions about minecraft server protocol
2024-02-09 14:10:02	<--	parsa (~parsa@2a01:5ec0:d008:5115:c50:66b1:6ace:de07) a quitté (Client Quit)
2024-02-09 14:14:52	-->	Guest6 (~Guest6@2a01:5ec0:d008:5115:c50:66b1:6ace:de07) a rejoint #mcdevs
2024-02-09 14:14:57	Guest6	sex
2024-02-09 14:15:05	Guest6	i like sex
2024-02-09 14:15:15	<--	Guest6 (~Guest6@2a01:5ec0:d008:5115:c50:66b1:6ace:de07) a quitté (Client Quit)
2024-02-10 00:20:43	<--	caleb_ (ca329e08ca@user/ace) a quitté (Ping timeout: 256 seconds)
2024-02-10 00:20:58	-->	caleb_ (ca329e08ca@user/ace) a rejoint #mcdevs
2024-02-10 05:20:29	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 256 seconds)
2024-02-10 05:31:04	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-02-10 13:34:50	<--	TheTechRobo (~TheTechRo@2001:19f0:b001:3f:5400:3ff:fee8:e827) a quitté (Remote host closed the connection)
2024-02-10 19:40:34	-->	sdomi (~meow@sakamoto.pl) a rejoint #mcdevs
2024-02-10 20:37:04	<--	sdomi (~meow@sakamoto.pl) a quitté (Remote host closed the connection)
2024-02-10 20:38:12	-->	sdomi (~meow@sakamoto.pl) a rejoint #mcdevs
2024-02-11 01:12:45	<--	kennytv (~kennytv@2001:41d0:800:19:da::) a quitté (Quit: Ping timeout (120 seconds))
2024-02-11 01:19:52	-->	kennytv (~kennytv@2001:41d0:800:19:da::) a rejoint #mcdevs
2024-02-11 02:21:29	-->	MisterVector (~Vector@47.145.188.72) a rejoint #mcdevs
2024-02-11 03:02:10	-->	VectorTest (~Vector@47.145.188.72) a rejoint #mcdevs
2024-02-11 03:06:08	<--	MisterVector (~Vector@47.145.188.72) a quitté (Ping timeout: 256 seconds)
2024-02-11 16:36:55	-->	Geolykt (~Geolykt@IP-094046093245.static.medianet-world.de) a rejoint #mcdevs
2024-02-11 20:48:25	-->	TheTechRobo (~TheTechRo@2001:19f0:b001:3f:5400:3ff:fee8:e827) a rejoint #mcdevs
2024-02-11 21:02:58	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-02-12 02:04:28	<--	GingerGeek (~Zed@droplet.lon1.do.zed.fyi) a quitté (Quit: Follow ma Twitter: @GingerGeek)
2024-02-12 02:04:43	-->	GingerGeek (~Zed@droplet.lon1.do.zed.fyi) a rejoint #mcdevs
2024-02-12 02:05:18	<--	Dykam (Dykam@dykam.nl) a quitté (Remote host closed the connection)
2024-02-12 02:07:57	-->	Dykam (Dykam@dykam.nl) a rejoint #mcdevs
2024-02-12 03:18:08	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: ZacSharp)
2024-02-12 13:00:55	<--	Almtesh (~Almtesh@2001:bc8:3335:c1aa:7951:ec8e:b50c:5a74) a quitté (Quit: So long, and thanks for all the fish!)
2024-02-12 13:05:24	-->	Almtesh (~Almtesh@2001:bc8:3335:c1aa:7951:ec8e:b50c:5a74) a rejoint #mcdevs
2024-02-12 13:09:02	<--	lassipulkkinen (lassi@pulk.fi) a quitté (Quit: WeeChat 4.1.2)
2024-02-12 13:09:15	-->	lassipulkkinen (lassi@pulk.fi) a rejoint #mcdevs
2024-02-12 13:25:28	<--	kennytv (~kennytv@2001:41d0:800:19:da::) a quitté (Quit: Ping timeout (120 seconds))
2024-02-12 13:28:02	-->	kennytv (~kennytv@2001:41d0:800:19:da::) a rejoint #mcdevs
2024-02-12 15:30:52	<--	AndrewPH (~Andrew@chat.andrewph.org) a quitté (Quit: I'm leavin, oh I'm leavin!)
2024-02-12 15:35:00	-->	AndrewPH (~Andrew@192.99.161.11) a rejoint #mcdevs
2024-02-12 15:40:34	<--	bixilon (~bixilon@node-3.bixilon.de) a quitté (*.net *.split)
2024-02-12 15:41:19	-->	bixilon (~bixilon@node-3.bixilon.de) a rejoint #mcdevs
2024-02-12 16:29:16	<--	sdomi (~meow@sakamoto.pl) a quitté (Ping timeout: 255 seconds)
2024-02-12 17:07:08	-->	sdomi (~meow@sakamoto.pl) a rejoint #mcdevs
2024-02-12 22:40:28	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-02-13 00:03:36	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-02-13 00:07:32	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-02-13 00:33:52	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-02-13 00:34:06	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-02-13 02:32:32	-->	NoahvdAa7 (~NoahvdAa@user/noahvdaa) a rejoint #mcdevs
2024-02-13 02:33:20	-->	kelvium_ (~kelvium@89b5da81.kelvium.fun) a rejoint #mcdevs
2024-02-13 02:35:46	-->	Jack_Kerouac (~VIPPER@1463639-static.elnsmiaa.metronetinc.net) a rejoint #mcdevs
2024-02-13 02:40:24	<--	kelvium (~kelvium@89b5da81.kelvium.fun) a quitté (Ping timeout: 264 seconds)
2024-02-13 02:40:24	<--	VIPPER (~VIPPER@1463639-static.elnsmiaa.metronetinc.net) a quitté (Ping timeout: 264 seconds)
2024-02-13 02:40:24	<--	bswartz (~bswartz@user/bswartz) a quitté (Ping timeout: 264 seconds)
2024-02-13 02:40:25	<--	NoahvdAa (~NoahvdAa@user/noahvdaa) a quitté (Ping timeout: 264 seconds)
2024-02-13 02:40:30	--	NoahvdAa7 est maintenant connu sous le nom NoahvdAa
2024-02-13 02:46:15	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-02-13 02:49:08	-->	bswartz (~bswartz@136.56.188.37) a rejoint #mcdevs
2024-02-13 02:49:08	<--	bswartz (~bswartz@136.56.188.37) a quitté (Changing host)
2024-02-13 02:49:08	-->	bswartz (~bswartz@user/bswartz) a rejoint #mcdevs
2024-02-13 05:33:09	<--	kelvium_ (~kelvium@89b5da81.kelvium.fun) a quitté (Ping timeout: 255 seconds)
2024-02-13 05:33:24	-->	kelvium (~kelvium@89b5da81.kelvium.fun) a rejoint #mcdevs
2024-02-13 10:22:55	<--	The_Red_Freak (~The_Red_F@user/The-Red-Freak/x-5541572) a quitté (Quit: ZNC 1.9.x-nightly-20211006-bc540f5d - https://znc.in)
2024-02-13 10:23:23	-->	The_Red_Freak (~The_Red_F@user/The-Red-Freak/x-5541572) a rejoint #mcdevs
2024-02-13 17:20:28	<--	Jack_Kerouac (~VIPPER@1463639-static.elnsmiaa.metronetinc.net) a quitté (Ping timeout: 256 seconds)
2024-02-13 18:10:44	-->	VIPPER (~VIPPER@1463639-static.elnsmiaa.metronetinc.net) a rejoint #mcdevs
2024-02-14 00:47:13	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 264 seconds)
2024-02-14 00:58:00	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-02-14 14:28:37	<--	Kurt- (~KurtThiem@nc.thiemann.io) a quitté (Ping timeout: 264 seconds)
2024-02-14 14:31:18	-->	KurtThiemann (~KurtThiem@nc.thiemann.io) a rejoint #mcdevs
2024-02-14 14:35:51	<--	KurtThiemann (~KurtThiem@nc.thiemann.io) a quitté (Client Quit)
2024-02-14 14:41:15	-->	KurtThiemann (~KurtThiem@nc.thiemann.io) a rejoint #mcdevs
2024-02-14 14:47:50	<--	KurtThiemann (~KurtThiem@nc.thiemann.io) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-14 14:48:12	-->	KurtThiemann (~KurtThiem@nc.thiemann.io) a rejoint #mcdevs
2024-02-14 14:52:54	-->	iamzim (~iamzim@user/invaderzim) a rejoint #mcdevs
2024-02-14 15:05:23	-->	Kurt- (~KurtThiem@nc.thiemann.io) a rejoint #mcdevs
2024-02-14 15:05:37	<--	KurtThiemann (~KurtThiem@nc.thiemann.io) a quitté (Read error: Connection reset by peer)
2024-02-14 15:12:30	-->	KurtThiemann (~KurtThiem@nc.thiemann.io) a rejoint #mcdevs
2024-02-14 15:13:30	<--	Kurt- (~KurtThiem@nc.thiemann.io) a quitté (Read error: Connection reset by peer)
2024-02-14 15:45:10	<--	iamzim (~iamzim@user/invaderzim) a quitté #mcdevs
2024-02-14 17:10:02	-->	botifico (~botifico@montreal.tkte.ch) a rejoint #mcdevs
2024-02-14 17:10:04	botifico	[McUpdates] Minecraft snapshot 24w07a has just been published to the launcher!
2024-02-14 17:12:39	botifico	[Burger] New data now avaliable for 24w07a:
2024-02-14 17:12:42	botifico	[Burger] Diff from 24w06a: https://pokechu22.github.io/Burger/diff_24w06a_24w07a.html (https://pokechu22.github.io/Burger/diff_24w06a_24w07a.json)
2024-02-14 17:12:45	botifico	[Burger] Full data: https://pokechu22.github.io/Burger/24w07a.html (https://pokechu22.github.io/Burger/24w07a.json)
2024-02-14 20:35:33	<--	Thinkofname (~thinkthin@37.205.12.211) a quitté (Quit: Bridge terminating on SIGTERM)
2024-02-14 20:36:58	-->	Thinkofname (~thinkthin@37.205.12.211) a rejoint #mcdevs
2024-02-15 01:26:34	-->	xtex (250b76165c@2a03:6000:1812:100::12fc) a rejoint #mcdevs
2024-02-15 07:45:52	<--	yosafbridge (~yosafbrid@static.38.6.217.95.clients.your-server.de) a quitté (Quit: Leaving)
2024-02-15 07:51:32	-->	yosafbridge (~yosafbrid@static.38.6.217.95.clients.your-server.de) a rejoint #mcdevs
2024-02-15 08:08:18	-->	nkid00 (~nkid00@198.144.166.42) a rejoint #mcdevs
2024-02-15 11:07:56	<--	kelvium (~kelvium@89b5da81.kelvium.fun) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-15 11:08:14	-->	kelvium (~kelvium@89b5da81.kelvium.fun) a rejoint #mcdevs
2024-02-15 11:11:17	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 252 seconds)
2024-02-15 20:41:50	<--	nkid00 (~nkid00@198.144.166.42) a quitté (Quit: Konversation terminated!)
2024-02-15 21:37:45	--	craftxbox est maintenant connu sous le nom snep
2024-02-16 00:51:27	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 255 seconds)
2024-02-16 01:03:49	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-02-16 02:33:10	-->	Mateon2 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-02-16 02:34:15	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Ping timeout: 272 seconds)
2024-02-16 02:34:15	--	Mateon2 est maintenant connu sous le nom Mateon1
2024-02-16 02:39:38	-->	Mateon2 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-02-16 02:40:47	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Ping timeout: 252 seconds)
2024-02-16 02:40:47	--	Mateon2 est maintenant connu sous le nom Mateon1
2024-02-16 05:16:53	<--	snep (craftxbox@2001:bc8:650:730::1) a quitté (Ping timeout: 240 seconds)
2024-02-16 05:22:08	-->	craftxbox (craftxbox@2001:bc8:710:3215:dc00:ff:fe3f:5a1) a rejoint #mcdevs
2024-02-16 09:07:58	<--	VectorTest (~Vector@47.145.188.72) a quitté (Ping timeout: 268 seconds)
2024-02-16 10:02:13	-->	MisterVector (~Vector@47.145.186.13) a rejoint #mcdevs
2024-02-16 14:39:11	<--	Disconsented (~quassel@irc.disconsented.com) a quitté (Remote host closed the connection)
2024-02-16 14:41:51	-->	Disconsented (~quassel@irc.disconsented.com) a rejoint #mcdevs
2024-02-16 15:16:08	<--	bswartz (~bswartz@user/bswartz) a quitté (Remote host closed the connection)
2024-02-16 15:17:02	-->	bswartz (~bswartz@136.56.188.37) a rejoint #mcdevs
2024-02-16 15:17:02	<--	bswartz (~bswartz@136.56.188.37) a quitté (Changing host)
2024-02-16 15:17:02	-->	bswartz (~bswartz@user/bswartz) a rejoint #mcdevs
2024-02-16 20:55:07	<--	balrog (znc@user/balrog) a quitté (Quit: Bye)
2024-02-16 20:59:27	-->	balrog (znc@user/balrog) a rejoint #mcdevs
2024-02-16 21:15:43	<--	DigitalDragon (~digital@arto.servers.digitaldragon.dev) a quitté (Read error: Connection reset by peer)
2024-02-16 21:36:17	<--	bswartz (~bswartz@user/bswartz) a quitté (Ping timeout: 268 seconds)
2024-02-16 21:49:55	-->	bswartz (~bswartz@136.56.42.13) a rejoint #mcdevs
2024-02-16 21:49:55	<--	bswartz (~bswartz@136.56.42.13) a quitté (Changing host)
2024-02-16 21:49:55	-->	bswartz (~bswartz@user/bswartz) a rejoint #mcdevs
2024-02-16 23:48:04	-->	DigitalDragon (~digital@arto.servers.digitaldragon.dev) a rejoint #mcdevs
2024-02-17 02:12:05	<--	trimill (~trimill@mail.trimill.xyz) a quitté (Quit: WeeChat 3.6)
2024-02-17 06:09:33	<--	TkTech (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a quitté (Quit: Ping timeout (120 seconds))
2024-02-17 06:09:57	-->	TkTech (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a rejoint #mcdevs
2024-02-17 11:31:34	<--	MisterVector (~Vector@47.145.186.13) a quitté (Read error: Connection reset by peer)
2024-02-17 11:31:51	-->	MisterVector (~Vector@47.145.186.13) a rejoint #mcdevs
2024-02-17 12:20:49	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 264 seconds)
2024-02-17 12:21:29	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-02-18 01:24:33	<--	kennytv (~kennytv@2001:41d0:800:19:da::) a quitté (Quit: Ping timeout (120 seconds))
2024-02-18 01:34:13	-->	kennytv (~kennytv@2001:41d0:800:19:da::) a rejoint #mcdevs
2024-02-18 10:07:05	-->	TkTech0 (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a rejoint #mcdevs
2024-02-18 10:08:14	<--	TkTech (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a quitté (Ping timeout: 268 seconds)
2024-02-18 10:08:14	--	TkTech0 est maintenant connu sous le nom TkTech
2024-02-18 19:20:13	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-18 22:05:17	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-18 22:05:39	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-02-19 04:59:48	<--	MiniDigger09 (~MiniDigge@user/minidigger) a quitté (Quit: The Lounge - https://thelounge.chat)
2024-02-19 05:00:47	-->	MiniDigger09 (~MiniDigge@user/minidigger) a rejoint #mcdevs
2024-02-19 06:11:16	--	craftxbox est maintenant connu sous le nom snep
2024-02-19 10:05:24	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 255 seconds)
2024-02-19 12:03:46	<--	SpaceManiac (~SpaceMani@73.116.110.236) a quitté (Ping timeout: 268 seconds)
2024-02-19 12:06:11	-->	SpaceManiac (~SpaceMani@c-73-116-110-236.hsd1.ca.comcast.net) a rejoint #mcdevs
2024-02-19 14:33:21	-->	VectorTest (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-02-19 14:35:29	<--	MisterVector (~Vector@47.145.186.13) a quitté (Ping timeout: 256 seconds)
2024-02-19 14:48:26	--	caleb_ est maintenant connu sous le nom caleb
2024-02-19 15:11:35	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Quit: Mateon1)
2024-02-19 15:11:53	-->	Mateon1 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-02-19 15:13:37	<--	TheTechRobo (~TheTechRo@2001:19f0:b001:3f:5400:3ff:fee8:e827) a quitté (Ping timeout: 264 seconds)
2024-02-19 15:25:37	-->	TheTechRobo (~TheTechRo@2001:19f0:b001:3f:5400:3ff:fee8:e827) a rejoint #mcdevs
2024-02-19 16:06:01	-->	dinhero21 (~dinhero21@189.54.244.52) a rejoint #mcdevs
2024-02-19 16:06:58	<--	dinhero21 (~dinhero21@189.54.244.52) a quitté (Remote host closed the connection)
2024-02-19 16:07:39	-->	dinhero21 (~dinhero21@189.54.244.52) a rejoint #mcdevs
2024-02-19 16:08:16	<--	dinhero21 (~dinhero21@189.54.244.52) a quitté #mcdevs
2024-02-19 16:46:23	<--	TheTechRobo (~TheTechRo@2001:19f0:b001:3f:5400:3ff:fee8:e827) a quitté (Ping timeout: 256 seconds)
2024-02-19 16:47:18	-->	TheTechRobo (~TheTechRo@2001:19f0:b001:3f:5400:3ff:fee8:e827) a rejoint #mcdevs
2024-02-19 17:41:11	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-19 23:27:16	<--	NoahvdAa (~NoahvdAa@user/noahvdaa) a quitté (Read error: Connection reset by peer)
2024-02-19 23:29:24	-->	NoahvdAa (~NoahvdAa@user/noahvdaa) a rejoint #mcdevs
2024-02-20 00:19:09	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 268 seconds)
2024-02-20 00:33:51	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-02-20 04:02:49	<--	bswartz (~bswartz@user/bswartz) a quitté (Ping timeout: 264 seconds)
2024-02-20 04:03:41	-->	bswartz (~bswartz@136.56.42.13) a rejoint #mcdevs
2024-02-20 04:03:41	<--	bswartz (~bswartz@136.56.42.13) a quitté (Changing host)
2024-02-20 04:03:41	-->	bswartz (~bswartz@user/bswartz) a rejoint #mcdevs
2024-02-20 05:29:57	-->	NoahvdAa4 (~NoahvdAa@user/noahvdaa) a rejoint #mcdevs
2024-02-20 05:32:04	<--	NoahvdAa (~NoahvdAa@user/noahvdaa) a quitté (Ping timeout: 246 seconds)
2024-02-20 05:32:04	--	NoahvdAa4 est maintenant connu sous le nom NoahvdAa
2024-02-20 10:17:29	<--	Anna (anna@borealis.voxelstorm.com) a quitté #mcdevs
2024-02-20 10:59:49	<--	The_Red_Freak (~The_Red_F@user/The-Red-Freak/x-5541572) a quitté (Ping timeout: 272 seconds)
2024-02-20 11:00:56	-->	The_Red_Freak (~The_Red_F@user/The-Red-Freak/x-5541572) a rejoint #mcdevs
2024-02-20 14:17:52	-->	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a rejoint #mcdevs
2024-02-20 14:19:30	Scotsoo	Yo! Learning more about game servers so trying to implement a minecraft server. I'm on encryption request but every time I connect I get a protocol error in the client. My payload looks right according to the spec - is there any way to debug this a bit easier?
2024-02-20 14:25:57	Scotsoo	Ignore this, I've fixed it:D
2024-02-20 15:08:25	<--	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a quitté (Quit: Connection closed)
2024-02-20 15:52:51	<--	Disconsented (~quassel@irc.disconsented.com) a quitté (Remote host closed the connection)
2024-02-20 15:54:01	-->	Disconsented (~quassel@irc.disconsented.com) a rejoint #mcdevs
2024-02-20 16:05:42	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Remote host closed the connection)
2024-02-20 16:13:06	-->	Mateon1 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-02-20 17:56:32	<--	Disconsented (~quassel@irc.disconsented.com) a quitté (Quit: No Ping reply in 180 seconds.)
2024-02-20 17:58:43	-->	Disconsented (~quassel@irc.disconsented.com) a rejoint #mcdevs
2024-02-20 18:39:22	-->	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a rejoint #mcdevs
2024-02-20 23:24:10	<--	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a quitté (Quit: Connection closed)
2024-02-21 00:10:26	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 268 seconds)
2024-02-21 00:25:38	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-02-22 01:22:57	<--	The_Red_Freak (~The_Red_F@user/The-Red-Freak/x-5541572) a quitté (Ping timeout: 255 seconds)
2024-02-22 01:25:52	-->	The_Red_Freak (~The_Red_F@user/The-Red-Freak/x-5541572) a rejoint #mcdevs
2024-02-22 06:02:42	<--	TkTech (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a quitté (Read error: Connection reset by peer)
2024-02-22 06:04:45	-->	TkTech (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a rejoint #mcdevs
2024-02-22 15:53:09	-->	Guest24 (~Guest24@i16-les02-th2-31-36-119-220.sfr.lns.abo.bbox.fr) a rejoint #mcdevs
2024-02-22 15:53:28	Guest24	Hi
2024-02-22 15:53:45	Guest24	I'm conding a minecraft bot with node-minecraft-protocol
2024-02-22 15:54:07	Guest24	My question is "What's the packet to move forward" ?
2024-02-22 16:49:22	pokechu22	https://wiki.vg/Protocol#Set_Player_Position and the 3 after it
2024-02-22 17:08:12	Guest24	thx
2024-02-22 17:08:14	<--	Guest24 (~Guest24@i16-les02-th2-31-36-119-220.sfr.lns.abo.bbox.fr) a quitté (Quit: Client closed)
2024-02-22 17:14:36	-->	Guest24 (~Guest24@i16-les02-th2-31-36-119-220.sfr.lns.abo.bbox.fr) a rejoint #mcdevs
2024-02-22 17:41:14	<--	Guest24 (~Guest24@i16-les02-th2-31-36-119-220.sfr.lns.abo.bbox.fr) a quitté (Quit: Client closed)
2024-02-22 21:19:41	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-02-22 21:26:24	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-02-22 22:26:57	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-02-22 23:12:17	<--	bixilon (~bixilon@node-3.bixilon.de) a quitté (Quit: ZNC 1.8.2+deb2build5 - https://znc.in)
2024-02-22 23:12:45	-->	bixilon (~bixilon@node-3.bixilon.de) a rejoint #mcdevs
2024-02-22 23:14:36	<--	bixilon (~bixilon@node-3.bixilon.de) a quitté (Client Quit)
2024-02-22 23:15:03	-->	bixilon (~bixilon@node-3.bixilon.de) a rejoint #mcdevs
2024-02-22 23:15:06	<--	kelvium (~kelvium@89b5da81.kelvium.fun) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-22 23:33:30	<--	bixilon (~bixilon@node-3.bixilon.de) a quitté (Quit: ZNC 1.8.2+deb2build5 - https://znc.in)
2024-02-22 23:33:57	-->	bixilon (~bixilon@node-3.bixilon.de) a rejoint #mcdevs
2024-02-23 00:53:30	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Quit: Ping timeout (120 seconds))
2024-02-23 00:54:04	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-23 01:02:00	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-02-23 01:24:14	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-02-23 01:34:12	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Quit: Ping timeout (120 seconds))
2024-02-23 01:36:55	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-23 01:36:56	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Remote host closed the connection)
2024-02-23 01:39:28	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-23 01:48:19	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Quit: Ping timeout (120 seconds))
2024-02-23 01:49:10	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-23 02:20:08	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-02-23 07:24:21	<--	kennytv (~kennytv@2001:41d0:800:19:da::) a quitté (Quit: Ping timeout (120 seconds))
2024-02-23 07:40:10	-->	kennytv (~kennytv@2001:41d0:800:19:da::) a rejoint #mcdevs
2024-02-23 09:01:08	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Quit: :3)
2024-02-23 09:01:26	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-23 09:35:54	<--	BratishkaErik (fd46852e72@user/BratishkaErik) a quitté (Remote host closed the connection)
2024-02-23 09:35:54	<--	xtex (250b76165c@2a03:6000:1812:100::12fc) a quitté (Write error: Broken pipe)
2024-02-23 09:35:54	<--	caleb (ca329e08ca@user/ace) a quitté (Remote host closed the connection)
2024-02-23 09:35:54	<--	vismie (c8b263ae0e@2a03:6000:1812:100::fb8) a quitté (Remote host closed the connection)
2024-02-23 09:36:32	-->	caleb_ (ca329e08ca@user/ace) a rejoint #mcdevs
2024-02-23 09:36:40	-->	BratishkaErik (fd46852e72@user/BratishkaErik) a rejoint #mcdevs
2024-02-23 09:36:40	-->	xtex (250b76165c@2a03:6000:1812:100::12fc) a rejoint #mcdevs
2024-02-23 09:36:40	-->	vismie (c8b263ae0e@2a03:6000:1812:100::fb8) a rejoint #mcdevs
2024-02-23 13:25:18	<--	kennytv (~kennytv@2001:41d0:800:19:da::) a quitté (Quit: Ping timeout (120 seconds))
2024-02-23 13:35:16	-->	kennytv (~kennytv@2001:41d0:800:19:da::) a rejoint #mcdevs
2024-02-23 14:11:12	-->	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a rejoint #mcdevs
2024-02-23 14:34:14	<--	high_ground (~high_grou@user/high-ground/x-5722129) a quitté (Quit: Left)
2024-02-23 14:35:12	-->	high_ground (~high_grou@user/high-ground/x-5722129) a rejoint #mcdevs
2024-02-23 16:42:11	<--	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a quitté (Quit: Connection closed)
2024-02-24 21:55:36	-->	Tebras (~void@52.red-88-25-8.staticip.rima-tde.net) a rejoint #mcdevs
2024-02-24 22:05:31	Tebras	Hello, sorry to bother you all again with the same issue, my client fails at the authentication step with "https://sessionserver.mojang.com/session/minecraft/join", authentication step from "https://wiki.vg/Protocol_Encryption".
2024-02-24 22:05:35	Tebras	Error 403 "ForbiddenOperationException", my access token looks fine, testing with a 1.19.4 version server, so the server id is empty, length 0, i dont use it in my hash(i do sha1update(secret) and sha1update(pubkey) for the hash).
2024-02-24 22:05:45	Tebras	I do the authentication(always fails with 403) and then i send an encryption response message to the server, i always receive an aes encrypted message saying {"translate":"multiplayer.disconnect.unverified_username"}.
2024-02-24 22:05:56	Tebras	Maybe the public key data im using for the hash is wrong, this is a screenshot of the public key data im using represented as a hex string, ive tried sending only specific parts but nothing : "https://imgur.com/a/p5CyUrI".
2024-02-24 22:06:06	Tebras	Also every time i get an access token its length is different, could it be that im missing data? I just cant think of any other data that could be wrong, Thanks.
2024-02-24 22:18:02	<--	TheTechRobo (~TheTechRo@2001:19f0:b001:3f:5400:3ff:fee8:e827) a quitté (Quit: Leaving)
2024-02-24 22:31:03	-->	TheTechRobo (~TheTechRo@217.167.75.170.lunanode-rdns.com) a rejoint #mcdevs
2024-02-24 22:35:41	<--	TheTechRobo (~TheTechRo@217.167.75.170.lunanode-rdns.com) a quitté (Remote host closed the connection)
2024-02-24 22:41:54	-->	TheTechRobo (~TheTechRo@217.167.75.170.lunanode-rdns.com) a rejoint #mcdevs
2024-02-24 22:47:03	<--	TheTechRobo (~TheTechRo@217.167.75.170.lunanode-rdns.com) a quitté #mcdevs (Leaving)
2024-02-25 01:25:15	lassipulkkinen	I can imagine the access token varying in length at least, since they were using JWT last time I checked.
2024-02-25 01:28:53	lassipulkkinen	Um, wait, that "public key data" is getting interpreted by the web decoder thing as a private key of some sort?
2024-02-25 01:40:02	Tebras	Its supposed to be this https://imgur.com/WCyUAQG, i dont know why it says private key in the decoder
2024-02-25 01:41:34	Tebras	But im able to use it to encrypt the secret and send it to the server, then the server uses that secret to send me aes encrypted data
2024-02-25 01:41:57	lassipulkkinen	Yeah I already figured that out; the tool just doesn't know the SubjectPublicKeyInfo schema for whatever reason.
2024-02-25 01:43:12	lassipulkkinen	The data looks fine
2024-02-25 01:47:38	lassipulkkinen	I assume you accounted for the non-standard digest encoding pointed out in the article?
2024-02-25 01:48:21	lassipulkkinen	Also assuming you're able to join using the official client.
2024-02-25 01:48:57	Tebras	yes, i get the right output, with Notch, jeb_ and simon, also tested that i can do update(si) and then update(mon) and i get the same output
2024-02-25 01:49:06	Tebras	and yes i can connect with the official client
2024-02-25 01:49:06	lassipulkkinen	good
2024-02-25 01:55:35	lassipulkkinen	Based on a bit of testing, the ForbiddenOperationException seems to indicate the problem has to do with the access token.
2024-02-25 01:56:08	lassipulkkinen	Invalid selectedProfile or serverId gave more descriptive error messages.
2024-02-25 01:57:34	lassipulkkinen	Did you spell accessToken correctly? Just checking
2024-02-25 02:00:22	lassipulkkinen	Also, if the server hash is properly formatted but wrong, the endpoint doesn't complain at all.
2024-02-25 02:09:36	Tebras	yes, accessToken, selectedProfile, serverId
2024-02-25 02:09:48	Tebras	but i get the same error if i send junk
2024-02-25 02:10:35	lassipulkkinen	so do i
2024-02-25 02:11:03	lassipulkkinen	But if the token is correct, you get different errors
2024-02-25 02:11:13	Tebras	if i replace the access token data, selectedid data etc, the error is the same, only changes if i miss a coma because its wrong format 
2024-02-25 02:11:17	Tebras	oh really?
2024-02-25 02:11:24	lassipulkkinen	yes
2024-02-25 02:11:35	lassipulkkinen	Apparently it checks the other fields after authenticating
2024-02-25 02:12:43	Tebras	the way i got the access token wasnt from my executable but curl command in a script, and at first i had %2b and %3d around
2024-02-25 02:13:09	Tebras	and apparently it was its way of escaping the characters + and =
2024-02-25 02:13:50	Tebras	so i replaced them with commands, but maybe i messed something up, i should be getting the access token in my executable too, and make sure i dont have anything wrong i guess
2024-02-25 02:14:35	lassipulkkinen	possibly; mine only contains A-Za-z0-9_. though...
2024-02-25 02:14:52	Tebras	it doesnt contain / characters?
2024-02-25 02:15:07	lassipulkkinen	mine doesn't, though that doesn't make it impossible
2024-02-25 02:16:21	Tebras	i mean mine gets many, ok that was really helpful, thank you very much
2024-02-25 02:17:36	lassipulkkinen	I requested a new one, and now it has - and ., no _... Maybe they're just randomizing which ones are used for questionable obfuscation?
2024-02-25 02:19:08	lassipulkkinen	The encoding looks like base64, but normally it would use either +/ or -_
2024-02-25 02:19:45	Tebras	how long is it?
2024-02-25 02:20:12	lassipulkkinen	Both 612 bytes.
2024-02-25 02:20:43	Tebras	mine always goes beyond 1000, and looks just like this, https://imgur.com/tU6Sihq
2024-02-25 02:20:51	Tebras	found that reading randomly around
2024-02-25 02:21:11	Tebras	without the begin public key thing, but almost always ends with the ++
2024-02-25 02:21:27	lassipulkkinen	Is that a valid token??
2024-02-25 02:21:46	lassipulkkinen	Did you send a token in a public chat?
2024-02-25 02:22:05	Tebras	thats from https://wiki.vg/Microsoft_Authentication_Scheme
2024-02-25 02:22:05	lassipulkkinen	It'll expire I guess
2024-02-25 02:22:16	lassipulkkinen	ah oops
2024-02-25 02:22:25	lassipulkkinen	the darkreader thing made it non-obvious
2024-02-25 02:22:37	Tebras	oh hahaha
2024-02-25 02:23:12	Tebras	weird that mine looks like that, i literally got it like: AcessToken=thenallthat
2024-02-25 02:23:23	Tebras	but ill just do that part in my program to make sure i get the right data and i should be fine
2024-02-25 02:24:36	lassipulkkinen	AccessToken=... where? That's definitely not that it should look like.
2024-02-25 02:24:42	lassipulkkinen	*what
2024-02-25 02:25:49	lassipulkkinen	The correct token is the one you get from https://api.minecraftservices.com/authentication/login_with_xbox
2024-02-25 02:28:27	Tebras	i think i did this https://mojang-api-docs.gapple.pw/authentication/msa
2024-02-25 02:29:33	Tebras	https://imgur.com/a/TkBhQmF
2024-02-25 02:29:54	Tebras	and thats how i get my uuid too
2024-02-25 02:31:02	Tebras	i have no idea why i just went and did it that way, not being sent there by the wiki.vg documentation at all
2024-02-25 02:32:41	lassipulkkinen	That's not the right access token; you need to continue to the "Signing into Minecraft" section. 
2024-02-25 02:32:53	lassipulkkinen	Which looks pretty similar to what's on wiki.vg
2024-02-25 02:33:28	lassipulkkinen	There's a lot of tokens; it's confusing.
2024-02-25 02:44:51	Tebras	It all makes sense now, thank you so much really, ive been really stuck.
2024-02-25 05:25:16	<--	Tebras (~void@52.red-88-25-8.staticip.rima-tde.net) a quitté #mcdevs
2024-02-25 10:53:52	<--	balrog (znc@user/balrog) a quitté (Quit: Bye)
2024-02-25 10:54:44	-->	balrog (znc@user/balrog) a rejoint #mcdevs
2024-02-25 12:50:23	<--	deltab (~deltab@95.154.230.49) a quitté (Ping timeout: 272 seconds)
2024-02-25 13:01:32	-->	deltab (~deltab@95.154.230.49) a rejoint #mcdevs
2024-02-25 21:00:35	<--	NoahvdAa (~NoahvdAa@user/noahvdaa) a quitté (Ping timeout: 264 seconds)
2024-02-25 22:09:19	-->	NoahvdAa (~NoahvdAa@user/noahvdaa) a rejoint #mcdevs
2024-02-26 02:37:48	-->	Mateon2 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-02-26 02:39:28	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Ping timeout: 255 seconds)
2024-02-26 02:39:28	--	Mateon2 est maintenant connu sous le nom Mateon1
2024-02-26 03:22:47	<--	Thinkofname (~thinkthin@37.205.12.211) a quitté (Ping timeout: 264 seconds)
2024-02-26 03:31:53	-->	Thinkofname (~thinkthin@37.205.12.211) a rejoint #mcdevs
2024-02-26 11:34:58	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Ping timeout: 255 seconds)
2024-02-26 11:35:13	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-02-26 13:15:55	<--	deltab (~deltab@95.154.230.49) a quitté (Ping timeout: 272 seconds)
2024-02-26 13:26:48	-->	deltab (~deltab@95.154.230.49) a rejoint #mcdevs
2024-02-26 15:56:24	-->	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a rejoint #mcdevs
2024-02-26 15:57:58	<--	stilbruch (~stilbruch@vps-b83b453a.vps.ovh.us) a quitté (Remote host closed the connection)
2024-02-26 19:06:36	-->	balrog_ (znc@user/balrog) a rejoint #mcdevs
2024-02-26 19:11:19	<--	balrog (znc@user/balrog) a quitté (*.net *.split)
2024-02-26 19:11:20	<--	lassipulkkinen (lassi@pulk.fi) a quitté (*.net *.split)
2024-02-26 19:12:36	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Ping timeout: 255 seconds)
2024-02-26 19:19:25	-->	lassipulkkinen (lassi@pulk.fi) a rejoint #mcdevs
2024-02-26 19:36:09	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Quit: Ping timeout (120 seconds))
2024-02-26 19:41:41	-->	magmaus3 (~magmaus3@46.151.137.244) a rejoint #mcdevs
2024-02-26 21:49:33	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-26 21:49:55	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-02-26 23:16:21	<--	Scotsoo (~Scotsoo@host-78-145-154-107.as13285.net) a quitté (Quit: Connection closed)
2024-02-27 03:59:50	-->	Mateon1 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-02-27 06:08:04	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-27 06:08:26	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-02-27 13:24:15	<--	kennytv (~kennytv@2001:41d0:800:19:da::) a quitté (Quit: Ping timeout (120 seconds))
2024-02-27 13:26:53	-->	kennytv (~kennytv@2001:41d0:800:19:da::) a rejoint #mcdevs
2024-02-27 14:44:02	--	balrog_ est maintenant connu sous le nom balrog
2024-02-27 15:31:03	<--	Disconsented (~quassel@irc.disconsented.com) a quitté (Quit: No Ping reply in 180 seconds.)
2024-02-27 15:32:23	-->	Disconsented (~quassel@irc.disconsented.com) a rejoint #mcdevs
2024-02-27 15:57:28	-->	magmaus34 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-27 15:59:44	<--	magmaus3 (~magmaus3@46.151.137.244) a quitté (Ping timeout: 256 seconds)
2024-02-27 15:59:44	--	magmaus34 est maintenant connu sous le nom magmaus3
2024-02-27 16:03:50	-->	magmaus35 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-27 16:05:58	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 264 seconds)
2024-02-27 16:05:59	--	magmaus35 est maintenant connu sous le nom magmaus3
2024-02-27 19:28:38	<--	VectorTest (VectorTest@47.145.186.13) a quitté (Read error: Connection reset by peer)
2024-02-27 19:28:52	-->	MisterVector (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-02-27 20:17:05	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-27 20:17:26	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-02-28 02:16:56	-->	stack (~StackDoub@195.252.219.49) a rejoint #mcdevs
2024-02-28 16:20:02	botifico	[McUpdates] Minecraft snapshot 24w09a has just been published to the launcher!
2024-02-28 16:22:40	botifico	[Burger] New data now avaliable for 24w09a:
2024-02-28 16:22:41	botifico	[Burger] Diff from 24w07a: https://pokechu22.github.io/Burger/diff_24w07a_24w09a.html (https://pokechu22.github.io/Burger/diff_24w07a_24w09a.json)
2024-02-28 16:22:42	botifico	[Burger] Full data: https://pokechu22.github.io/Burger/24w09a.html (https://pokechu22.github.io/Burger/24w09a.json)
2024-02-28 18:39:31	-->	stdcall (~stdcall@2a01:4f9:3070:1569:a::3) a rejoint #mcdevs
2024-02-28 18:41:46	stdcall	Hey people. Wanted to ask about Burger project. Is it still alive? Last commit was pushed 2 years ago, just running the project fails with:
2024-02-28 18:41:47	stdcall	Traceback (most recent call last):
2024-02-28 18:41:47	stdcall	  File "C:\Projects\MinecraftMods\burger\munch.py", line 40, in <module>
2024-02-28 18:41:48	stdcall	    from burger import website
2024-02-28 18:41:48	stdcall	ModuleNotFoundError: No module named 'burger'
2024-02-28 18:47:32	-->	stdcall41 (~stdcall@2a01:4f9:3070:1569:a::3) a rejoint #mcdevs
2024-02-28 18:48:08	<--	stdcall (~stdcall@2a01:4f9:3070:1569:a::3) a quitté (Quit: Client closed)
2024-02-28 18:48:20	<--	stdcall41 (~stdcall@2a01:4f9:3070:1569:a::3) a quitté (Client Quit)
2024-02-28 18:48:31	-->	stdcall (~stdcall@2a01:4f9:3070:1569:a::3) a rejoint #mcdevs
2024-02-28 18:51:24	pokechu22	stdcall: yeah, see https://github.com/pokechu22/burger/tree/1.19-dev
2024-02-28 18:51:50	pokechu22	and e.g. https://pokechu22.github.io/Burger/diff_24w07a_24w09a.html - things are fairly broken in recent versions but it at least does *something*
2024-02-28 18:52:18	pokechu22	(and https://pokechu22.github.io/Burger/24w09a.html)
2024-02-28 18:52:48	pokechu22	I'm not sure why you're getting that specific error though; I don't think I've seen that one before and I don't think any recent changes would fix it
2024-02-28 18:54:37	stdcall	I see that these are generated HTML pages. Are any JSON files available?
2024-02-28 18:56:45	pokechu22	Yeah, https://pokechu22.github.io/Burger/diff_24w07a_24w09a.json and https://pokechu22.github.io/Burger/24w09a.json
2024-02-28 18:57:02	pokechu22	there's gigabytes of them in https://github.com/pokechu22/burger/tree/gh-pages
2024-02-28 18:58:01	stdcall	Much appreciated!
2024-02-28 19:11:55	<--	stdcall (~stdcall@2a01:4f9:3070:1569:a::3) a quitté (Ping timeout: 250 seconds)
2024-02-28 19:49:16	-->	stdcall (~stdcall@2a01:4f9:3070:1569:a::3) a rejoint #mcdevs
2024-02-28 19:49:36	<--	stdcall (~stdcall@2a01:4f9:3070:1569:a::3) a quitté (Client Quit)
2024-02-29 01:04:37	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 264 seconds)
2024-02-29 01:05:26	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-02-29 01:28:53	-->	Tebras (~void@52.red-88-25-8.staticip.rima-tde.net) a rejoint #mcdevs
2024-02-29 02:19:42	Tebras	Hello, my client has succesfully completed the step at "https://wiki.vg/Protocol_Encryption"
2024-02-29 02:19:53	Tebras	I got the http response 204, and then i sent the encryption response.
2024-02-29 02:20:00	Tebras	But i receive an aes encrypted message from the server that says {"translate":"multiplayer.disconnect.unverified_username"}
2024-02-29 02:20:08	Tebras	The data sent in the login start packet is the exact same as my official minecraft launcher, and the encryption is working
2024-02-29 02:20:15	Tebras	What could be making the server say unverified username?
2024-02-29 02:53:12	lassipulkkinen	Hard to know just based on that. You could launch the server with SSLKEYLOGFILE set (to allow decryption of the https traffic) and use wireshark to see the request it's making to https://sessionserver.mojang.com/session/minecraft/hasJoined.
2024-02-29 02:54:22	lassipulkkinen	What os are you on, though? No idea how to do that on windows.
2024-02-29 02:58:42	Tebras	linux, ill look into that thanks
2024-02-29 03:02:11	lassipulkkinen	That won't necessarily help, since based on the previous troubleshooting you _probably_ have the hash calculation correct, at least. But it might.
2024-02-29 03:05:06	Tebras	The hash calculation must be correct right? since i did get http 204 code, or is it possible to somehow be wrong?
2024-02-29 03:07:00	lassipulkkinen	(i was writing this before you responded:) Other than that, the only potential bug I can think of without looking at your code is that you could be sending the Encryption Response before the request to /join has completed. Seems a bit far fetched; probably depends on the http library / frameworks / language being used.
2024-02-29 03:08:49	lassipulkkinen	About the hash calculation, no the auth server has no way of knowing if it's correct. The point of the mechanism is that it'll match up with the one sent by the server afterwards.
2024-02-29 03:09:03	lassipulkkinen	*sent by the client when the server makes the request
2024-02-29 03:09:21	lassipulkkinen	oh now i realize what i meant by that oops not a typo
2024-02-29 03:09:29	lassipulkkinen	but confusing i guess
2024-02-29 03:10:13	Tebras	i understand, then i should see what the server is sending like you said
2024-02-29 03:10:55	Tebras	i tried waiting for some time after the step where i have to send the hash, same thing
2024-02-29 03:12:53	lassipulkkinen	Ok; it should be enough to just wait for the response to arrive. All I meant was that if you happened to be using an async http library, it would be possible to start the request and proceed without waiting for it to complete.
2024-02-29 03:14:50	Tebras	oh ok
2024-02-29 03:37:10	Tebras	Im pretty sure i know what i did wrong, i really messed things up when adding new code and im not authenticating with mojang servers before starting the connection with the minecraft server
2024-02-29 03:38:01	Tebras	i noticed because when looking at the server, a message saying that the username couldnt be verified happens before i do the hash part
2024-02-29 03:38:41	Tebras	dumb mistakes from when im tired, damn
2024-02-29 03:41:12	lassipulkkinen	wait, the server logs are of course separate from your client's, so you're looking at the timestamps or what? or did you mean the server's response appears in the client log?
2024-02-29 03:45:35	Tebras	i had a pause, like, enter to continue in my code from when i was testing, in case my code was going too fast, and i saw the error in the server window
2024-02-29 03:46:54	Tebras	then i realized i was trying to authenticate with mojang servers right before sending the hash, once i had already started the connection with the server
2024-02-29 03:48:30	lassipulkkinen	opening the mc server connection before auth shouldn't be a problem; you need to do that to know if the server needs auth in the first place.
2024-02-29 03:49:36	Tebras	but you must have logged into your minecraft account right?
2024-02-29 03:53:07	lassipulkkinen	typically it would of course go (1) login (obtain accesss token) (2) connect, receive Encryption Request (3) generate hash and send to /join, wait for response (4) send Encryption Response. But rearranging steps 1 and 2 shouldn't make a difference.
2024-02-29 03:54:08	lassipulkkinen	Again, I don't know what your code looks like, so talking about it gets confusing.
2024-02-29 03:55:33	Tebras	the first step, login, i was login when i generated the hash
2024-02-29 03:55:57	Tebras	for some reason
2024-02-29 03:56:25	Tebras	i was logging in*
2024-02-29 03:59:20	lassipulkkinen	if they were happening concurrently, then that's a problem; if not then it whould still work. But of course, if you do/did get it to work, then you found the solution. There's clearly some miscommunication going on, and it's hard to tell where exactly.
2024-02-29 04:02:11	Tebras	yes its hard for me to explain anything, ill just fix what im pretty sure is wrong and see
2024-02-29 07:13:02	Tebras	Its working, first i was getting the "failed to verify username" message as soon as i sent the first message to the server
2024-02-29 07:13:51	Tebras	i fixed the login, and i was no longer getting the error as soon as i joined, but i was getting the same error when i sent the encryption response message
2024-02-29 07:14:20	Tebras	and then i realized i was sending the verify token with the public key, fixed that too and its working
2024-02-29 07:38:47	<--	Tebras (~void@52.red-88-25-8.staticip.rima-tde.net) a quitté (Quit: Lost terminal)
2024-02-29 07:54:38	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-29 07:55:01	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-02-29 11:24:19	<--	MisterVector (VectorTest@47.145.186.13) a quitté (Read error: Connection reset by peer)
2024-02-29 11:25:18	-->	MisterVector (~Vector@47.145.186.13) a rejoint #mcdevs
2024-02-29 15:10:20	<--	KurtThiemann (~KurtThiem@nc.thiemann.io) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-29 15:10:32	-->	KurtThiemann (~KurtThiem@nc.thiemann.io) a rejoint #mcdevs
2024-02-29 16:39:48	<--	MisterVector (~Vector@47.145.186.13) a quitté
2024-02-29 16:42:55	-->	MisterVector (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-02-29 20:16:39	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-02-29 20:17:00	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-01 23:46:28	-->	harlanji (~harlanji@lib-07-subnet-130.rdns.cenic.net) a rejoint #mcdevs
2024-03-01 23:50:08	<--	harlanji (~harlanji@lib-07-subnet-130.rdns.cenic.net) a quitté (Client Quit)
2024-03-01 23:50:24	-->	harlanji (~harlanji@lib-07-subnet-130.rdns.cenic.net) a rejoint #mcdevs
2024-03-02 00:17:49	<--	harlanji (~harlanji@lib-07-subnet-130.rdns.cenic.net) a quitté (Quit: Client closed)
2024-03-02 00:39:27	-->	harlanji (~harlanji@lib-07-subnet-130.rdns.cenic.net) a rejoint #mcdevs
2024-03-02 01:34:07	-->	Tebras (~void@52.red-88-25-8.staticip.rima-tde.net) a rejoint #mcdevs
2024-03-02 01:50:05	<--	harlanji (~harlanji@lib-07-subnet-130.rdns.cenic.net) a quitté (Ping timeout: 250 seconds)
2024-03-02 06:41:42	<--	Tebras (~void@52.red-88-25-8.staticip.rima-tde.net) a quitté (Quit: leaving)
2024-03-02 07:16:12	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-02 07:23:12	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-02 07:24:12	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Client Quit)
2024-03-02 07:25:49	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-02 07:26:42	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Client Quit)
2024-03-02 07:27:42	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-02 07:29:12	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Client Quit)
2024-03-02 07:31:56	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-02 07:37:42	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-02 07:44:38	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-02 07:48:42	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Client Quit)
2024-03-02 07:49:04	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-02 07:50:12	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Client Quit)
2024-03-02 07:54:56	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-02 12:13:58	-->	Scotsoo (~Scotsoo@host-92-18-229-120.as13285.net) a rejoint #mcdevs
2024-03-02 12:29:11	<--	Scotsoo (~Scotsoo@host-92-18-229-120.as13285.net) a quitté (Quit: Connection closed)
2024-03-02 12:40:05	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 268 seconds)
2024-03-02 12:42:50	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-03-02 17:43:10	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 246 seconds)
2024-03-02 17:51:12	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-03-02 17:56:16	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Ping timeout: 260 seconds)
2024-03-03 04:34:49	<--	stack (~StackDoub@195.252.219.49) a quitté (Quit: Ping timeout (120 seconds))
2024-03-03 12:00:02	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-03 12:14:54	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-03 15:37:47	-->	magmaus3 (~magmaus3@hostb244.plastcom.pl) a rejoint #mcdevs
2024-03-03 22:43:53	-->	Lokerhp (~lokerhp@185.155.220.251) a rejoint #mcdevs
2024-03-03 22:56:53	Lokerhp	Hello! Just wanted to say thanks to the wiki.vg makers, the protocol spec is very usefull! 
2024-03-04 02:08:11	<--	mbaxter (mbaxter@bnc.io) a quitté (Changing host)
2024-03-04 02:08:11	-->	mbaxter (mbaxter@user/mbaxter) a rejoint #mcdevs
2024-03-04 02:41:04	-->	mbaxter2 (~mbax@user/mbaxter) a rejoint #mcdevs
2024-03-04 02:41:46	<--	mbaxter (mbaxter@user/mbaxter) a quitté (Quit: Meow)
2024-03-04 02:41:46	--	mbaxter2 est maintenant connu sous le nom mbaxter
2024-03-04 07:59:07	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-04 07:59:29	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-04 08:26:46	<--	grumble (grumble@user/grumble) a quitté (Ping timeout: 268 seconds)
2024-03-04 22:35:44	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-05 00:47:09	-->	horzion (~horzion@ProtonDB/horzion) a rejoint #mcdevs
2024-03-05 00:47:55	horzion	hoi. i am trying to get MCP 4.5 (b1.9-pre5) running, but i cant seem to decompile. is decompile even needed?
2024-03-05 00:48:12	horzion	it errors when trying to patch
2024-03-05 01:04:51	pokechu22	If you want to use MCP you almost certainly want to decompile. But if it fails to patch then it might just not work - b1.9-pre5 is pretty old and other versions came out very shortly after it
2024-03-05 01:05:41	pokechu22	the patching isn't strictly necessary to decompile but it is needed if you want to recompile afterwards (the patches mainly fix issues with the decompiler, and while some of those issues may have been fixed in newer versions of the decompiler in the decade since then, trying to use a newer decompiler will lead to its own issues)
2024-03-05 01:06:03	horzion	ive seen videos of alpha decompiling working from 2020, so i am not sure why its not working with a newer version of mc
2024-03-05 01:07:05	horzion	and while i am aware that the next release to pre5 is literal 1.0, i really want to get stuff working/goin on b1.9 pre 5. maybe i should use legacy fabric instead?
2024-03-05 01:07:09	pokechu22	That might be because people have done additional work to make alpha decompiling more stable (or perhaps that version of MCP just happened to be more stable)
2024-03-05 01:07:28	pokechu22	Legacy fabric is presumably a more recent project and one where issues have a chance of being fixed, so it's worth a try, though I've never used it myself
2024-03-05 01:07:42	pokechu22	and don't forget about the two release candidates :)
2024-03-05 01:09:08	horzion	actually missing more than that
2024-03-05 01:09:14	horzion	there is also b1.9 pre 6
2024-03-05 01:09:30	horzion	either way, for legacy fabric i need to figure out how that would work in multimc
2024-03-05 01:09:39	horzion	but that should be easily done
2024-03-05 01:12:39	<--	mbaxter (~mbax@user/mbaxter) a quitté (Ping timeout: 260 seconds)
2024-03-05 01:14:54	horzion	hm, seems legacy fabric supports at the earliest, 1.3
2024-03-05 01:15:03	horzion	not beta, actual release 1.3
2024-03-05 01:15:07	horzion	so thats not really an option
2024-03-05 01:15:27	-->	mbaxter (~mbax@user/mbaxter) a rejoint #mcdevs
2024-03-05 01:23:41	pokechu22	Then I recommend trying either a slightly older version of MCP or a slightly newer one and seeing how those work
2024-03-05 01:32:26	horzion	so, apparently, there is a whole seperate project that tries to support fabric/quilt like modding on minecraft versions not serviced by official fabric named ornithe
2024-03-05 04:06:29	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Ping timeout: 250 seconds)
2024-03-05 04:20:01	<--	horzion (~horzion@ProtonDB/horzion) a quitté (Ping timeout: 268 seconds)
2024-03-05 04:36:05	-->	horzion (~horzion@ProtonDB/horzion) a rejoint #mcdevs
2024-03-05 07:34:23	<--	rtm516 (~rtm516@irc.rtm516.co.uk) a quitté (Ping timeout: 260 seconds)
2024-03-05 09:11:56	-->	rtm516 (~rtm516@irc.rtm516.co.uk) a rejoint #mcdevs
2024-03-05 13:25:10	<--	kennytv (~kennytv@2001:41d0:800:19:da::) a quitté (Quit: o>)
2024-03-05 18:05:31	<--	magmaus3 (~magmaus3@hostb244.plastcom.pl) a quitté (Changing host)
2024-03-05 18:05:31	-->	magmaus3 (~magmaus3@user/magmaus3) a rejoint #mcdevs
2024-03-05 18:39:59	<--	Almtesh (~Almtesh@2001:bc8:3335:c1aa:7951:ec8e:b50c:5a74) a quitté (Remote host closed the connection)
2024-03-05 19:56:21	-->	ponaskovas12321 (~PonasKova@193.219.171.1) a rejoint #mcdevs
2024-03-05 19:56:32	<--	ponaskovas12321 (~PonasKova@193.219.171.1) a quitté (Client Quit)
2024-03-05 22:05:32	<--	horzion (~horzion@ProtonDB/horzion) a quitté (Quit: Off praying to the Omnissiah)
2024-03-05 22:55:48	-->	Almtesh (~Almtesh@2001:bc8:3335:c1aa:7951:ec8e:b50c:5a74) a rejoint #mcdevs
2024-03-05 23:49:48	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-06 00:01:39	<--	Disconsented (~quassel@irc.disconsented.com) a quitté (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
2024-03-06 00:03:55	-->	Disconsented (~quassel@irc.disconsented.com) a rejoint #mcdevs
2024-03-06 00:04:40	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-06 00:05:09	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-06 04:09:03	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Ping timeout: 250 seconds)
2024-03-06 06:07:41	<--	high_ground (~high_grou@user/high-ground/x-5722129) a quitté (Ping timeout: 272 seconds)
2024-03-06 09:15:34	-->	TkTech8 (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a rejoint #mcdevs
2024-03-06 09:16:49	<--	TkTech (~TkTech@modemcable198.106-201-24.mc.videotron.ca) a quitté (Ping timeout: 255 seconds)
2024-03-06 09:16:50	--	TkTech8 est maintenant connu sous le nom TkTech
2024-03-06 10:34:37	-->	VectorTest (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-03-06 10:35:49	<--	MisterVector (VectorTest@47.145.186.13) a quitté (Ping timeout: 264 seconds)
2024-03-06 16:02:51	botifico	[Burger] New data now avaliable for 24w10a:
2024-03-06 16:02:58	botifico	[Burger] Diff from 24w09a: https://pokechu22.github.io/Burger/diff_24w09a_24w10a.html (https://pokechu22.github.io/Burger/diff_24w09a_24w10a.json)
2024-03-06 16:03:00	botifico	[Burger] Full data: https://pokechu22.github.io/Burger/24w10a.html (https://pokechu22.github.io/Burger/24w10a.json)
2024-03-06 16:05:01	botifico	[McUpdates] Minecraft snapshot 24w10a has just been published to the launcher!
2024-03-06 18:28:42	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-06 18:29:04	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-06 20:16:12	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-06 20:16:34	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-07 02:38:31	-->	Mateon2 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-03-07 02:39:43	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Ping timeout: 260 seconds)
2024-03-07 02:39:43	--	Mateon2 est maintenant connu sous le nom Mateon1
2024-03-07 05:35:21	<--	VectorTest (VectorTest@47.145.186.13) a quitté
2024-03-07 05:40:07	-->	MisterVector (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-03-07 05:40:07	<--	MisterVector (VectorTest@47.145.186.13) a quitté (Client Quit)
2024-03-07 05:41:36	-->	MisterVector (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-03-07 05:54:52	-->	SinZ (thelounge@grimm.361zn.is) a rejoint #mcdevs
2024-03-07 06:12:55	<--	SinZ (thelounge@grimm.361zn.is) a quitté (Quit: The Lounge - https://thelounge.chat)
2024-03-07 09:10:13	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-07 09:10:35	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-07 16:29:55	<--	magmaus3 (~magmaus3@user/magmaus3) a quitté (Quit: Ping timeout (120 seconds))
2024-03-07 16:30:13	-->	magmaus3 (~magmaus3@user/magmaus3) a rejoint #mcdevs
2024-03-07 16:50:14	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-07 16:50:36	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-07 17:20:14	-->	stack (~StackDoub@195.252.219.49) a rejoint #mcdevs
2024-03-07 17:58:44	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-07 17:59:05	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-07 22:00:15	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-07 22:00:37	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-07 23:54:26	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-08 00:02:56	<--	sdomi (~meow@sakamoto.pl) a quitté (Ping timeout: 268 seconds)
2024-03-08 00:03:39	-->	sdomi (~meow@sakamoto.pl) a rejoint #mcdevs
2024-03-08 00:40:15	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-08 00:40:37	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-08 01:00:40	-->	VectorTest (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-03-08 01:02:59	<--	MisterVector (VectorTest@47.145.186.13) a quitté (Ping timeout: 264 seconds)
2024-03-08 01:18:45	<--	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-08 01:19:05	-->	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a rejoint #mcdevs
2024-03-08 02:34:19	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-03-08 02:57:37	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-08 02:59:53	chibill	I have been porting old MCP mappings (Alpha, Beta and old releases.) To the Tiny File mappings that Enigma can load.
2024-03-08 03:00:10	chibill	To dig into the older protocol info. 
2024-03-08 03:30:47	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Leaving)
2024-03-09 01:08:31	<--	SpaceManiac (~SpaceMani@c-73-116-110-236.hsd1.ca.comcast.net) a quitté (Ping timeout: 260 seconds)
2024-03-09 01:10:09	-->	SpaceManiac (~SpaceMani@c-73-116-110-236.hsd1.ca.comcast.net) a rejoint #mcdevs
2024-03-09 04:45:45	<--	mbaxter (~mbax@user/mbaxter) a quitté (Quit: bye!)
2024-03-09 04:46:13	-->	mbaxter (~mbax@user/mbaxter) a rejoint #mcdevs
2024-03-09 08:32:27	<--	VectorTest (VectorTest@47.145.186.13) a quitté
2024-03-09 08:34:16	-->	MisterVector (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-03-09 15:21:18	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 255 seconds)
2024-03-09 15:21:58	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-03-09 22:08:33	<--	Thinkofname (~thinkthin@37.205.12.211) a quitté (Ping timeout: 255 seconds)
2024-03-09 22:23:37	-->	Thinkofname (~thinkthin@37.205.12.211) a rejoint #mcdevs
2024-03-09 22:50:36	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 256 seconds)
2024-03-09 22:51:03	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-03-09 23:42:33	-->	ZacSharp92 (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-09 23:46:41	--	ZacSharp92 est maintenant connu sous le nom ZacSharp
2024-03-10 00:16:59	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-03-10 00:22:43	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-10 00:50:23	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-03-10 06:09:06	<--	MisterVector (VectorTest@47.145.186.13) a quitté
2024-03-10 06:10:49	-->	MisterVector (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-03-10 08:04:41	<--	balrog (znc@user/balrog) a quitté (Ping timeout: 268 seconds)
2024-03-10 08:09:13	-->	balrog (znc@user/balrog) a rejoint #mcdevs
2024-03-10 19:30:29	<--	yosafbridge (~yosafbrid@static.38.6.217.95.clients.your-server.de) a quitté (Quit: Leaving)
2024-03-10 19:39:26	-->	yosafbridge (~yosafbrid@static.38.6.217.95.clients.your-server.de) a rejoint #mcdevs
2024-03-10 20:00:32	-->	dcraftbg (~dcraftbg@185.217.243.43) a rejoint #mcdevs
2024-03-10 20:00:38	dcraftbg	Hello?
2024-03-10 20:00:59	dcraftbg	Is anyone on right now?
2024-03-10 20:01:59	pokechu22	Hi
2024-03-10 20:02:09	dcraftbg	Hello!
2024-03-10 20:02:14	dcraftbg	So
2024-03-10 20:02:17	dcraftbg	I have a question
2024-03-10 20:02:32	dcraftbg	related to the ping packets
2024-03-10 20:02:39	dcraftbg	refering to wiki.vg
2024-03-10 20:03:24	dcraftbg	So There's these legacy ping packets right? I wanted to ask, how exactly do you 'know' you are in the Handshake mode?
2024-03-10 20:04:22	pokechu22	There's no automatic way of checking and it's a bit of a mess
2024-03-10 20:04:23	dcraftbg	Because from what I saw, launchers tend to connect to the server, use a handshake in order to enter 'handskae mode' and then close the socket, only to then send the legacy ping 
2024-03-10 20:04:39	dcraftbg	Oh
2024-03-10 20:04:40	pokechu22	oh, that's a little more complicated
2024-03-10 20:04:52	dcraftbg	Yeah because before it was pretty straight-forward
2024-03-10 20:04:53	dcraftbg	like
2024-03-10 20:04:57	dcraftbg	connect and then ping
2024-03-10 20:05:09	dcraftbg	boom you know you were in handshake mode so a 0xFE would mean legacy ping
2024-03-10 20:05:20	pokechu22	As a server, you have to look at the incoming packet and try to parse it as a handshake packet, but if it *doesn't* make sense that way then you try parsing it as one of the legacy ping packets
2024-03-10 20:05:42	dcraftbg	Thanks for that
2024-03-10 20:05:44	dcraftbg	But
2024-03-10 20:05:50	dcraftbg	I'm in a bit of a pickle right now
2024-03-10 20:05:53	pokechu22	As a client, you just send the handshake packet. If the server is running 1.6 or earlier, then it won't respond nicely to that, but I don't think modern clients send the legacy ping packets
2024-03-10 20:06:07	pokechu22	If you're sending a handshake packet and getting a legacy ping back, that means something's wrong with your handshake packet probably
2024-03-10 20:06:22	dcraftbg	since I collect all incomming messages from the client that connects
2024-03-10 20:06:31	dcraftbg	like all incoming traffic for that address
2024-03-10 20:06:39	dcraftbg	and collect them into one big bundle
2024-03-10 20:06:44	dcraftbg	to then parse as individual packets
2024-03-10 20:06:49	dcraftbg	and could there be a world
2024-03-10 20:06:58	dcraftbg	where length was 0xFE and it was a real packet?
2024-03-10 20:07:21	dcraftbg	Or 0xFE was legacy ping
2024-03-10 20:07:27	dcraftbg	but because I collected the whole bundle
2024-03-10 20:07:30	dcraftbg	and the length made sense 
2024-03-10 20:07:36	dcraftbg	it got treated weirdly
2024-03-10 20:07:38	pokechu22	I don't think anything stops it, even for a handshake packet... but note that you'll only get a legacy ping as the *very first* packet the client ever sends
2024-03-10 20:07:54	pokechu22	so once you've gotten a valid handshake packet, you don't need to worry about the legacy ping at all
2024-03-10 20:08:11	dcraftbg	Thats interesting
2024-03-10 20:08:16	dcraftbg	because from what I saw
2024-03-10 20:08:24	dcraftbg	the launcher connected to the server
2024-03-10 20:08:28	dcraftbg	sent the handshake packet
2024-03-10 20:08:35	dcraftbg	and then I got a weird packet
2024-03-10 20:08:44	dcraftbg	whose length translated to 0xFe
2024-03-10 20:08:52	dcraftbg	which is the legacy packet
2024-03-10 20:09:00	dcraftbg	AFTER a handshake was made
2024-03-10 20:09:05	dcraftbg	and it closed the connection
2024-03-10 20:09:08	dcraftbg	which is kind of weird
2024-03-10 20:09:29	pokechu22	If it closed the connection and opened a new one, then you should treat it as a whole new connection
2024-03-10 20:09:44	pokechu22	I might be wrong about the client/launcher not sending the legacy ping... will check
2024-03-10 20:09:45	dcraftbg	yeah
2024-03-10 20:10:13	dcraftbg	Also can I vent about something annoying related to sockets on windows? You might be able to help me with the situation
2024-03-10 20:10:24	pokechu22	I'm not super familiar with them, but sure :)
2024-03-10 20:10:57	dcraftbg	So basically I've been struggling to write a server for MC on windows
2024-03-10 20:11:04	dcraftbg	mainly due to the fact that the windows firewall
2024-03-10 20:11:18	dcraftbg	blocks connections that are from the same family but are different types
2024-03-10 20:11:22	dcraftbg	whereas on linux
2024-03-10 20:11:25	dcraftbg	from my limited testing
2024-03-10 20:11:34	dcraftbg	it allows connections that are from the same family
2024-03-10 20:11:39	dcraftbg	AF_INET family
2024-03-10 20:11:45	dcraftbg	particularly
2024-03-10 20:12:12	dcraftbg	The whole thing is, I had to write my entire server in TCP sockets which is very annoying
2024-03-10 20:12:15	dcraftbg	and had its quirks
2024-03-10 20:12:37	dcraftbg	Because the MC launcher on windows for some reason, opened a TCP connection
2024-03-10 20:12:39	dcraftbg	to the server
2024-03-10 20:12:54	dcraftbg	and localhost did not like that I have TCP vs UDP connections
2024-03-10 20:13:31	dcraftbg	It worked fine with LAN, since the firewall has zero control over the type of socket the client uses in LAN if its not on the same machine
2024-03-10 20:13:37	dcraftbg	and so it doesn't block it
2024-03-10 20:13:49	dcraftbg	I just don't see a world where you would need to block different type same family sockets
2024-03-10 20:13:52	dcraftbg	for 'security' reasons
2024-03-10 20:14:53	dcraftbg	And so I was wondering how I could configure the firewall to allow Cross-type connections
2024-03-10 20:15:09	dcraftbg	so I don't have to have a different code-base JUST for TCP sockets
2024-03-10 20:15:51	pokechu22	I unfortunately don't have any advice for that... but I'm pretty sure MC only uses TCP sockets (except for query and rcon, which are fairly niche and I believe are designed to be compatible with some old valve source engine thing?)
2024-03-10 20:16:18	dcraftbg	Really? Thats weird
2024-03-10 20:16:45	dcraftbg	Almost all game-making knowledge I have says UDP should be the primary one for speed reasons
2024-03-10 20:16:49	dcraftbg	So TCP it is?
2024-03-10 20:18:00	pokechu22	Pocket/bedrock edition uses UDP, but Java edition uses TCP... I think part of it is Notch didn't know what he was doing, but also for MC packet loss in general would be bad (if you lose a block change packet, it's not like later packets will include the same data to fix that, while most games mainly deal with movement and losing one position packet doesn't matter if you can just use the position
2024-03-10 20:18:02	pokechu22	from a later packet)
2024-03-10 20:18:28	dcraftbg	Makes a bit of sense
2024-03-10 20:18:29	pokechu22	Also I looked at it and it seems like clients *do* send the legacy ping if they fail to connect. You should get a "Can't ping" log message in that case
2024-03-10 20:19:09	dcraftbg	I'm not 100% sure
2024-03-10 20:19:17	dcraftbg	but at least from the tests I did
2024-03-10 20:19:23	dcraftbg	the client connected to the server
2024-03-10 20:19:26	dcraftbg	sent a handshake
2024-03-10 20:19:29	dcraftbg	and a status packet
2024-03-10 20:19:42	dcraftbg	my server responded (hopefully correctly) with a status response
2024-03-10 20:19:56	dcraftbg	and then the client disconnected and reconnected from a different port and sent a legacy ping
2024-03-10 20:20:34	dcraftbg	And of course, the server doesn't account for that (no legacy packet support yet) and so the client waits until saying "Can't ping" like you mentioned
2024-03-10 20:20:45	pokechu22	Yeah, that sounds like what happens when the client doesn't like your status response
2024-03-10 20:20:57	dcraftbg	Oh
2024-03-10 20:21:06	dcraftbg	thanks for the lead <3 I would have never guessed that
2024-03-10 20:21:28	dcraftbg	I think the packet response is constructed correctly
2024-03-10 20:21:33	dcraftbg	but just the body isn't
2024-03-10 20:21:41	dcraftbg	mind if I share some code?
2024-03-10 20:22:17	pokechu22	Sure
2024-03-10 20:23:00	dcraftbg	So my "response" looks something like the following (its built in rust so it uses that one string that allows inner '"'): {"version": {"name": "1.18.1","protocol": 757},"players": {"max": 69,"online": 5,"sample": []},"description": {"text": "Hello From Rust"},"enforcesSecureChat": true,"previewsChat": true}
2024-03-10 20:23:14	dcraftbg	No newlines, just some spaces
2024-03-10 20:23:21	dcraftbg	don't know if thats a problem for it
2024-03-10 20:23:45	dcraftbg	I do prefix the string as the docs says, with a varint length of it
2024-03-10 20:24:39	pokechu22	Hmm. One random guess: are you including a null-terminator on the string as well? You shouldn't but I have no idea if rust would default to doing that or not
2024-03-10 20:24:50	dcraftbg	Nope
2024-03-10 20:24:55	dcraftbg	No null terminator
2024-03-10 20:25:08	dcraftbg	Rust uses size+ptr type strings
2024-03-10 20:25:35	dcraftbg	as a note: just the ptr is copied over in the response 
2024-03-10 20:26:15	dcraftbg	lemme see tho, it might be due to the weird r#" strings and '"' could be getting removed
2024-03-10 20:26:35	dcraftbg	nope
2024-03-10 20:27:28	pokechu22	Can you post a hexdump of your packet?
2024-03-10 20:27:34	dcraftbg	yeah sure
2024-03-10 20:28:10	dcraftbg	gimme a sec
2024-03-10 20:29:25	dcraftbg	Let me know if its all good:
2024-03-10 20:29:27	dcraftbg	\xfe\x01\xfa\x00\x0b\x00M\x00C\x00|\x00P\x00i\x00n\x00g\x00H\x00o\x00s\x00t\x00;\x7f\x00\x1a\x00k\x00u\x00b\x00e\x00r\x00n\x00e\x00t\x00e\x00s\x00.\x00d\x00o\x00c\x00k\x00e\x00r\x00.\x00i\x00n\x00t\x00e\x00r\x00n\x00a\x00l\x00\x00c\xdd
2024-03-10 20:30:00	dcraftbg	oh wait
2024-03-10 20:30:02	dcraftbg	thats weird
2024-03-10 20:30:12	dcraftbg	I just noticed that the whole thing doesn't start with 0x0
2024-03-10 20:31:11	dcraftbg	I saw the error
2024-03-10 20:31:12	dcraftbg	lemme fix that
2024-03-10 20:31:14	dcraftbg	and see if it works
2024-03-10 20:31:31	dcraftbg	It does
2024-03-10 20:31:33	dcraftbg	holy smokes
2024-03-10 20:32:01	dcraftbg	tysm <3
2024-03-10 20:33:02	dcraftbg	I know it might be a big ask, but you seem like a nice guy who knows a thing or two about this whole thing, mind if we keep in contact somehow?
2024-03-10 20:36:20	pokechu22	Feel free to ask more questions in here. I'm not always available but there are several people in here with some knowledge who can help
2024-03-10 20:36:41	pokechu22	(it might be a while before you get an answer depending on who's around, of course)
2024-03-10 20:37:01	dcraftbg	Thanks for all the help either way. Love this comunity and thanks for all the help <3
2024-03-10 20:37:28	dcraftbg	It seems like quite a tight but wholesome comunity
2024-03-10 20:37:41	dcraftbg	pretty rare in todays day and age
2024-03-10 20:38:01	pokechu22	Yeah :)
2024-03-10 20:38:31	dcraftbg	Bye for now, GL with everything you're doing <3
2024-03-10 20:39:36	<--	dcraftbg (~dcraftbg@185.217.243.43) a quitté (Quit: leaving)
2024-03-10 20:47:01	<--	stack (~StackDoub@195.252.219.49) a quitté (Quit: Ping timeout (120 seconds))
2024-03-10 20:47:21	-->	stack (~StackDoub@195.252.219.49) a rejoint #mcdevs
2024-03-10 21:34:40	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-10 21:55:10	-->	bixilon_ (~bixilon@node-3.bixilon.de) a rejoint #mcdevs
2024-03-10 21:57:00	<--	bixilon (~bixilon@node-3.bixilon.de) a quitté (Quit: ZNC - https://znc.in)
2024-03-10 21:57:01	--	bixilon_ est maintenant connu sous le nom bixilon
2024-03-10 21:57:17	<--	bixilon (~bixilon@node-3.bixilon.de) a quitté (Remote host closed the connection)
2024-03-10 21:57:42	-->	bixilon (~bixilon@node-3.bixilon.de) a rejoint #mcdevs
2024-03-11 00:24:08	<--	stack (~StackDoub@195.252.219.49) a quitté (Quit: Ping timeout (120 seconds))
2024-03-11 00:24:27	-->	stack (~StackDoub@195.252.219.49) a rejoint #mcdevs
2024-03-11 01:14:32	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-03-11 01:14:35	-->	ZacSharp13 (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-11 04:14:39	--	ZacSharp13 est maintenant connu sous le nom ZacSharp
2024-03-11 05:18:58	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: ZacSharp)
2024-03-11 05:19:53	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-11 05:21:21	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Client Quit)
2024-03-11 08:22:36	<--	MisterVector (VectorTest@47.145.186.13) a quitté
2024-03-11 08:24:38	-->	MisterVector (VectorTest@47.145.186.13) a rejoint #mcdevs
2024-03-11 14:25:23	<--	sdomi (~meow@sakamoto.pl) a quitté (Ping timeout: 260 seconds)
2024-03-11 15:41:30	-->	dcraftbg (~dcraftbg@185.217.243.43) a rejoint #mcdevs
2024-03-11 15:41:35	dcraftbg	Hello :D
2024-03-11 15:43:25	dcraftbg	Is anyone on right now?
2024-03-11 15:57:05	dcraftbg	Maybe @pokechu22?
2024-03-11 15:58:22	dcraftbg	But all help is welcome
2024-03-11 15:58:24	dcraftbg	:D
2024-03-11 16:28:53	dcraftbg	...
2024-03-11 17:06:26	<--	dcraftbg (~dcraftbg@185.217.243.43) a quitté (Quit: Reconnecting)
2024-03-11 17:06:39	-->	dcraftbg (~dcraftbg@185.217.243.43) a rejoint #mcdevs
2024-03-11 17:07:17	dcraftbg	Hey is anyone on right now?
2024-03-11 17:22:25	<--	dcraftbg (~dcraftbg@185.217.243.43) a quitté (Quit: Lost terminal)
2024-03-11 17:27:54	-->	dcraftbg (~dcraftbg@185.217.243.43) a rejoint #mcdevs
2024-03-11 19:20:32	<--	balrog (znc@user/balrog) a quitté (Quit: Bye)
2024-03-11 19:42:46	<--	xoreaxeax (~xoreaxeax@user/daswf852) a quitté (Ping timeout: 255 seconds)
2024-03-11 19:55:02	lassipulkkinen	yes?
2024-03-11 20:01:50	-->	xoreaxeax (~xoreaxeax@user/daswf852) a rejoint #mcdevs
2024-03-11 20:06:28	dcraftbg	Anyone on right now?
2024-03-11 20:07:28	lassipulkkinen	me at least.. i just replied to you
2024-03-11 20:07:43	dcraftbg	Hiyo :D
2024-03-11 20:07:46	dcraftbg	I was wondering if I could
2024-03-11 20:07:52	dcraftbg	maybe ask a bit about server design
2024-03-11 20:08:37	dcraftbg	Specifically how to verify handshakes and connections, and kick those who connect and don't provide any packet
2024-03-11 20:09:40	lassipulkkinen	so you're asking about timeouts?
2024-03-11 20:09:58	dcraftbg	Something along those lines
2024-03-11 20:10:26	dcraftbg	I would love to make a 1 thread server, that can handle multiple connections, and kick invalid connect (no response) ones
2024-03-11 20:10:54	lassipulkkinen	The Notchian server I think has a rather long timeout before the handshake; haven't looked at that code, but just based on connecting via netcat.
2024-03-11 20:11:27	dcraftbg	Well I wouldn't really love to have a long timeout
2024-03-11 20:11:45	lassipulkkinen	For an application like minecraft you'll need asynchronous networking
2024-03-11 20:11:51	dcraftbg	Yeah
2024-03-11 20:11:53	dcraftbg	Well
2024-03-11 20:11:59	dcraftbg	I thought about using mio and rust
2024-03-11 20:12:09	dcraftbg	And I've gotten to the point of accepting connections
2024-03-11 20:12:14	lassipulkkinen	so having multiple handshakes going on at once should be no problem
2024-03-11 20:12:38	dcraftbg	Yeah, but my problem is long timeout times, in which no connect had happened
2024-03-11 20:12:41	dcraftbg	maybe in between events
2024-03-11 20:12:46	dcraftbg	I should check the time of connection
2024-03-11 20:12:49	dcraftbg	and last packet
2024-03-11 20:12:52	dcraftbg	to kick those
2024-03-11 20:12:56	dcraftbg	smth along those lines
2024-03-11 20:12:57	lassipulkkinen	so you're using mio already?
2024-03-11 20:13:07	dcraftbg	Yeah
2024-03-11 20:14:01	lassipulkkinen	ah, okay. mio has a timer feature, right? you should use that
2024-03-11 20:14:09	dcraftbg	Timer feature?
2024-03-11 20:14:43	lassipulkkinen	so you'll use the timer to get notified when a connection times out. or am i still misunderstanding the uestion?
2024-03-11 20:14:48	lassipulkkinen	*question
2024-03-11 20:15:10	dcraftbg	No no, Let me start over. Essentially how do I handle the case where a client connects but doesn't send anything after connecting
2024-03-11 20:16:15	lassipulkkinen	in async io, you should never ever be blocking on an individual connection. you have an event loop with all the sockets associated with it, and get an event when something happens on any of those
2024-03-11 20:16:31	lassipulkkinen	then you use a timeout to eventually kick unresponsive ones
2024-03-11 20:16:55	dcraftbg	Is there a way to register a timeout
2024-03-11 20:17:15	dcraftbg	Like for a given socket, set the timeout for inactivity
2024-03-11 20:17:52	dcraftbg	I have a rough idea of how that might be implemented, but I just can't exactly put my finger on it
2024-03-11 20:18:26	lassipulkkinen	is your server actually getting blocked on unresponsive connections at the moment? it's still unclear to me if that's your issue or if you're just wondering about timeouts
2024-03-11 20:18:47	lassipulkkinen	it shouldn't get blocked, it should just let them hang on for a while and then kick to save memory
2024-03-11 20:19:04	dcraftbg	Exactly the kick process is what I'm interested in
2024-03-11 20:19:15	dcraftbg	I don't currently get any of those
2024-03-11 20:19:20	lassipulkkinen	but your server is already properly async?
2024-03-11 20:19:29	dcraftbg	but I know that clogging the pipeline with those kinds of sockets is a potential problem
2024-03-11 20:19:32	dcraftbg	Yes
2024-03-11 20:19:33	dcraftbg	it does use async
2024-03-11 20:19:39	dcraftbg	Well sorta async
2024-03-11 20:19:41	dcraftbg	but yeah
2024-03-11 20:19:48	dcraftbg	mio
2024-03-11 20:19:53	lassipulkkinen	sorta? and what pipeline exactly?
2024-03-11 20:20:01	lassipulkkinen	mio is async if you use it correctly
2024-03-11 20:20:11	dcraftbg	Then yes
2024-03-11 20:21:17	dcraftbg	its async
2024-03-11 20:21:34	lassipulkkinen	it's basically an abstraction over epoll and other apis, and those should automatically round-robin over the connections or similar, so it shouldn't be getting "clogged" unless there's a disproportionate amount of dead clients, like in a ddos.
2024-03-11 20:21:49	dcraftbg	Yeah
2024-03-11 20:21:59	dcraftbg	I explicitly want to protect against DDoS attacks like those
2024-03-11 20:22:04	dcraftbg	hanging connections
2024-03-11 20:22:12	dcraftbg	Haven't tested it out myself
2024-03-11 20:22:17	dcraftbg	to see if its automatically handled
2024-03-11 20:22:20	dcraftbg	I imagine it isn't
2024-03-11 20:22:23	dcraftbg	but yeah
2024-03-11 20:24:38	lassipulkkinen	ddoses are difficult because you can't easily tell if they're happpening. but yeah, timeouts of course help.
2024-03-11 20:24:48	dcraftbg	I think saying it out loud helped me realise how simple it could be. By just storing the sockets in a pool with their date of last packet and iterating over them after getting any event so that you clear up any inactive ones
2024-03-11 20:25:14	dcraftbg	I don't know the performance implications of that
2024-03-11 20:25:17	dcraftbg	on like a large scale
2024-03-11 20:25:26	dcraftbg	but I don't think my server architecture is getting to that point anyway
2024-03-11 20:25:41	lassipulkkinen	i looked at the mio docs (have used rust before, but not using it at the moment). apparently it doesn't have a built-in timer helper thing. so yes, you will need to do that yourself.
2024-03-11 20:25:49	lassipulkkinen	with the poll timeout
2024-03-11 20:25:54	dcraftbg	YEah
2024-03-11 20:25:56	dcraftbg	*yeah
2024-03-11 20:26:04	dcraftbg	I saw that there isn't like an explicit timer thing
2024-03-11 20:26:09	dcraftbg	but it doesn't seem too bad
2024-03-11 20:26:09	lassipulkkinen	there are two ways of doing it, broadly
2024-03-11 20:26:45	dcraftbg	Since a poll will end once any event is gotten, even accept event, doing cleanup after each poll should be fine
2024-03-11 20:26:53	dcraftbg	and it probably wouldn't use an insane amount of memory
2024-03-11 20:28:10	dcraftbg	A single client structure could be as little as 8 bytes for the handle, 16 bytes for the address and another 8 for the date of creation in unix millis
2024-03-11 20:28:17	lassipulkkinen	you can either have a priority queue / heap of all the last packet dates like you said. the rust std has one of those, i think. or you can have a doubly-linked list, which _might_ be faster, but will only work if all the timeouts are equal.
2024-03-11 20:28:51	dcraftbg	I feel as tho a data structure that can somehow sort quickly
2024-03-11 20:28:57	dcraftbg	over the time of last packet
2024-03-11 20:28:59	dcraftbg	could be useful
2024-03-11 20:29:00	lassipulkkinen	of course you could have multiple linked lists for different timeouts
2024-03-11 20:29:49	dcraftbg	Something that can easily be iterated over starting from the oldest to the newest time of packets
2024-03-11 20:29:55	dcraftbg	so you don't have to iterate over all of the
2024-03-11 20:30:02	dcraftbg	items in the pool
2024-03-11 20:30:12	dcraftbg	just iterate until you reach a date (time) 
2024-03-11 20:30:15	lassipulkkinen	read my previous two messages. std::collections::BinaryHeap.
2024-03-11 20:30:24	dcraftbg	Yeah
2024-03-11 20:30:27	dcraftbg	I'll check that out
2024-03-11 20:30:30	dcraftbg	tysm <3!
2024-03-11 20:31:36	dcraftbg	BinaryHeap seems like exactly what I need
2024-03-11 20:31:42	dcraftbg	if I want to make it 'production' scale
2024-03-11 20:32:00	dcraftbg	A basic Vec will do for now I guess
2024-03-11 20:32:16	dcraftbg	I don't have those kind of ambitions about this mini-project just yet
2024-03-11 20:33:07	dcraftbg	But yeah tysm for all the help <3
2024-03-11 20:35:31	lassipulkkinen	i did realize one caveat with the priority queue option - you can't remove from the middle, e.g. if someone disconnects. probably not a problem since you can just discard those when they time out.
2024-03-11 20:35:56	dcraftbg	I mean I'll find a way to work that in
2024-03-11 20:35:57	dcraftbg	:D
2024-03-11 20:36:05	dcraftbg	But ty <3
2024-03-11 20:36:24	lassipulkkinen	i'm currently using the "array of linked lists" option since i'm using C and was too lazy to work out how to make a binary heap.
2024-03-11 20:37:00	dcraftbg	Well the data structure isn't all too important if you're talking a scale of <100 players
2024-03-11 20:37:20	dcraftbg	Heck even <200 can work with a Vec without too much of a compromise
2024-03-11 20:38:42	lassipulkkinen	yeah, though since you're worried about ddos you should probably consider the case of ~ 10 or 100 times more unauthenticated connections than players.
2024-03-11 20:38:58	dcraftbg	Ye
2024-03-11 20:39:01	dcraftbg	I just wanted to know
2024-03-11 20:39:04	dcraftbg	how I could work that in
2024-03-11 20:39:12	dcraftbg	to this 'library' thing
2024-03-11 20:39:15	dcraftbg	I'm making
2024-03-11 20:39:38	dcraftbg	and being able to kind of express that through into words helped a ton
2024-03-11 20:39:50	lassipulkkinen	it happens, yeah
2024-03-11 20:39:56	dcraftbg	Ty <3
2024-03-11 20:40:09	dcraftbg	Oh
2024-03-11 20:40:10	dcraftbg	and also
2024-03-11 20:40:15	dcraftbg	you could use a sorted array
2024-03-11 20:40:18	dcraftbg	now that I think of it
2024-03-11 20:40:32	dcraftbg	insertions into sorted arrays aren't too bad either
2024-03-11 20:41:04	dcraftbg	also a memmove isn't that expensive
2024-03-11 20:41:38	lassipulkkinen	it isn't "expensive" w.r.t. the amount of memory but it scales badly when you're doing it per connection.
2024-03-11 20:41:45	lassipulkkinen	basic algorithmic complexity
2024-03-11 20:41:51	dcraftbg	Yea
2024-03-11 20:41:58	-->	balrog (znc@user/balrog) a rejoint #mcdevs
2024-03-11 20:42:07	dcraftbg	But even with like upwards to 300 entries
2024-03-11 20:42:17	lassipulkkinen	300 * 300 = 60000
2024-03-11 20:42:24	dcraftbg	its still going to be relatively fast if you're just bothered about hung ups
2024-03-11 20:42:24	dcraftbg	oh
2024-03-11 20:42:35	dcraftbg	thats a different story
2024-03-11 20:42:57	dcraftbg	I was still thinking of verification once at the start
2024-03-11 20:42:59	dcraftbg	yeah
2024-03-11 20:43:01	dcraftbg	true
2024-03-11 20:43:09	dcraftbg	It does get expensive as you go further
2024-03-11 20:43:29	dcraftbg	Binary Map is your best bet I suppose
2024-03-11 20:43:37	dcraftbg	*heap
2024-03-11 20:44:07	dcraftbg	alright Imma go now. Thanks for everything :D
2024-03-11 20:44:41	lassipulkkinen	well, what i just said is slightly inaccurate. really it would be like "sum of all numbers 1..300" if they're connecting one by one. but still, there's no reason to have O(n^2) timeouts.
2024-03-11 20:44:49	lassipulkkinen	bye
2024-03-11 20:45:04	dcraftbg	Bye!
2024-03-11 20:45:19	dcraftbg	Also you probably don't have to check all of them
2024-03-11 20:45:22	dcraftbg	like at some point
2024-03-11 20:45:25	dcraftbg	it does get cut off
2024-03-11 20:45:34	dcraftbg	if its a sorted array
2024-03-11 20:45:40	dcraftbg	but updating it will be painful
2024-03-11 20:45:45	dcraftbg	like on each packet
2024-03-11 20:45:56	dcraftbg	anywho
2024-03-11 20:46:00	dcraftbg	thanks for everything :D
2024-03-11 20:46:03	dcraftbg	cya!
2024-03-11 20:46:05	<--	dcraftbg (~dcraftbg@185.217.243.43) a quitté (Quit: leaving)
2024-03-11 22:01:07	<--	stack (~StackDoub@195.252.219.49) a quitté (Quit: Ping timeout (120 seconds))
2024-03-11 22:01:29	-->	stack (~StackDoub@195.252.219.49) a rejoint #mcdevs
2024-03-11 23:58:49	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Ping timeout: 255 seconds)
2024-03-11 23:59:00	-->	Mateon2 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-03-12 00:01:17	--	Mateon2 est maintenant connu sous le nom Mateon1
2024-03-12 03:26:16	<--	stack (~StackDoub@195.252.219.49) a quitté (Quit: Ping timeout (120 seconds))
2024-03-12 03:26:33	-->	stack (~StackDoub@195.252.219.49) a rejoint #mcdevs
2024-03-12 13:00:12	-->	LyzaTheAnnihilat (~LyzaTheAn@2a02:a213:273d:7b80:71f3:a3c7:461d:233a) a rejoint #mcdevs
2024-03-12 15:42:53	<--	balrog (znc@user/balrog) a quitté (Remote host closed the connection)
2024-03-12 15:45:14	-->	balrog (znc@user/balrog) a rejoint #mcdevs
2024-03-12 15:47:34	<--	balrog (znc@user/balrog) a quitté (Remote host closed the connection)
2024-03-12 15:49:45	-->	balrog (znc@user/balrog) a rejoint #mcdevs
2024-03-12 21:37:15	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-12 21:47:22	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-03-12 21:50:36	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-12 22:46:24	<--	Processus42 (~lel-amri@static.121.11.12.49.clients.your-server.de) a quitté (Quit: ZNC 1.8.2 - https://znc.in)
2024-03-12 22:46:47	-->	Processus42 (~lel-amri@2a01:4f8:c17:d3e5::1) a rejoint #mcdevs
2024-03-13 00:22:34	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: Client closed)
2024-03-13 01:01:04	<--	LyzaTheAnnihilat (~LyzaTheAn@2a02:a213:273d:7b80:71f3:a3c7:461d:233a) a quitté (Read error: Connection reset by peer)
2024-03-13 01:05:52	-->	grumble (grumble@user/grumble) a rejoint #mcdevs
2024-03-13 01:07:05	-->	ZacSharp (~ZacSharp@user/zacsharp) a rejoint #mcdevs
2024-03-13 01:07:25	<--	Mateon1 (~Thunderbi@user/mateon1) a quitté (Quit: Mateon1)
2024-03-13 01:41:48	-->	Mateon1 (~Thunderbi@user/mateon1) a rejoint #mcdevs
2024-03-13 04:53:57	<--	ZacSharp (~ZacSharp@user/zacsharp) a quitté (Quit: ZacSharp)
2024-03-13 07:08:02	-->	MiniDigger098 (~MiniDigge@user/minidigger) a rejoint #mcdevs
2024-03-13 07:09:14	-->	_123DMWM_ (~123DMWM@me.123dmwm.com) a rejoint #mcdevs
2024-03-13 07:09:51	<--	MiniDigger09 (~MiniDigge@user/minidigger) a quitté (Quit: Ping timeout (120 seconds))
2024-03-13 07:09:52	<--	_123DMWM (~123DMWM@167.114.174.122) a quitté (Remote host closed the connection)
2024-03-13 07:09:52	--	MiniDigger098 est maintenant connu sous le nom MiniDigger09
2024-03-13 09:39:29	-->	Guest99 (~Guest99@31-149-29-130.biz.kpn.net) a rejoint #mcdevs
2024-03-13 09:39:54	<--	Guest99 (~Guest99@31-149-29-130.biz.kpn.net) a quitté (Client Quit)
2024-03-13 09:40:15	-->	Guest99 (~Guest99@31-149-29-130.biz.kpn.net) a rejoint #mcdevs
2024-03-13 09:40:37	<--	Guest99 (~Guest99@31-149-29-130.biz.kpn.net) a quitté (Client Quit)
2024-03-13 11:47:47	-->	MiniDigger098 (~MiniDigge@user/minidigger) a rejoint #mcdevs
2024-03-13 11:49:51	<--	MiniDigger09 (~MiniDigge@user/minidigger) a quitté (Ping timeout: 252 seconds)
2024-03-13 11:49:51	--	MiniDigger098 est maintenant connu sous le nom MiniDigger09
2024-03-13 11:50:24	<--	killme (~killmePI@ovh4.avatarmc.com) a quitté (Ping timeout: 252 seconds)
2024-03-13 11:50:36	-->	killme (~killmePI@ovh4.avatarmc.com) a rejoint #mcdevs
2024-03-13 13:07:50	<--	stack (~StackDoub@195.252.219.49) a quitté (Quit: Ping timeout (120 seconds))
2024-03-13 13:08:08	-->	stack (~StackDoub@195.252.219.49) a rejoint #mcdevs
2024-03-13 13:30:48	--	_123DMWM_ est maintenant connu sous le nom _123DMWM
2024-03-13 15:28:47	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 264 seconds)
2024-03-13 15:29:10	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-03-14 13:34:42	<--	caleb_ (ca329e08ca@user/ace) a quitté (Remote host closed the connection)
2024-03-14 13:34:43	<--	vismie (c8b263ae0e@2a03:6000:1812:100::fb8) a quitté (Write error: Connection reset by peer)
2024-03-14 13:34:43	<--	BratishkaErik (fd46852e72@user/BratishkaErik) a quitté (Write error: Connection reset by peer)
2024-03-14 13:34:44	<--	xtex (250b76165c@2a03:6000:1812:100::12fc) a quitté (Write error: Connection reset by peer)
2024-03-14 13:35:04	-->	BratishkaErik (fd46852e72@user/BratishkaErik) a rejoint #mcdevs
2024-03-14 13:35:05	-->	vismie (c8b263ae0e@2a03:6000:1812:100::fb8) a rejoint #mcdevs
2024-03-14 13:35:11	-->	xtex (250b76165c@2a03:6000:1812:100::12fc) a rejoint #mcdevs
2024-03-14 13:35:11	-->	caleb_ (ca329e08ca@user/ace) a rejoint #mcdevs
2024-03-14 14:17:28	-->	Guest14 (~Guest14@89.205.224.108) a rejoint #mcdevs
2024-03-14 14:18:07	Guest14	Does anyone know how to correctly send over the server list ping json data in python?
2024-03-14 14:19:58	<--	Guest14 (~Guest14@89.205.224.108) a quitté (Quit: Connection closed)
2024-03-14 14:27:40	-->	Guest14 (~Guest14@89.205.224.230) a rejoint #mcdevs
2024-03-14 14:28:25	<--	Guest14 (~Guest14@89.205.224.230) a quitté (Client Quit)
2024-03-14 14:49:29	-->	Guest14 (~Guest14@89.205.224.42) a rejoint #mcdevs
2024-03-14 14:49:58	<--	Guest14 (~Guest14@89.205.224.42) a quitté (Client Quit)
2024-03-14 15:16:47	-->	Guest14 (~Guest14@89.205.224.175) a rejoint #mcdevs
2024-03-14 15:19:18	<--	Guest14 (~Guest14@89.205.224.175) a quitté (Client Quit)
2024-03-14 15:21:33	<--	dav1d (~dav1d@user/dav1d) a quitté (Ping timeout: 272 seconds)
2024-03-14 15:33:38	-->	dav1d (~dav1d@user/dav1d) a rejoint #mcdevs
2024-03-14 15:49:32	<--	dav1d (~dav1d@user/dav1d) a quitté (Ping timeout: 252 seconds)
2024-03-14 15:50:32	-->	dav1d (~dav1d@user/dav1d) a rejoint #mcdevs
2024-03-14 16:33:09	<--	magmaus3 (~magmaus3@user/magmaus3) a quitté (Quit: :3)
2024-03-14 16:49:41	-->	magmaus3 (~magmaus3@user/magmaus3) a rejoint #mcdevs
2024-03-14 16:54:06	-->	emilknievel (~emilkniev@78-82-73-180.customers.ownit.se) a rejoint #mcdevs
2024-03-14 17:15:01	botifico	[McUpdates] Minecraft snapshot 24w11a has just been published to the launcher!
2024-03-14 17:22:40	botifico	[Burger] New data now avaliable for 24w11a:
2024-03-14 17:22:43	botifico	[Burger] Diff from 24w10a: https://pokechu22.github.io/Burger/diff_24w10a_24w11a.html (https://pokechu22.github.io/Burger/diff_24w10a_24w11a.json)
2024-03-14 17:22:45	botifico	[Burger] Full data: https://pokechu22.github.io/Burger/24w11a.html (https://pokechu22.github.io/Burger/24w11a.json)
2024-03-14 18:29:37	<--	chibill (~chibill@c-67-175-64-113.hsd1.il.comcast.net) a quitté (Quit: ZNC 1.8.2+deb2build5 - https://znc.in)
2024-03-14 18:31:24	-->	chibill (~chibill@c-67-175-64-113.hsd1.il.comcast.net) a rejoint #mcdevs
2024-03-14 19:10:29	-->	NoahvdAa9 (~NoahvdAa@user/noahvdaa) a rejoint #mcdevs
2024-03-14 19:10:44	-->	antoniomika2 (~antonio@user/antoniomika) a rejoint #mcdevs
2024-03-14 19:11:32	-->	chibill_ (~chibill@c-67-175-64-113.hsd1.il.comcast.net) a rejoint #mcdevs
2024-03-14 19:12:33	<--	chibill (~chibill@c-67-175-64-113.hsd1.il.comcast.net) a quitté (Ping timeout: 260 seconds)
2024-03-14 19:12:34	<--	sudden (~cat@user/sudden) a quitté (Ping timeout: 264 seconds)
2024-03-14 19:12:34	<--	antoniomika (~antonio@user/antoniomika) a quitté (Read error: Connection reset by peer)
2024-03-14 19:12:34	--	antoniomika2 est maintenant connu sous le nom antoniomika
2024-03-14 19:12:34	--	chibill_ est maintenant connu sous le nom chibill
2024-03-14 19:12:47	<--	NoahvdAa (~NoahvdAa@user/noahvdaa) a quitté (Ping timeout: 260 seconds)
2024-03-14 19:12:48	<--	kashike (kashike@user/kashike) a quitté (Ping timeout: 260 seconds)
2024-03-14 19:12:49	--	NoahvdAa9 est maintenant connu sous le nom NoahvdAa
2024-03-14 19:14:05	-->	kashike (kashike@2a01:4f8:c0c:9876::1) a rejoint #mcdevs
2024-03-14 19:14:13	-->	sudden (~cat@user/sudden) a rejoint #mcdevs
2024-03-14 20:41:37	-->	dcraftbg (~dcraftbg@185.217.243.43) a rejoint #mcdevs
2024-03-14 20:41:49	dcraftbg	Heyo! Is anyone online?
2024-03-14 21:06:01	lassipulkkinen	yes
2024-03-14 21:11:07	dcraftbg	Hello!
2024-03-14 21:11:11	dcraftbg	So I have a question
2024-03-14 21:11:24	dcraftbg	About the Login Start packet
2024-03-14 21:11:51	dcraftbg	When I received that packet I got the username entirely correct but no UUID was provided 
2024-03-14 21:12:25	dcraftbg	And on the Wiki it says that after the username the packet follows up with the UUID
2024-03-14 21:12:33	dcraftbg	But I don't get it
2024-03-14 21:15:07	lassipulkkinen	Checked the source - that field is definitely still there, and you should be getting it.
2024-03-14 21:15:31	dcraftbg	Well in here it says that I have 0 things left after the username. I'm gonna give it a check one more time
2024-03-14 21:15:35	dcraftbg	but yeah
2024-03-14 21:16:27	dcraftbg	I just checked it and yeah. The packet was just 15 bytes without any UUID
2024-03-14 21:17:33	lassipulkkinen	If you send a Login Success anyway, do you get a valid Login Acknowledged back? If not, maybe you're not handling packet framing properly.
2024-03-14 21:17:52	dcraftbg	Lemme give it a try
2024-03-14 21:19:11	dcraftbg	It has a lot of fields
2024-03-14 21:19:54	dcraftbg	I don't know how to exactly fill up those fields tho. Like UUID and Username
2024-03-14 21:19:57	dcraftbg	and a lot of other properties
2024-03-14 21:23:13	-->	Guest1035 (~Guest1035@040-113-045-062.dynamic.caiway.nl) a rejoint #mcdevs
2024-03-14 21:24:21	lassipulkkinen	They don't really matter tbh; Username is self-explanatory, and the client doesn't care what the UUID is either. Number Of Properties can be 0.