About Receiving Help from the Support Board: While all members may answer questions posted in the Support board, you should only rely on responses posted or confirmed by support moderators and website administrators. Any solutions provided by members of the community that are not verified by a staff member (as indicated by a light-green background) are provided as-is, and we cannot take responsibility for any of the results of said actions.
About Responding to Support Threads: If you feel you know the answer to a question, you are welcome to respond to the thread and politely offer assistance. Please be courteous and try to provide detailed and helpful solutions to users who may not be as advanced as you. We ask that you refrain from posting one-sentence solutions.
* Topics denoted with the [OPEN] tag are awaiting a response from the end user. You are welcome to post in these threads if you are experiencing a similar issue so we may provide further support.
* Topics denoted with the [RESOLVED] title have been successfully answered and confirmed by a support moderator and the end user, and should be used as a reference. These topics are locked.
* Topics denoted with the [CLOSED] tag were either inactive for more than 30 days or the end user did not respond to a suggestion and confirm if the issue was resolved. These topics are locked.
There is no official way to change the configs in OpenMBU, since it's trying to be a 1 to 1 recreation of the Xbox 360 version without any modifications.
However, there is two ways you can change the controls yourself.
First method [Installing a mod]:
Warning: Spoiler!
Connie stitched together a mod that allows you to change your keybinds within the game, here's the file:
The installation process should be present in the README file.
Second method [Changing the code by yourself]:
Warning: Spoiler!
The second method will require you to go through a text editor
Find the "default.bind.cs" file, which should be under "\marble\client\scripts"
Next, open the file using a text editor (Notepad++, Visual Studio, either or.) and scroll all the way down to line 610, that's the line that contains general controls (keyboard or controller)
What's going to be relevant to you is line 632 up to 636, those are you keyboard controls to move the marble.
As for mouse, it's going to be just 649 and 650.
Though this doesn't mean you're limited to those controls, you can change a keyboard bind to work for mouse and vice versa, it's just a matter of preference.
For example, if I want to bind blast (which is called altTrigger in the code) to a key instead, I would change the first value from "mouse" to "keyboard", and the second to whatever key I want (in this example, "e", WITHOUT the quotations.)
This is what the line initially looked like, underlining the ones you should change:
moveMap.bind( mouse, button1, altTrigger );
Applying what I instructed you to do, the code should now look like this:
moveMap.bind( keyboard, e, altTrigger );
The way you do it to change something into a mouse control just the opposite, where you write mouse and button0/button1 instead.
As a handy guide, this is how you can read the code:
moveMap.bind( {hardware}, {input}, {action} );
We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.