Need Help with Server Input translator

[II./JG1_Kadin]

I have two issues that I need help with.

First, I have placed  several "Server Input Translators" in my missions awhile back and they used to function properly.  I have not used IL2 for a few years and as I have reinstalled IL2, the Server Input translators do not seem to work.  Has something changed over the updates?

The Missions have been resaved and are fully functional in Mission Editor otherwise.

 

Second, the RConClient.exe disconnects everytime I send a Server Input command and I need to browse to my _rconClient.cfg file to reconnect everytime.  When I input the default commands: getplayerlist or getconsole or mystatus, the console stays connects and the server responses.  Is it suppose to happen like that.  

Any feedback would be most welcome.

[JG4_Deciman]

Hi

 

As I use 'serverinputs' for testing very intensive

here is my guess:

 

You have some 'type mismatches' when you enter the command in the console

You use 'special' characters within the names of the serverinput inside the mission.

 

Whenever i had a type mismatch (not meaning the name of the serverinput inside the mission), but a general mismatch

my console also disconnects.

 

Not tried 'special' characters for naming the serverinputs inside the mission yet.

 

And as far as I can tell:

even having a lot of serverinputs inside the mission (all with exactly the same name)

whenever I send the command, ALL of them are triggered and executed without a disconnect

 

Deci

[II./JG1_Kadin]

Thank you Deciman

I understand what you say. It puzzles me since they have been working in the past that I have actually written the usage directions in the mission briefs.

I will try to run some tests on the mission intergrity.  If any solution arises,  I will report back.

[JG4_Deciman]

1 minute ago, II./JG1_Kadin said:

Thank you Deciman

I understand what you say. It puzzles me since they have been working in the past that I have actually written the usage directions in the mission briefs.

I will try to run some tests on the mission intergrity.  If any solution arises,  I will report back.

You can send me the mission and I'll have a closer look...

 

Deci

4 minutes ago, II./JG1_Kadin said:

I have actually written the usage directions in the mission briefs.

 

Does that mean the 'players' are able to send server commands?

So they do know how to connect and there are multiple connections from different consoles possible at the same time?

 

Deci

[II./JG1_Kadin]

If they know how to use the console, the IP is posted along with the pertaining commands no pass or logging name required at the time.  I will appreciate it very much if you give one of my missions a test.   Let me put a zip together.

[II./JG1_Kadin]

Px-BFM-ACM_KDN.zip I have attached a smaller training version.  Everything inside the mission editor are grouped per their function.  The mission brief has certain references that are older and probably not accurate.  (website ref e.t.c)

Let me know if you need anything else.

Thank you

[II./JG1_Kadin]

Here is a simpler mission that I got from Coconut that I also have same trouble.  The Server Input commands are GerIn, GerOut, RusIn, RusOut but you double check them in the editor.  I resaved coconuts mission yesterday because it was from 2015.

coconut.zip

[Cynic_Al]

11 hours ago, II./JG1_Kadin said:

the RConClient.exe disconnects everytime I send a Server Input command and I need to browse to my _rconClient.cfg file to reconnect everytime. 

 

I cannot replicate this problem.

 

 serverinput inputname

 

does not cause the console to disconnect.

 

You can automate specifying a cfg when starting  the console for your server(s):

 

 Make a copy of _rconClient.cfg, say myserver.cfg

 

 Create a desktop shortcut specifying myserver.cfg at the end of the Target parameter (outside the quotes). 

 

 You can also make a shortcut for DServer.exe itself that specifies an SDS file. You need to specify a relative path in the filename, something like

 

..\..\data\myserver.sds

 

Makes things a lot easier.

[JG4_Deciman]

The only way to force my console to a disconnect was

enter a wrong command...

serverinput (no name entered)
serverinputNAME (space missing)

serverinp*t NAME (type mismatch in serverinput)

 

I've also tested with 2 consoles connected.

Only the one with the 'wrong' command disconnected, the other one stays connected

 

Deci

[II./JG1_Kadin]

Thank you both Cynic_AI and Deciman.  It seems that the problem is on me which is good.  I am doing some stupid somewhere, am sure

 

I really appreciate your time guys.

...minutes later...

So stupid of me.  I was not using it correctly.  I was NOT putting the "serverinput" word infront of the command.  I feel embarrased and sorry for wasting everybodies time.

I am guessing after all these years out of IL2, certain synapses stop connecting.

My sincere apologies and again THAAAANK you both!

Edited 11 hours ago by II./JG1_Kadin

[JG4_Deciman]

37 minutes ago, II./JG1_Kadin said:

So stupid of me.  I was not using it correctly.  I was NOT putting the "serverinput" word infront of the command.  I feel embarrased and sorry for wasting everybodies time.

 

Mistakes do just exist for beeing made...

Fortunately this one was easy to locate *g*

 

You're welcome

 

Deci