Mordhau
 Vesanus — Level Design
Level Design
  • Likes received 555
  • Date joined 26 Oct '15
  • Last seen 22 Sep '20

Private Message

Knight 685 1855
  • 4
  • 28 May '19
 ÐMontyleGueux

The Lutebot 2.0 Thread

This is it guys. The lutebot in a new and shiny version. What was originally a little project for a handful of alpha roleplayers has been heavily reworked to match the incredible release mordhau and its community just went through. I hope to be able to update and support it to bring the best out of mordhau's lute (and possible future instruments) for years to come using this new solid codebase and set of features.

See this new thread as a rework as well. Please read carefully through the guides below, they have been written by painstackingly collecting feedback from the new release users.

Join the bards guild discord server here to get troubbleshooting help, midis and more !

Check out this live midi input showcase, one of the novelties brought by the 2.0 :

Index

About

What's the lutebot ?

The lutebot is a third party software that can read midi files (.mid) and mimic their content to the best of its ability using the lute in game. It uses console commands to communicate with the game.

Is it safe ?

The lutebot is born from a cooperation with the devs. They created the console commands for the lute specifically for this usage and fully endorse it. Furthermore, the code is entirely public on github (check the download section).

I have heard from moderators that some people have been trying to blame the lutebot after getting banned for third party software usage (actual cheats). Rest assured that the lutebot won't get you banned.

How does it works ?

The lutebot is built on the C# midi library by sanford that you can get here. This library plays midi files for the lutebot, which then intercept midi events when thrown by the library and turn them into console commands.

The lutebot's interface is made using winform, a somewhat outdated yet time saving tool for simple window interfaces.

If you like the lutebot and wish to support it, you can help me by donating to my patreon
Reworking the lutebot and adding live midi input was only the beginning, I have more features planned for the future (more on that on my patreon page !). But this is a time consuming project, your support will let me put more time into it.

Download

You can get the latest lutebot version here

Or get access to the code directly on GitHub

Older versions :

Getting Started

Installation

Download and unzip the lutebot folder. As long as its content is intact, it will work regardless of where you put it.

Quick Setup

Start the lutebot by double clicking on LuteBot.exe. Click on options then on keybinding to open the keybinding menu.
From here, check the message displayed below the list of keybinds. It should look like this :

Capture.PNG

If it does, please Ignore the following section.

If this is not the message you're seeing, you need to manually set the path to mordhau's configuration file. Please do so by clicking on Mordhau Config then Mordhau Configuration Files then Set DefaultInput.ini Location. Then, select the file named DefaultInput.ini in your game folder. Its default location is :
C:\Program Files (x86)\Steam\steamapps\common\Mordhau\Mordhau\Config\DefaultInput.ini
If you selected the right file, the message below should look like the picture above.

Now that the lutebot knows where your mordhau settings are located, you may use the automatic configuration that will set the console both in game and in the lutebot to PageDown for you.
To do so, please click on Mordhau Config then on Automatic Configuration then on Set up.

Then press Apply to close the keybind window.

The lutebot's OpenConsole keybind should be set to Next, and the next time the game starts, pressing PageDown should open the console. Take a moment to check if this is your case.

How to operate

To play a midi file (.mid) on the lutebot, click on Load Midi File in the main window and select a file. If you selected a proper midi file, it's title should appear one the window, and the buttons Stop and Play Should be now accessible. Click on the play button and you should start hearing music.

To play this midi file using the in game lute, go in settings and turn off sound effects here :

Capture1 - Copie.PNG

Then go in game, have a lute equipped in your hands, and press + on the numpad (the default shortcut to play) to start playing.

Warnings :

  • Do not use the play button to play in game, always use the shortcut.
  • Do not attempt to open the console yourself, let the lutebot manage the console.
  • Do not try to jump or crouch while playing.
The lutebot should now be ready to operate. Consult the detailed guide for more, or the troubleshooting section if you're still encountering issues.

Detailed Guide

Main Window

Capture8.PNG

