• Likes received 1854
  • Date joined 10 Sep '17
  • Last seen 2 Jan

Private Message

Knight 685 1854
  • 23 Jun '19

Alright everyone, for troubbleshooting please refers to the bard guild discord server here it will be more convenient than the forums.

Knight 685 1854
  • 15 Jun '19

@smug said:
am i missing something? why is character detail not handled by the gpu

Character quality is a mislabeled setting. It controls the quality of animations for characters far away, nothing to do with graphics.

Knight 685 1854
  • 8 Jun '19

@BootyMachine said:
I can't load the playlists I make with Lutebot, is there any specific reason this would be happening?

Pre 2.0 playlists aren't supported by 2.0, that might be the issue.

Knight 685 1854
  • 4 Jun '19

@Lokermann said:

I have an issue with the bot, every time I try to play it it opens a lot of ingames commands.
I've walked through the guide for more than a hour and I still can't figure how to make it work.

Is there anyone who could enlighten my sorry ass I would be very gratefull.

thanks in advance

Check the troubleshooting section. Either you have an extra character at the start or the i is missing in the commands.

Knight 685 1854
  • 4 Jun '19

@Sasquatchias said:

@ÐMontyleGueux said:

@Sasquatchias said:
I'm sorry if my comment is beating a dead horse here, but I cannot for the life of me get LuteBot to work - I've installed it and went through what I think are the correct instructions (making sure the settings synced, changing my console command opening) but whenever I try to use LuteBot in-game it does absolutely nothing - no commands, nothing opening or closing, etc...

Maybe I'm missing something obvious, but any help or assistance on the matter would be appreciated.

Are the sound effects on ?

Yes the sound effects are on, the config is linked to Mordhau's config, and I went and changed the things needed in the DefaultInput file (the open console stuff).

Turn the sound effects off then.

Knight 685 1854
  • 3 Jun '19

@Sasquatchias said:
I'm sorry if my comment is beating a dead horse here, but I cannot for the life of me get LuteBot to work - I've installed it and went through what I think are the correct instructions (making sure the settings synced, changing my console command opening) but whenever I try to use LuteBot in-game it does absolutely nothing - no commands, nothing opening or closing, etc...

Maybe I'm missing something obvious, but any help or assistance on the matter would be appreciated.

Are the sound effects on ?

Knight 685 1854
  • 30 May '19

Isn't it just the same exploit as the dude who deleted some animation to parry without recovery?

He may have deleted the throw animation from his client.

Knight 685 1854
  • 29 May '19

@ParalyzedTortoise said:
Huh, this is strange. So I went through with the setup completely as instructed, console key is pagedown and Lutebot was run as an admin, but it seems to just not paste commands into console, regardless of which automatic console setting I use.

What's even stranger is that the program works when using the live midi input function, but not with just regular midi files. No clue what's going on.

You probably have the sound effects on.

Knight 685 1854
  • 29 May '19

@FloridaMan said:
Awesome work, the 2.0 note conversion is what I am most happy with, it is able to play both my fixed and non-fixed octaves files from 1.2 with no issues.

Here is my collection of MIDI files I created from scores I found online:
FloridaMan's Collection
All songs are done on 20 note cooldown and default for the rest.

Come join The Bards Guild discord for more files, discussion and help:

Thanks, I added it to the post

Knight 685 1854
  • 4
  • 28 May '19

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 :



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.


You can get the latest lutebot version here

Or get access to the code directly on GitHub

Older versions :

Getting Started


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 :


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


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



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.


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.


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



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.



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


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


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.


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)[]

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 685 1854
  • 28 May '19

@smellycathawk said:

@VampireDuck said:
How exactly would you combat this other than vote kick?

The devs could grow a brain and make it so any teammate can move engineer emplacements, like in Chiv horde. Usually actually good engineers walk away from their shit and sometimes it needs to be moved, why the fuck can't anybody on their team just pick up and move a barricade into a better spot when they are the ones actually fighting and using them anyway?

If any teammate could move these barriers they would be more effective in all situations AND they could never be used to effectively grief again.

EZ ffs

fact that this is still a fucking problem a month after release is truly Retardhau

What a horrible suggestion. Engineer would be unplayable due to teammates stealing your shit for fun.

Knight 685 1854
  • 26 May '19

Hi everyone,

I've put together with a few of my friends a short video showcasing the new possibilities comming with the live midi input feature in the upcoming lutebot 2.0 version. Hope you enjoy it. Stay tuned for the update, it's comming to you soon.

PlouPlou and Iodine both played using their midi keyboard in the video. A big thanks to those two incredibly talented members of the community !

Knight 685 1854
  • 20 May '19

@Egossi said:
console says "Command not recognized: equpmentcommand #"
im pretty sure i got everything set up, what am i missing here?

edit: so the correct command seems to be "equipmentcommand #", why is the program entering a wrong command? was this a typo when you coded the program?

edit edit: its because of my keyboard, you should make it adaptive to different keyboards, idk if thats possible but it only works on English (United States) keyboard on windows

This was developped on my azerty keyboard. Your keyboard is probably unsupported by the windows form api.

Which kind of keyboard is it?

Knight 685 1854
  • 16 May '19

@JON影 said:
I played Chivalry for 3000 hours with a ping that averaged between 80 and 100. I was looking forward to its spiritual successor having improved on its netcode, but I'm sad to say that it's just more of the same with this game. At around 80-100, parrying becomes unreliable to the point where attacks will frequently cut through your parry.

The funny thing is, my brother has the exact same ISP with the exact same speeds and he lives only an hour away. Yet his ping usually floats around the 40-60 range. All I can conclude is that the line infrastructure in my apartment is terrible and there's nothing I can do about it.

The netcode has vastly improved. In chivalry high ping would affect others, a single high ping player could ruin the experience for a lot of people. In mordhau the game is mostly server sided which prevents a lot of cheating and lag exploiting at the costs of the gameplay experience of high ping players.

Knight 685 1854
  • 16 May '19

@omarxz11 said:

@ÐMontyleGueux said:
In my experience it is indeed quite common not to get any weapon in the beginning. Though it's not pubg, your fists are very strong in this game and can easily overpower a poorly equipped opponent.


If you still don't believe me, check this out :

Knight 685 1854
  • 15 May '19

Then the update is working as intended.

Hiding isn't as easy anymore.

Knight 685 1854
  • 15 May '19

The early release of stabs was increased, not the release. Early release is a phase between windup and release when the attack can be blocked but can't damage.

Knight 685 1854
  • 15 May '19

@Koda said:
There is no rule against it, mainly because it would be impossible to enforce properly, but also because it leads to more interesting scenarios, at least in my opinion. Just like hunger games!

It's interesting when you team up with randoms because one gave the other a weapon and spared him, or because there is a scary horseman around.

It's absolutely awful when it's two or more friends playing together on voice chat and cooperate through entire games. I think the br matchmaking should prevent steam friends from playing in the same rounds, that would limit teaming.

Knight 685 1854
  • 15 May '19

In my experience it is indeed quite common not to get any weapon in the beginning. Though it's not pubg, your fists are very strong in this game and can easily overpower a poorly equipped opponent.

Knight 685 1854
  • 12 May '19

@Pygex said:

LuteController - play lute with MIDI input

Hi there, I made a thing :3

I figured out how to pick up MIDI input from devices and translate those to the lute console commands. Maybe my code could be merged to Lute Bot?

Link to github

Hi, the feature is already part of the lutebot 2.0 comming very shortly. It also support playing from a regular qwerty keyboard if you bind each note to a key.