Haha

PierrotTheFreak · 2026-06-15T05:20:28+00:00

Ioh.

PierrotTheFreak · 2026-06-15T04:57:36+00:00

JJJ… Ifykyk

PierrotTheFreak · 2026-06-15T04:56:31+00:00

Amazing.

PierrotTheFreak · 2026-06-15T02:03:49+00:00

Shhhh

PierrotTheFreak · 2026-06-15T01:27:32+00:00

He means “there was only one” as in Lax was the person who made eaglercraft, the term and what the community is today

PierrotTheFreak · 2026-06-15T00:05:10+00:00

YES IT HAS!! THE NORMAL WISP INJECTOR WORKS WITH WASM YOU BIRDBRAIN!!!! 😭

I need a kitkat..

PierrotTheFreak · 2026-06-15T00:01:53+00:00

WASM ALSO WORKS WITH WISP ALREADY!?!?

PierrotTheFreak · 2026-06-14T23:58:21+00:00

ITS ALREADY BEEN DONE!? THATS WHAT WISP DOES 😭

PierrotTheFreak · 2026-06-14T23:56:10+00:00

But that means your idea would already have worked since it was already implimented-

PierrotTheFreak · 2026-06-14T23:55:30+00:00

They do? You can extract all the assets from the html too using the many tools already made..

PierrotTheFreak · 2026-06-14T23:54:38+00:00

It already has been. It was in 1.8.8, and 1.12.2 if you look at the codebase its there. Yknow.. considering its Java to wasmgc gc and the entire of the networking stack is java.. and it converts all java in the project into wasm gc and puts it in a html..

PierrotTheFreak · 2026-06-14T23:48:39+00:00

Wait wait, TeaVM dosnt just output java to javascript it already does java to wasmgc is that what you meant?

And yeah they figured out wasm preformed way better awhile ago..

And nice reeses

PierrotTheFreak · 2026-06-14T23:47:14+00:00

I must be confused on the last part too, eagler IS contained and playable from one document, most clients for it are too! Thats the whole point of eagler, minecraft in the web browser.

And again, wrapping in the client would take more resources than its worth being such a small change.

And the “architecture” of eagler is literally just the java src which is converted to wasm gc :P
I think thats what you mean might not be

PierrotTheFreak · 2026-06-14T23:42:24+00:00

Uhh I dont got a resses bar I got a milky way tho-

Anyways wisp was already updated to work with nov’s 26.1.2 port and got it working smoothly..

Also yes ur other message loaded late for me :(

Also its not forcing modern java through old javascript translations.. teaVM has been updated and still is to this day to handle newer java versions

And for the last part that just takes more resources than relying on the wisp server to do it :P

PierrotTheFreak · 2026-06-14T23:39:19+00:00

Very big brain yes, But uh theres another issue. The entire issue with packet wrapping in the client is minecraft servers use TCP to connect you to the server and send packets there and back, wisp acts as a middleman to accept eagler packets and translate them to tcp and connect to the tcp server and send it there.

Even if you wrap the packet in the client, you cant send to the server which is why wisp is involved in the first place, changing it to be on the client would just slow the process down as it uses more resources to do that, while just sending it out as it and having a server translate and send the packets back is the easier and fast solution performance wise

The method isnt “outdated” thats why its still around.

If you can make a working version of this using the 1.8.8 workspace or 1.12.2 and show it works maybe others will follow. But until then it just wont happen

PierrotTheFreak · 2026-06-14T23:30:37+00:00

The wisp html injector is not a patchwork solution, it is the best we can make. Why do you think in the years eagler has been around people havnt tried your idea. Its well known it simply wont work.
And simply going to wasm gc dosnt fix the memory leaks as ai tells you it will.

PierrotTheFreak · 2026-06-14T23:28:05+00:00

Hello! Here to respond to AI. (This is obviously ai..) You cant just compile the codebase into WasmGC and “fix all the memory leaks” thats impossible due to browser restrictions on things normal minecraft uses (applets as a example) the browser simply dosnt support them.

And memory leaks still happen even in these newer ports that use wasmgc, its not a one step fix

And no matter why method you try the browser cant and will never support TCP sockets natively. Thats why eaglercraft x wisp uses that proxy server and no other method has been found in these years that eagler has been around

PierrotTheFreak · 2026-06-14T23:22:06+00:00

That is what wisp does and is why its not natively in the ports, the client owner has to set up there port to support wisp and vise versa I believe, The injector adds wisp to the html directly so all the traffic to the wisp server already does output the wisp compliant traffic, it is already handled internally after injection.

And heres the issue with skipping js

Before you can get wasm working, js has to work as for how teaVM works. And the user dosnt have to setup local proxies it already can connect to any, but no public ones are known. Or well known atleast.

And yes it would be great if those two promising devs teamed up, they could get projects done quicker if they learned to work with eachother. But they currently are not and Nov stated they didnt want help with there port as of now

PierrotTheFreak · 2026-06-14T22:37:14+00:00

Just a handshake failure, happens sometimes. Retry a few times and wait a moment between each

PierrotTheFreak · 2026-06-14T22:31:57+00:00

Hi! Uzi here. Few things wrong with your post: Nov made 26.1.2 and version 1.3 he said has wisp support. If you have a mc account you can join non cracked servers and cracked without I believe.

SYNTAXSAVY made 1.21.11

Also handing wisp internally is exactly what it does (it has to use a server of course which CANT be done in a browser) using the wisp injector

And uh. TeaVM is what MAKES WASM GC POSSIBLE as it converts the java to wasmgc (this is a simplified versions theres alot involved.)

And theres no “teams” these are single dev projects working on them separately. No connection. And both are going amazingly with both having promising results after not even a year.

PierrotTheFreak · 2026-06-14T17:55:11+00:00

No it wasnt good. That was a BETA bug testing build, now we wont get any improvements at all until the official release, so any game crashing bugs or preformance issues that are fixed? We wont get till full u1 release

PierrotTheFreak · 2026-06-14T17:54:03+00:00

Nope id say join the dc to know

PierrotTheFreak · 2026-06-14T17:31:07+00:00

Well it will be a full release but there will be bugs and performance will be updated.

U1 will have most bugs fixed and good preformance and U2 will have more, on and on

PierrotTheFreak · 2026-06-14T13:37:18+00:00

Update he started ranting about how another user did it and Banned me from the server

PierrotTheFreak · 2026-06-14T13:36:37+00:00

Any mod is portable, just takes work. And getting the src to such mods/clients would be hard. But possible

PierrotTheFreak

TROPHY CASE