This is the main window of the lutebot that will always show while it is running. It is designed to look like a regular music player, displaying the elapsed and total time in the current song, a scrollbar that you can move around, a play/pause button and a stop button.

Clicking on the central button will let you manually load one midi file into the player.

The previous and next buttons will let you navigate in the playlist. They are only accessible if a playlist is currently active and it contains at least two tracks.

The Options button in the top left corner will let you access the settings and the keybind menu. The Window button next to it let you use the optional features of the lutebot described below. The focus button in the window menu will put all of the lutebot's windows back to the foreground, useful when having multiple windows open. Alternatively, clicking on the main window does the same.

Configuring the LuteBot

Settings

Capture1.PNG

The following settings affect which parts of the lutebot's interface will be open when starting the lutebot :
  • Show Playlist Menu on Startup
  • Show Soundboard Menu on Startup
  • Show Track Selection Menu on Startup
  • Show Online Sync Menu on Startup (unfinished)
  • Show Live Midi Input Menu on Startup

Sound effects : lets you switch between playing in game or playing using midi sounds (useful to try different instruments and tracks settings beforehand).

Automatic Console System : lets you change the way the lutebot interacts with the console.

  • Old : The big console will open once when you start playing, and close when you pause. This console mode prevents you from moving entirely when playing, and is slower (meaning that the note cooldown needs to be set much higher for it to work, 50 is recommended for this setting)
  • New : Opens the small console for each command. The small console closes automatically upon inputting one command, which allows the lutebot to input commands at a much faster rate. This is the recommended setting. Warning this setting won't work if the console key you're using for the lutebot can input characters (like Tilde). PageDown is recommended for this setting.
  • Off : the lutebot will not try to interact with the console at all. You have to manually open the big console before pressing play. Just like the old setting, it is slow and require a high note cooldown.

Note Conversion Mode : Turns on and off the note transposition feature. Due to the lute's limitations in game, the lutebot has a transposition system applied to notes outside of the lute's range. Turning it off and enabling sound effects lets you use the lutebot as a regular midi player. Useful to listen to original tracks before attempting tweaks.

Lowest Note ID : The lowest note id mordhau's lute supports. This setting should not be modified, please keep it to 0 at all times.

Note Count : The number of notes mordhau's lute supports. If mordhau's lute gets updated and receive more notes, you can set this setting so that the lutebot will take these changes into account.

Note Cooldown : This setting changes the cooldown in ms applied after a note has been played. 50 is recommended when using old or off console modes, while 30 or lower is recommended for the new console system.

You can check for updates in the bottom right corner of the settings window.

Keybinds

To change one of the lutebot's keyboard shortcuts, simply click on one of the keybind list's items and press the desired key to set the shortcut.
Do not forget to apply or your change won't be saved.

Here is a detail of all the keybinds and their functionnalities :

  • Play : Start/pause the current song.
    Next : Load the next song in the current playlist.Previous : Load the previous song in the current playlist.
    Ready : Currently unused (related to online sync).OpenConsole : Is used by the lutebot to open the console for you.
    *LiveMidiListen : Toggle listening to your selected midi input device.

As explained in the Getting Started section, the keybind menu is also capable of setting your console key properly for you. Please refer to this section for more details.

Features

Each of the main features have their own window, so that you can customize the lutebot's interface to your liking.

Playlist

Capture2.PNG

The playlist window lets you create a list of midi files that will be played one after the other. You can also skip to the previous or next song in the playlist using the buttons on the main window, or use the convenient keyboard shortcuts (/ and * on the numpad by default) to go from one song to the other without even leaving the game.

You can use the Add to Playlist button to add a midi file to the playlist.

You may also save the playlist as an xml file for later use using the Save Playlist button, and load a previously saved playlist using the Load Playlist button. Note that when you open the playlist window, it will automatically open the last playlist you saved.

Warning: Do not attempt to load a soundboard xml file as a playlist.

Soundboard

Capture3.PNG

