Let's Playthough: Alice: Madness Returns (Chp1 - Part12)

Alice is back in this beautifully rendered sequel with twisted visuals, dark story, and quick combat. Alas it has it's shares of glitches (damn you umbrella glitch) and other problems/issues but on the whole I find it enjoyable at the moment.
Let's follow the story of Alice Liddel and her trip back down the rabbit hole shall we?
--------------------------------------------------------------------------------­-----------------------
A mind of metal and gears - we return to the Mad Hatter's Castle to find it in disarray. Madcaps are everywhere (little versions of him), steamworks is the theme (nice dress Alice) and we hopefully gain some clues as to why Wonderland is in the state it's in. We also discover a crippling BUG - which we fix with some file configuration magic.

Category:

Gaming

Tags:

• Lotaeri
• Play
• Through
• Alice
• Madness
• Returns
• Chapter 1
• Part 12

[Lotaeri]

If this fix doesn't work I am so sorry, I tried the fix (altering your config binding, which just seems like black magic to me) posted at EA and it does NOTHING to fix my problem, but the fix I did worked for me, hopefully it will for you as well if you had trouble.

[JanyPL]

Hey, thanks for info how to fix that umbrella bug, I tried do that before, but didn't works anyway. And second thing, when I played found something interesting. When target is lock you can use umbrella by pressing A(jump) button on game-pad, and only on it, on keyboard that don't works, and that is the trick, you need to have game-pad :P

PS.: anyone who have cheap gamepads, try this: dl.dropbox.com/u/25167467/x360­ce.7z - XBOX 360 gamepad emulator, readme inside.

[Muupsy]

@lexos1993 I changed it in +Bindings=(Name="G",Command="T­­riggerBlock true | OnRelease TriggerBlock true") but it doenst really work for me..?

[lexos1993]

i found out that +Bindings=(Name="G",Command="T­riggerBlock true | OnRelease TriggerBlock true") works like a charm! find the defaultinput file in your alice: madness returns or steam folder, and change the original line with this one

+Bindings=(Name="G",Command="T­riggerBlock true | OnRelease TriggerBlock true")

every block you'll have to untarget and retarget tho, but its a solution.

hope that helps

[Lotaeri]

@MrAgr7 Yeah sure man.  Here's the line:

+Bindings=(Name="XboxTypeS_DPa­d_Up",Command="TriggerBlock true | OnRelease TriggerBlock false")

And it used to be something like this:

+Bindings=(Name="XboxTypeS_DPa­d_Up",Command="SwitchMeleeWeap­on")

Let me know if that works, if not message my channel and I'll backup my files/saves and reinstall, and message you back with the line-by-line of my original file.

[Lotaeri]

@MrAgr7 Bah that sucks MrAgr. You're going to fight a few more menacing ruins too (although the horse does break their defense). I would imagine that putting the button assignment back to it's original value would work. If you backed up the file just grab the Command= line that you switched out. Did you reassign the Hobby Horse, or the SwitchMeleeWeapon action?

[Lotaeri]

With that fix - if you use the keyboard *ANY* block button you assign now works (I have a hunch that switchMeleeWeapon won't work though - as we eliminated it from the gamepad). If you use the gamepad then whatever action you eliminated is gone as well, but you can block at least!

Hopefully Spicy Horse will release a patch for the game soon.

[Lotaeri]

6)- Delete everything after the 'Command=' section for that binding.

7)- Paste in the block data you copied earlier. That line should now read: +Bindings=(Name="XboxTypeS_DPa­d_Up", Command="TriggerBlock true | OnRelease TriggerBlock false"

That should fix the issue! The problem is that they seem to be mapping keyboard functions to gamepad input and they forgot to include the block button in their default gamepad config. This fixed the issue for me, hopefully it will for you too.

[Lotaeri]

5) - Now, we're going to adjust one of the other lines. If you're using a mouse/keyboard then you most likely don't care, but if you are using a gamepad with the PC you may want to select the same one I did: +Bindings=(Name="XboxTypeS_DPa­d_Up" I believe that option is 'switch to melee weapon' by default - which I (at the moment) don't see a use for (and I'm more concerned with pressing onward in the game).

[Lotaeri]

2)- Back up your original DefaultInput config file. This is the one we'll be editing.

3)- Open up the DefaultInput.ini file you find in the above directory. Look for this line:  +Bindings=(Name="E",Command="T­riggerBlock true | OnRelease TriggerBlock false")

4)- Copy Everything after the 'Command=' section. We're going to alter a joystick entry with that bit.