Profanitizer

The reason i got that error is something to do with me editing the mission file by trying to change default parameters, but i figured out that server config file can be edited to force mission parameters. Sadly, it seems that this tool overwrites what you've editied in the server.cfg file no matter what, so i guess I'm going to have to stick with the "leave as is" option on the TADST tool instead. Maybe in the future you should add a feature to either edit parameters, or stop them from overwriting cfg files?

That solved the issue, thanks, but now a new issue has appeared lol! When i try and launch the server, with the mission file named "Antistasi.Altis"(.pbo), the server window shows an error stating "Can't find a mission collection / mission with template name: 'Antistasi.Altis', skipping to next mission." I looked online for solutions, but most said to rename the mission file to have ".Altis" at the end and that didn't work. Here is what the config file contains: ...; class Missions { class Mission_1 { template = "Antistasi.Altis"; difficulty = "Recruit"; }; }; Is it something to do with the class name "Mission_1"? Or have I incorrectly placed the mission file? "Antistasi.Altis.pbo" was copied over from where the Antistasi mission is kept after downloading on the workshop, and was renamed as it was originally just "mission.pbo".

I'm having a real problem getting my server to launch. Every time i attempt to launch it I get this error: System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at FAST.NewServerTab.LaunchServer() at FAST.NewServerTab.LaunchServer_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Usually I can pick out a key word for what is causing the problem, but this just looks like gibberish to me. Anyone got any ideas?