Author Topic: Triggering plant errors in script  (Read 818 times)

How do I get a brick plant error to display to a specific client?

Before you ask, I did trace. I found two things: clientCmdServerMessage(22 MsgPlantError_Float) and handlePlantError(same argument)
I tried handlePlantError("22 MsgPlantError_Float") first. It did the right thing, but it sent the plant error to all of the connected clients. I then tried clientCmdServerMessage("22 MsgPlantError_Float") and then commandToClient(%client,"ServerMessage","22 MsgPlantError_Float"), neither did anything that I could see.

Could someone that actually knows about this tell me what to do?

Did you do a trace from the server or the client?
This is important.

ninja: also, all clientcmds have to be surrounded in single quotes ('), not double quotes (").

Did you do a trace from the server or the client?
This is important.

ninja: also, all clientcmds have to be surrounded in single quotes ('), not double quotes (").
Pretty sure it was a trace from the server, I was the host. I will also be using this for a server mod

Pretty sure it was a trace from the server, I was the host. I will also be using this for a server mod
Allright, try doing the trace from the client and tell me the results.

Allright, try doing the trace from the client and tell me the results.
I cannot, on my mobile right now

I cannot, on my mobile right now
Well then do it when you get on your desktop or laptop or bedtop or whatever your blockland computer is ._.

Try this:
commandToClient(%client,'ServerMessage','MsgPlantError_Float');

Try this:
messageClient( %client, 'MsgPlantError_Float' );

Try this:
commandToClient(%client,'ServerMessage','MsgPlantError_Float');
Try this:
messageClient( %client, 'MsgPlantError_Float' );
Both work fine
I feel like Greek's is better because the server does the actual error stuff, while port's just sends the message without handling.

I feel like Greek's is better because the server does the actual error stuff, while port's just sends the message without handling.

messageClient( arg0, arg1, ..., argN ) is just an alias for commandToClient( arg0, 'ServerMessage', arg1, ..., argN ) anyway.

Yes, our methods are one and the same.

Yes, our methods are one and the same.
Well ok then, case closed