disguise api

[yannicklamprecht]

relates to #10584

Adds a simple disguise api that also makes sure that invalid entity data, not belonging to the type that is faked, is filtered.
It also adds a server generator module to reduce maintenance of the entity data filter.

tldr; The API provides a way to disguise any entity as another or a player with having the possibility to interact with the entity like with any others. The big advantage is that you've the whole vanilla logic and Mob Goal and Pathfinding included without hassle.

Testing the changes can be done using the following snippet:
https://gist.github.com/yannicklamprecht/639acba127a54f5617e1281f099b7aff

TODO:

• Add JavaDoc
• remove test plugin code
• comment paper-server-generator
• figure out how to get teams working with real teams, client side ones worked in my fork Non issue just use the Entity#getName() instead of the Entity#getScoreboardEntryName()
• Persist and load DisguiseData to avoid client disconnects when moving away and approaching again. see disguise api #10478 (comment)

[yannicklamprecht]

Tested with:
https://gist.github.com/yannicklamprecht/639acba127a54f5617e1281f099b7aff

Only open part is the discussion for a common generator module

[yannicklamprecht]

We should probably move the common generator classes into a separate module to reduce duplications.

[MiniDigger]

this is complicated enough that we prolly want a lil docs page with an example, but that can wait till after its merged and we know the final api design

[yannicklamprecht]

this is complicated enough that we prolly want a lil docs page with an example, but that can wait till after its merged and we know the final api design

Thought of adding a Java 18+ snippet to the javadoc but a docs page will be better.

EDIT: Or do you mean regarding code generation?

[MiniDigger]

I meant the api itself

[yannicklamprecht]

Addressed issue with experience orbs by filtering them out. Mentioned that exclusion in the JavaDoc.

Additionally found an issue with ElderGuardian when disguising them as a Player on the client side. That happens only when the ElderGuardian is in the water. First thought is the ElderGuardian stream sucking health from other entities. To be sure I need to deobf the client stacktrace.

Failed to handle packet adm@395c0068
java.lang.ClassCastException: class gct cannot be cast to class ckb (gct and ckb are in unnamed module of loader 'app')
	at fxy.a(SourceFile:1068)
	at adm.a(SourceFile:41)
	at adm.a(SourceFile:13)
	at zz.a(SourceFile:25)
	at bpm.d(SourceFile:162)
	at bpq.d(SourceFile:23)
	at bpm.A(SourceFile:136)
	at bpm.bA(SourceFile:121)
	at ffh.c(SourceFile:1275)
	at ffh.f(SourceFile:888)
	at net.minecraft.client.main.Main.main(SourceFile:265)

[kennytv]

That's ClientPacketListener handleEntityEvent, Player can't be cast to Guardian

[yannicklamprecht]

That's ClientPacketListener handleEntityEvent, Player can't be cast to Guardian

Found the reason why. I basically moved away from the entity, the chunk or at least the entities got unloaded.
Due to the state that the disguise data is not persisted on the entity, when loading the entity again it published itself to the client without the disguise info. The client knows the entity uuid only as the disguised type but gets the original one.

I updated the test plugin snippet to reflect the needed change - cache cleaning on death excluded.

It would be way better to persist the disguise data in NBT to avoid manual caching per plugin.