The soundboard lets you create up to 9 song shortcut. Pressing the associated key will instantly start playing the associated song. Consider using this feature to avoid alt-tabbing to switch between songs. To modify a shortcut's keybind or song, simply right click on one of the 9 buttons.

Just like the playlist, the soundboard can be saved as an xml file, and loaded later. Opening the soundboard window will automatically load the last soundboard you saved.

Track Filtering

Capture5.PNG

The track filtering window lets you remove some complexity out of a midi file to make it sound better on the lute. Some midi files may contain a lot of instruments playing at the same time, which is undesired for mordhau's lute limitations.

You can tweak the content of a midi file simply by ticking boxes off to remove either instruments, or tracks. Tracks are a series of commands in midi files that may or may not contain notes, removing some might not have any effects depending on how the current midi was made.

When you think the tweak you applied suits your needs, simply press Save Song Profile to save your changes. As opposed to the soundboard and the playlist, you cannot choose where you save song profiles. They will be automatically stored in a folder and retrieved if they exists when a song is loaded (manually or using a playlist or soundboard).

Live Midi Input

Capture7.PNG

The live midi input window is the most important feature of this new version. It allows you to take full control of the lute using either a midi input device plugged to your computer, or your keyboard directly.

Check the drop down menu to see the list of available devices. Keyboard Mode will always show up in the list on top, any midi input device directly plugged into your computer will show under it.

Once you selected the device you wish to use, click on the listening button. Your inputs will only be taken into consideration when this button is green. You may also use the . (or del) key on your numpad to toggle it while in game.

Selecting Keyboard mode will allow you to simulate a midi input device using your computer keyboard. You can bind individual notes to each of the piano keys below by clicking on one then pressing the desired key. Pressing those keybinds while in the game and with listening enabled will play the corresponding notes.

You may use the - 1 Octave and +1 Octave buttons to change the note range the lutebot is focusing on. Pressing a key on your midi device that plays a note outside of the displayed range will automatically transpose that note to the range. Alternatively, checking the box below will causes notes outside of this range to be simply ignored.

Troubleshooting

Before reading this section, please read carefully through the quick start up guide first. Make sure you're operating the lutebot properly.

The lutebot immediately spam the chat and open the team selection menu when I press play

This typically happens when your console key isn't set properly. Check that the lutebot's OpenConsole bind in the keybinding menu is properly set to the key you use to open the console in game. To rebind the console key in game, please check the quick start up guide. Alternatively, you can consult the official discord (by typing !c console in any channel of the official discord) to know how to bind it manually.

Command not recognised appears in the console when playing

This can happen for multiple reasons, please refer to the two sections below for more information.

A character appears before every command, causing the command not recognised error

This happens because the key you have set your console to can input characters (like tilde writing ~). You need to use a key that cannot input characters, like PageDown.

The i is missing, equpmencommand is being written in the console, causing the command not recognised error

Check the keyboard windows is currently set to. Make sure it is set to qwerty (EN should appear on the taskbar), or azerty (FRA on the taskbar).
Any other keyboard type is officially untested thus support cannot be guaranteed.

The lutebot start spamming the chat and opening the team selection menu in the middle of a song

This can happen for various reasons. Make sure that you don't jump, crouch or sprint while playing the lutebot.

If this happens with the big console (console mode off or old) then you need to set the note cooldown higher than it is. 50 ms is recommended.

Midi Files

I will post here the various midi files that people have edited to work with the lutebot.

