Hide FLShell commands in the chat, but commands Should work

Welcome Vector9,

Unfortunately, as far as I know, there are many conflicts between FLShell and FLHook, which is why the FLShell commands aren’t being processed correctly. To be honest, in my opinion, I think it’d be best to simply toss FLShell - short of the /restart command, most FLHook implementations have everything FLShell has.

I wish I could help further, however FLShell is unfortunately not open-source like FLHook is, so there’s not much chance of resolving the issues between the two hooking modules.

There’s a /restart plugin available for the FLHook Plugin version.

@Vector9:

Compatibility problem :

My Test Server run FLShell and FlHook

The problem consists in Shell commands pass in a chat

At use Shell command, the command visible in a chat

How to make that commands of a shell did not visible in a chat , but worked?

P.S. Sorry my english is bad.

Write to console.

We run FlShell + FlHook together since a while

• with minor problems.
  To keep the problems with FlShell low
  i d just stay away from it’s “/land” and “/beam” command.
  

Besides the restart there are some minor FlShell things,
which are nice 2 have:

• the “/list” command, showing who is online with what ship
• the “/cargo” command
• the possibility to set a reward 4 player kills, taken from victims account.

I also like the possibility to restrict the usage
by ship type and reputation on the user side
and as well on the target side.

And i think that’s the solution here:
@HeIIoween:

Write to console.

Shell and hook work pretty fine together, unless you enable disconnect delay in hook - it really messes things up with commands that kick player (like rename). My server is running both shell and hook for about a year now with no big problems except that.

This issue with shell command is shown into system chat do exsists however.
You can avoid this some ways:
1. Write shell commands into console chat channel You can even disable command-catching for system chat in shell.
2. Get rid of HkSendChat (or smthing) hook. You’ll lose ignores and chatstyles with this.
3. You can block all lines beginning with ‘/’ in HkSendChat. You can’t block those lines in HkSubmitChat 'cause then shell won’t see any command at all.

To keep the problems with FlShell low
i d just stay away from it’s “/land” and “/beam” command.

yea, there’s this bug that crashes server after ForceLand. I use shell’s /jump command instead, which kicks you to move your ship, but it won’t crash server and also it can move you to point in space, not only to base.

The best chance for ‘safe beaming’ gives the
last FlHook version of Motah with the option
“kick after beaming” imho.

FLHook plugin has a configuration option to suppress all chat lines starting with different characters, e.g. ‘/’
See the flhook.ini file for details.

We use the .beam command with this version and it works correctly. Haven’t had any problems.

The player control plugin for flhook-plugin has a /move command that moves you to any location in a system. It doesn’t kick you. Again haven’t had any problems with this. This plugin also has a /pos to get your current position and a /chase command to move you to the location of another ship.

@Cannon:

FLHook plugin has a configuration option to suppress all chat lines starting with different characters, e.g. ‘/’
See the flhook.ini file for details.

I don’t know about the plugin, but in flhook 1.5.5 this is done in HkSubmitChat, thus not passing commands to the shell.

Don’t get me wrong

• i just tried 2 tell, i prefer FLHook instead of FLShell for beaming.

No offence against any of those FlHook versions around.