[1.7.10] Disguise player as Entity/Block

[clienthax]

How would i go about disguising the player as a Entity/Block on the server side

[SilentThief]

Have you written any code yet?

[clienthax]

Have you written any code yet?

I'm not sure why that matters, if you are asking if I know how to make mods etc the answer would be yes.

[jabelar]

No, he means have you written any code yet to try to accomplish this: disguise the player as an entity as a block.

 

People aren't inclined to help if you haven't already tried.  Why are you asking us?  How do you think you'd disguise the player? 

 

At least tell people what you've tried, or tell them what you think might work, otherwise your question sounds like "write my mod for me".  It's not just about being lazy, you really need to struggle through the thought process yourself if you want to really get good at modding.

 

So, here are some questions to figure out for yourself:

- what code controls how the player looks?

- how do you think you can intercept that code to modify it?

[clienthax]

I figured the basic idea would be to cancel the player location packet then make a entity on the server and set the location / yaw to match the players ?

[TLHPoE]

That's a bit too extreme for what you're trying to accomplish.

 

Just cancel the RenderPlayerEvent and then do your own rendering.

[clienthax]

That's a bit too extreme for what you're trying to accomplish.

 

Just cancel the RenderPlayerEvent and then do your own rendering.

 

This mod is going to be server side only.

[TLHPoE]

Oh, didn't see that part.

 

You could give invisibility to the player and then spawn the entity/set the block at the player's location.

[clienthax]

Oh, didn't see that part.

 

You could give invisibility to the player and then spawn the entity/set the block at the player's location.

 

Mhm il give that a go, i think ima make a instance of the entity and store it instead of making it each tick however.

[jabelar]

I don't think it can be server side only, or at least it would be extremely difficult.  The client is aware of the player, and is also does all the rendering (i.e. the "disguise" part).  Even if you made a new entity, the client would have to have the mod for that entity.

 

Anything that requires displaying something different would need client-side.

[delpi]

Create extendedProperties for your players.

 

When disquised, keep track of it in the extendedProperties.  Whenver a change of disquise occurs, sync with all the clients via packets.  I would recommend doing this also on some time frequency just in case.  Once a second won't hurt, if you are efficient this won't even be noticable network traffic compared to minecraft itself.

 

On the clients, have setup the render event and when it occurs for a player that has a disquise, cancel the render and utilize your disquise render instead.

 

This isn't that hard to map out based upon other discussions you can search for.  As Jabelar said, get out and try something first. 

[clienthax]

Create extendedProperties for your players.

 

When disquised, keep track of it in the extendedProperties.  Whenver a change of disquise occurs, sync with all the clients via packets.  I would recommend doing this also on some time frequency just in case.  Once a second won't hurt, if you are efficient this won't even be noticable network traffic compared to minecraft itself.

 

On the clients, have setup the render event and when it occurs for a player that has a disquise, cancel the render and utilize your disquise render instead.

 

This isn't that hard to map out based upon other discussions you can search for.  As Jabelar said, get out and try something first.

Server only mod, ive mostly worked it out now, i just need to figure out how to stop the entity from trying to walk off.

[WorldsEnder]

You could make this mod server only mod but you have to keep track of the following (at least):

 

The player changes to a disguise (some packet the disguising player sends):

-> Server has to send a LogoffEvent? to all other players and not display the player on the serverlist anymore (so that the disguise is good) or despawn the EntityPlayer in the world. I can't tell you if it will be respawned but the disguised player should not be sent these Events

-> Server has to spawn a new Entity in the world (the disguise) and keep it in synch with the actual player movement. If it is a block the server has to prevent movement.

 

Player changes disguise: Pretty much the same as changing to a disguise

 

Player changes to normal: Reverse the process

 

With this implementation the server could be fully aware of the player without changing it's state internally but all sent updates have to be modified which can be extremely difficult to catch all of them (especially when other mods interfere). Also the player wouldn't know about his own state because HIS client never received any updates. How could he, he doesn't support a player being a block.

 

To sum this all up: The mod should be clientside, too.

[clienthax]

You could make this mod server only mod but you have to keep track of the following (at least):

 

The player changes to a disguise (some packet the disguising player sends):

-> Server has to send a LogoffEvent? to all other players and not display the player on the serverlist anymore (so that the disguise is good) or despawn the EntityPlayer in the world. I can't tell you if it will be respawned but the disguised player should not be sent these Events

-> Server has to spawn a new Entity in the world (the disguise) and keep it in synch with the actual player movement. If it is a block the server has to prevent movement.

 

Player changes disguise: Pretty much the same as changing to a disguise

 

Player changes to normal: Reverse the process

 

With this implementation the server could be fully aware of the player without changing it's state internally but all sent updates have to be modified which can be extremely difficult to catch all of them (especially when other mods interfere). Also the player wouldn't know about his own state because HIS client never received any updates. How could he, he doesn't support a player being a block.

 

To sum this all up: The mod should be clientside, too.

 

easy way,

set player to invisible, spawn in mob on server side, in world tick update the entity with players info.

[jabelar]

I really don't understand how that could be a server-side only mod.  If you have a custom entity that the client can see (in disguise) at some point a client has to render it and furthermore won't there be trouble when the server tries to send packets about the entity to the client (which it normally does for all entities) if the client doesn't have the same custom entity class?.  Any custom entity created on server would need to be rendered on the client.  Or maybe I don't understand what you're saying you're doing -- right now it sounds like you're placing a custom entity that is rendered with a disguise.

 

Or are you placing an actual block on the server from an invisible entity?

[HuskyBlueFire]

 

easy way,

set player to invisible, spawn in mob on server side, in world tick update the entity with players info.

 

Would this not limit you to already existing mobs within Vanilla (or any modpacks the clients on your server have in common)?

[delpi]

I've done it with Bukkit before as server only, but like you said its only for vanilla things. 

 

If you are using forge, why not unlock the potential and have a client side as well?