Thanks to @Fohshizle for his work, you can get his midi files (here)[https://drive.google.com/file/d/1RUTe3ZMlpDY8QTNVTorZbKCa4oSqHh88/view?usp=sharing]

Also try FloridaMan's Collection

Special Thanks

Marox :

For making the lutebot possible in the first place.

Milosh_Obilic :

For putting together the tutorial videos as well as the various showcases. Stay tuned for his modding work once the sdk drops!

My testers, JasonBourne, PlouPlou, Iodine, Madcow :

For helping me figure out what I lacked in music knowledge, and reporting various bugs since the first version.

Knight 1837 2232
  • 19 Jul '19
 Void

SDK may not be out yet but people found a way to make community maps.
Here is the first community map made by Plouplou of the Berserkers clan. Watch the vid and read the description for info.

168 1700
  • 2
  • 6 May '19
 elwebbaro — Art

It's been one hell of a ride thus far, and it's only been 7 days. None of us would've expected this reception in our wildest dreams.
As of today MORDHAU has sold just shy of 500.000 copies and we have reached a peak of 60.000 concurrent players yesterday. These are just mindblowing numbers to us, and we still haven't fully realized that MORDHAU is currently among the top played games on Steam.

Unfortunately the launch wasn't as smooth as we had hoped. Server performance was abysmal and reward drops such as Gold and XP, as well as unlocks were not functioning properly. We are still in the process of seting up new servers in regions that need them and as a result the Matchmaking can still be spotty. There's also some other Matchmaking related bugs that prevent parties from joining the same game, or BR lobbies to populate very slowly, but we're on top of that. All things considered, the majority of launch issues have been resolved. As for compensation of the lost Gold and XP. We have not forgotten about it and will be shipping it via the next patch.

Right now we are addressing some of the more frequent and critical issues, like the "Ghost Bug" among others, as well as some map exploits. These past few days had been very hectic for us, but things are starting to somewhat get back in order.

Looking ahead for future updates, we've got a couple new maps in mid-production: Castello and Feitoria. Here's a few impressions on the latter.

On top of that we will start looking into Ranked/Competitive modes, starting with duels. However we cannot give an exact timeframe on when you can expect these updates to be rolled out yet. We are terrible when it comes to estimating things, I'm sure our alpha players can attest to that.

Additionally we will keep adding new armor pieces and weapon skins here and there, as well as some new character customization options.
Goals further down the line would be to release Modding Tools, as a lot of you seem to be very eager to create some custom content.

We've got lots of ideas for improvements to the maps and gamemodes. There's also been some amazing feedback and suggestions coming from you guys. When it comes to balancing and tweaking of mechanics, we are pretty happy with how things are looking right now, but we will start tweaking some things soon.

In closing we'll take this opportunity to give some shout-outs.

Thank you

  • to all the Kickstarter backers and alpha testers. Without your constant feedback, suggestions and nitpicking the game would not be where it is now.
  • to G-Portal/zeuz and their amazing support. You guys were super helpful and assisted us a bunch to keep up with our launch woes.
  • to all community server hosts. You really saved our asses to provide servers for all these players while we were struggling to spin up our own.
  • to our promotional launch re-stream: You guys knocked it out of the park and delivered some sweet first impressions right on the storefront.
  • to all the content creators out there creating videos and streaming. MORDHAU spread like a wildfire, which wouldn't have been possible without you.
Duke 5562 13285
  • 29 Apr '19
 Jax — Community Manager

ya yeet

132 1228
  • 1
  • 29 Apr '19
 Maxilatorn — Art

It's sure been a fun ride, big thanks to everyone who made it possible!

988 6974
  • 29 Apr '19
 marox — Project Lead

What a ride! The day of Mordhau's release is finally here. Our target is to go live today April 29th @ 10 AM PDT. We will be launching with a base price of $29.99 (Steam currency/regional pricing applies!) and a 10% launch discount. Besides the base game, for those who really want to go the extra mile to support us, you'll also be able to purchase the Supporter Pack containing the soundtrack, Medallion (necklace) wearable cosmetic and Mercenary banner. Those who wish to purchase the Steam key to the game on our webshop, will be able to do so here when the game is released, and a lot more money from those sales will go to the developers, as Steam won't take their cut.

Anyone who backed the game at $40 or more (Beta level, which contained the Soundtrack) will receive the Supporter Pack as part of their pledge via Steam key on the account you've registered on our website. So please keep this in mind to avoid purchasing the Supporter Pack twice! Please give us an extra couple of days to supply these Supporter Pack keys to you, as we ran into some delays there.

All backers should have received their rewards by now (except the soundtrack). For some of you, we're still waiting/adding the things that require your input (custom emblems, etc.) so make sure to fill out all forms on our website. If you have not yet received a key please do the following before contacting us. Check your emails, most of you that contact us have already activated your purchase back in 2017, but have not checked your forum account for the Steam keys. The keys have been waiting for you there for some time :) If you are sure you haven't received any activation link, and have never activated your purchase on our forum/website, then get in touch with us via a Kickstarter private message, or send an email to [email protected] from the email you used to purchase, and we will sort you out.

If you would like to purchase just the soundtrack (and it's a good one!) directly from the composers, you can do that here.

Thank you so much for supporting us and making this project possible. It's been an absolute blast to work on, and we hope you'll enjoy playing it!

See you on the battlefield!

Baron 19 31
  • 20 Apr '19
 FishBazooka

Cannot wait! I'm excited. Made a new video to get us all hyped! Enjoy :)

Knight 1388 3163
  • 2
  • 18 Apr '19
 Tim_Fragmagnet

The sword at 1:06 goes super spin mode
the one at 1:18 does as well

S H I T G A M E ???? ? ? ? ?? ? ?

thomp.png

Knight 1388 3163
  • 1
  • 20 Mar '19
 Tim_Fragmagnet

Please come back to me

plese.png

Knight 101 371
988 6974
  • 1
  • 12 Mar '19
 marox — Project Lead

Attention all backers!

NOTE: This is a closed test for Kickstarter backers only. Access to the game is otherwise not possible at the moment, but release is coming soon!

As we approach towards having everything ready for release, we need your help to do some stress testing and identifying any show-stopping issues. Starting on March 15th (Friday) at 5 PM CET (Central European Time), until (including) March 17th (Sunday), we will be running organized tests on the pre-release build, where you'll get a taste of what we've been working on.

This time around, we really need to hit high player counts, so we are going to be limiting the servers to guide the testing phase. We will be doing themed tests each day to focus the population, starting with Friday - Frontline on Camp, Saturday - Battle Royale on Grad, and ending with Sunday - Horde on Taiga. Outside of these dates, the new modes will not be available to play. We are doing this to ensure that all those who wish to try them out show up on the days mentioned, ensuring a high peak. During the testing we will have servers in EU, US, AUS and SA.

After the weekend testing period, we will be rolling back the game to the current test build which will remain up until closer to release. Assuming there are no major issues, we will then proceed with our preparations for release and will announce an exact date shortly after. Good times are coming.

(Sneak peak below of the new armory poses :))

HighresScreenshot00121.jpg

Count 331 1394
  • 12 Mar '19
 RingMaster

@marox said:

Horde on Taiga.

zulul.png

Knight 337 778
  • 20 Oct '18
 AngelEyes

:)

