Metroid Construction

1. Download and Extract Editroid
2. creating separate wine prefixes is ideal. create an editroid wine prefix: WINEPREFIX=~/.wine_editroid winecfg
3. save this shell script next to Editroid.exe:

run_editroid.sh

#!/bin/bash
WINEPREFIX=~/.wine_editroid ./Editroid.exe

give the script execution permissions so you can just double-click/hit enter to run it:
chmod +x run_editroid.sh

from now on, use the shell script to launch Editroid, because this will use the correct Editroid wine prefix. If you try to run the EXE directly, it will use the default wine prefix, which is a no-no.

Download and Extract LAMP. for best results grab LAMP 32-bit (x86), since 64-bit wine is still experimental
Next, either use the helper script, or follow the steps below

wine_lamp_helper.sh

#!/bin/bash
BITS=64
WINEPREFIX=~/.wine_lamp
 
export WINEPREFIX
# create wine prefix if it doesn't exist
if [ ! -e "$WINEPREFIX" ]; then
    wine hostname
fi
cd $WINEPREFIX
 
if [ "$BITS" = "64" ]; then
    export WINEARCH=win64
 
    # download LAMP and the .NET 6 runtime if we don't have them already
    if [ ! -f "$WINEPREFIX/LAMP.64bit.exe" ]; then
        wget https://builds.dotnet.microsoft.com/dotnet/WindowsDesktop/6.0.36/windowsdesktop-runtime-6.0.36-win-x64.exe
        wine windowsdesktop-runtime-6.0.36-win-x64.exe
        wget https://github.com/LAMP-Platform/LAMP/releases/download/Beta/LAMP.64bit.exe
    fi
 
    # launch LAMP
    wine LAMP.64bit.exe $@
else
    # download LAMP and the .NET 6 runtime if we don't have them already
    if [ ! -f "$WINEPREFIX/LAMP.32bit.exe" ]; then
        wget https://builds.dotnet.microsoft.com/dotnet/WindowsDesktop/6.0.36/windowsdesktop-runtime-6.0.36-win-x86.exe
        wine windowsdesktop-runtime-6.0.36-win-x86.exe
        wget https://github.com/LAMP-Platform/LAMP/releases/download/Beta/LAMP.32bit.exe
    fi
 
    # launch LAMP
    wine LAMP.32bit.exe $@
fi

copy the required commands and then paste them into your terminal with ctrl + shift + V.

1. creating separate wine prefixes is ideal. create a wine prefix for LAMP: WINEPREFIX=~/.wine_lamp winecfg
2. install .NET 6.0 Desktop Runtime with your LAMP wine prefix: WINEPREFIX=~/.wine_lamp winetricks dotnetdesktop6
3. save this shell script next to LAMP.32bit.exe:

run_lamp.sh

#!/bin/bash
WINEPREFIX=~/.wine_lamp ./LAMP.32bit.exe

give the script execution permissions so you can just double-click/hit enter to run it:
chmod +x run_lamp.sh

from now on, use the shell script to launch LAMP, because this will use the correct LAMP wine prefix. If you try to run the EXE directly, it will use the default wine prefix, which is a no-no

1. 64-bit LAMP
2. WINEARCH=win64 WINEPREFIX=~/.wine64_lamp winecfg
3. WINEARCH=win64 WINEPREFIX=~/.wine64_lamp winetricks dotnetdesktop6

4. run_lamp64.sh

   #!/bin/bash
   WINEARCH=win64 WINEPREFIX=~/.wine64_lamp ./LAMP.64bit.exe

okay i'm gonna need some real deal hackers to stress test this but i'll whip together what i've done to reach this point.

Download SMART.
(optional) SMILE RF
(optional) ASAR

1. extract SMART: bsdtar -x -v -f SMART.1.19.9228.42504.zip
2. creating separate wine prefixes is ideal. Create a SMART wineprefix: WINEPREFIX=~/.wine_smart winecfg
3. SMART uses some iteration of .NET 4. Install .NET 4.8 runtime to your SMART wine prefix: WINEPREFIX=~/.wine_smart winetricks dotnet48
4. (Optional) install VB6 to your SMART wineprefix for smile RF support. WINEPREFIX=~/.wine_smart winetricks vb6run
5. using a text editor, create a shell script (*.sh) to launch SMART. save it in the same directory as SMART.

run_smart.sh

#!/bin/bash
WINEPREFIX=~/.wine_smart ./SMART.exe

give the shell script execution permissions so you can just double-click/hit enter to run it:
chmod +x run_smart.sh

from now on, use the shell script to launch SMART, because this will use the correct SMART wine prefix. If you try to run the EXE directly, it will use the default wine prefix, which is a no-no

1. Download and Extract MAGE Themes.
2. creating separate wine prefixes is ideal. mage themes is 64-bit. make a 64 bit wineprefix: WINEARCH=win64 WINEPREFIX=~/.wine64_mage winecfg
3. install .net 6 runtime stuff: WINEARCH=win64 WINEPREFIX=~/.wine64_mage winetricks dotnetdesktop6
4. obtain the microsoft sans serif font micross.ttf, extract, and put it in your 64 bit wineprefix's fonts folder (drive_c/windows/fonts)
5. create a shell script that sets the proper wineprefix and 64-bit for launching mage:

run_mage.sh

#!/bin/bash
WINEARCH=win64 WINEPREFIX=~/.wine64_mage ./mage.exe

give the shell script execution permissions so you can just double-click/hit enter to run it:
chmod +x run_mage.sh

from now on, use the shell script to launch MAGE, because this will use the correct MAGE wine prefix. If you try to run the EXE directly, it will use the default wine prefix, which is a no-no