Mission Editor in WINE - Revision history

Histidine at 15:24, 25 June 2016

2016-06-25T15:24:12Z

Histidine at 15:03, 25 June 2016

2016-06-25T15:03:51Z

Histidine: /* Details */ fix download link

2016-06-25T15:03:28Z

Details: fix download link

HistidineBot: Ported from ZK wiki by DotNetWikiBot

2016-06-25T15:01:54Z

Ported from ZK wiki by DotNetWikiBot

HistidineBot: Ported from ZK wiki by DotNetWikiBot

2016-06-25T14:32:52Z

Ported from ZK wiki by DotNetWikiBot

New page

= Introduction =
This page is about making missions on linux. It will document the installation of and problems with the mission editor in WINE. This guide assumes knowledge of WINE, should you not understand something it will be well documented elsewhere on the internet.

= Details =
First create a new wineprefix. This is to ensure that there are no other applications complicating matters.

In order to install the Mission editor you must first install .net 4.0. To do this, run: (replace "(wineprefix)" with the filepath to your wineprefix)
{{{
WINEPREFIX=(wineprefix) winetricks dotnet40
}}}
Download the mission editor executable from https://code.google.com/p/zero-k/downloads/detail?name=MissionEditor.exe. From a terminal at the location of the downloaded file, run: (replacing "(wineprefix)" again)
{{{
WINEPREFIX=(wineprefix) wine MissionEditor.exe
}}}
You will likely have to give the executable permission to run as a program.

You now have the mission editor installed. Run the executable you downloaded with the above command whenever you want to run it.

= Bugs =
There are a few bugs with this:
* You must run this program WITHOUT a virtual desktop. If run in a virtual desktop you will have to reboot every time you wish to open the mission editor.
* When you press the button to publish your mission the mission editor will crash.

If you notice any bugs please report them to TheSponge via lobby PM. Happy mission editing!

@@ Line 1: / Line 1: @@
-= Introduction =
+== Introduction ==
 This page is about making missions on Linux. It will document the installation of and problems with the mission editor in WINE. This guide assumes knowledge of WINE, should you not understand something it will be well documented elsewhere on the internet.
-= Details =
+== Details ==
 First create a new wineprefix. This is to ensure that there are no other applications complicating matters.
 In order to install the Mission editor you must first install .net 4.0. To do this, run: (replace "(wineprefix)" with the filepath to your wineprefix)
 <code>
 WINEPREFIX=(wineprefix) winetricks dotnet40
 </code>
 Download the mission editor executable [http://zero-k.info/missioneditor/setup.exe here]. From a terminal at the location of the downloaded file, run: (replacing "(wineprefix)" again)
 <code>
 WINEPREFIX=(wineprefix) wine MissionEditor.exe
 </code>
 You will likely have to give the executable permission to run as a program.
 You now have the mission editor installed. Run the executable you downloaded with the above command whenever you want to run it.
-= Bugs =
+== Bugs ==
 There are a few bugs with this:
 * You must run this program WITHOUT a virtual desktop. If run in a virtual desktop you will have to reboot every time you wish to open the mission editor.