IMG_0031.JPG

988 6974
  • 25 Sep '18
 marox — Project Lead

We've set up a shop with Mordhau-branded physical items (no keys, sorry!) that you can buy, featuring some amazing t-shirts designed by our very talented Rattsknecht. Perfect if you want to show off your love for the game, or just want to look cool. We're starting it off with a 10% discount this week -- check out the shop here!

Knight 2608 6921
  • 25 Sep '18
 Rattsknecht

oh cool

Baron 1647 5234
  • 16 Sep '18
 Lincs

Damn Jax, over 14 minutes long? I'll never tease you with devblog wen comments ever again, that thing must have been a bitch and a half to put together and then another to edit. Really good video too!

Duke 5562 13285
  • 1
  • 16 Sep '18
 Jax — Community Manager

Hi everyone! It's been a while, but today we've just released our fourth dev blog, the Road to Release! In this blog we showcase some of the improvements and additions made to MORDHAU in the past few months during closed alpha testing. Speaking of testing, things have taken a little longer than planned and while we've had to push full release to early 2019, we've decided to activate keys for Early Bird and Release-tier Kickstarter backers, as well as Gumroad pre-orders! Check your emails registered with Kickstarter/Gumroad for more information, and enjoy the video!

Please note: currently, we have no plans for further access to closed testing - we ask that you patiently wait for full release in early 2019. Thank you for your understanding. For more information on this, check here

80 286
  • 2
  • 12 Sep '18
 wizardish
  • The problem with this thread and feint threads in the past is the over simplification and misrepresentation of the mechanic. Feints take skill to use. If you don't know what you're doing, you'll end up dying by trying to use them. The disparity between skill to perform and skill to defend certainly exists, I don't think anyone would deny that because it is inherent for feints and will always be as a result of how the mechanic works, but it's not as severe as people commonly make it out to be (like 0-100 or something). It seems I have to again suggest that the game is a multi-variable game, it's not a reaction time simulator. Feint reading doesn't always scale with hours put into the game or your reaction time. I used to tell noobs all the time that I have 300ms reaction time on humanbenchmark and I play on 60hz (now 144hz) to inspire them. The point being that feinting isn't so one dimensional as people make it out to be.

  • This thread focuses on the new player experience from what I've gathered. In that sense, (and knowing matchmaking will exist) why don't we focus on what noob vs noob fights will look like rather than some comp guy deleting some new player? In CS it certainly doesn't feel good when someone much better than you peeks a corner and insta one taps you. Noob vs noob situations look a lot different - usually both noobs spraying at each other and missing a significant amount of shots before one of them comes out on top. Sometimes they'll get a nice headshot or a perfect spray. I imagine a similar parallel in Mordhau.

  • Furthermore, if we're talking about the new player experience, why don't we ask some newer players how they feel? This thread consists of above average players speculating on what the new player might think about feints. Ask DasShuugs what he thinks about feints. 30 hours in chiv and hundreds in Mordhau (although he was able to read a lot at only the 100-200 hour mark). He is a prime example of what a new player might experience in the absence of matchmaking: having to fight chivalry veterans with thousands of hours and having no prior experience. Admittedly he had resources and help that other players didn't get, but I think that only emphasizes the need for an expansive tutorial and variety of resources to learn the game. You could argue that he is just an outlier, but we don't really have any kind of data to confidently conclude that. It's not just Shuugs either, there are other new players like Bob in EU.

  • All feints, with the exceptions of stabs, are readable. Highlighting the strength of stabs and thus the strength of feints via stabs is useless. Stabs are the issue (in that particular context), not the feints.

  • Arguing over whether or not a new player finds swing manipulation or feints more interesting is also useless. Unless a player has played the game, they probably have a limited sense of what is actually happening and therefore both feints and drags would appear just 'normal' to them. Extremes of feints (headbobbing) or swing manipulation (spinning or spazzing out) are both likely discouraging to new players. Feints objectively look cleaner because of the general lack of camera movement (yeah it exists Frise, but it's less extreme than chiv and at least in NA there's not many people doing it because it's not really effective in any capacity).

  • Longer release weapons also favor waterfalls or z-stabs, not just simple delay drags.

  • The chat log you included in your first post in this thread is taken out of context.

Mercenary 108 580
Knight 685 1855
  • 7
  • 30 May '18
 ÐMontyleGueux

Introduction

In the current alpha build of mordhau, there is no way to manage your loadouts. They are sorted in the order you created them, and that's it. The only way you may do it is by manually modifying a .ini file, which is less than ideal.

This is why I created the Mordhau Loadout Manager!

What's the Mordhau Loadout Manager ?

It's a little software that I created which allows you to order, archive, backup and share your Mordhau loadouts !

Here's how it looks :

Interface.PNG

Most of the functionalities are now accessible through right clicking.

The interface is pretty self explanatory, on the left you see the list of the loadouts that are currently accessible in game, and on the right the list of the loadouts that are archived, meaning that they won't be accessible in game to avoid clogging the loadout selection menu without deleting them.

Main features

Ordering loadouts

The Mordhau Loadout Manager lets you order your loadouts at will with a fancy drag and drop interface. I've even added a button to sort them alphabetically if you're too lazy to do it yourself.

Loadout archiving

You may save certain loadouts in a separate file to clean up your game's loadout selection menu without losing them. For instance in my example, I've archived my "fun" loadouts as I plan to play to go duelling and thus I need my regular loadouts ready. I can easily boot up the software again and add them back to the game later on.

Loadout sharing (experimental)

After selecting a loadout and pressing the Copy Share Code button, a share code will be generated and appear in the text area below. You can copy this code to share it, anyone pasting this code back in the Mordhau Loadout Manager and pressing the Import From Share Code button will get your loadout ! This feature is experimental as the share code is still huge (still smaller than the loadout code itself). Here's what a share code looks like currently :

H4sIAAAAAAAEAG1TTY/aMBD9K6s9JdIc/G3n4ANLoeXQFVrQtleTuhBtSGhiVNFf37ED4UOriOfxy5vxvImZ7lznyuC7Zdf+rmrf2+zV7b1dvL6vZz/X2fNLu3kKO//0cqzqX757zuGrd9302Id2X/1zoWobm/1Aym1Sdrb4YgWBaVu3HW4ZA8ZyWLqAZzSW5xAFeliovOoIcJ0PNOqzzwRC5eMbM77gGsg5UYwkJiKZw+zPsTrsfROGxszdeSjBxroQt0DGKqwYV2Qmh0M015T+wfNsj4b3lsAQXArHOvDdB1e/tcftrvF9vypd7S2TcuDXFbajYLL1mPzeVuW4LqtQ7ixlGjaLfu73MW3u6t7D3IVUYPVRNc3JUsVhFbq22VpOE5mOxzpzl8rNTn5gBHxzVTfE1KSNpVFVuTptknbTtX97i43H9AefazTf1y54m0lmKFDJFUE0+JUpU1IlRqSYR17FYSJnJIw6RA2cUlFElAwo1wYKTQUC0SAMGX+sUIW6Y+6ONFSIc8wKzRQwqQiJyPEtFZpekAkc0xlveUxmEWX66nePVkpGwFG8tSGZFpSZGwVV11AAJxqrcKqEBEa0MshAkRJ0vPpcYsOFvskxgrNzZG5qXZ5CRVuDYBwd+Wyfw3CvMiq4RFcJOSWcn+dFblYj5biikqvRApdxaiTNKOGguUdxrXKtVaB/de2LMKLO+GioUI82cTyC0QT4H8MLXNf9w71b+u6jtzDpyp0PpwPe6jz/D9scHNOuBAAA
It's shorter than the actual loadout code, but still pretty awful looking. I will see how I can improve this feature in the future.

Loadout Backups

By using the backups buttons on the center, you can manage backups of your Game.ini file containing all your loadouts.

Downloading

It is currently uploaded on my google drive, I will post the share links to the different versions here :

Up-to-date version :

Mordhau Loadout Manager V1.5 https://drive.google.com/open?id=1ezk2dlON-b0g9S4f5vP3J4BYn7L-JMEi

The interface have been reworked, most of the buttons have been replaced with a right click menu.
You will also be notified if there is a more recent version avaliable.

Additional Notes

Please Make a Manual Backup

While the current version have been extensively tested and should be fine, I recommend saving your Game.ini file somewhere else before you start using Mordhau Loadout Manager. It can be found at C:\Users[username]\AppData\Local\Mordhau\Saved\Config\WindowsClient. You never know...

Steam Cloud Conflicts

Note that the steam cloud isn't too happy about the game's files changing. If the steam cloud report a conflict, always select "upload to the steam cloud".

Bug reports and suggestions

Don't hesitate to report bugs in this thread, I will make sure to take a look at them.
I'm also open to suggestions. What kind of features would you like to see in Mordhau Loadout Manager ?

Special thanks

To triternion. You guys are doing a hell of a job and we love it !