Search results

// RUN/WALK TOGGLE set walk "cl_run 0; bind SHIFT vstr run" set run "cl_run 1; bind SHIFT vstr walk" bind SHIFT "vstr walk" Save that as autoexec.cfg and put it in your MBII folder, and when you get in-game go into console and type /exec autoexec.cfg. About as much as you can simulate toggle...

Support is Jedi/Sith's primary role, given how their kit works. I don't mind if people want to play them like a warrior, but it was never intended to be this easy. Rushing in ahead of your team and running straight at gunfire should have it's risks, no matter what class you're playing; Jedi...

You know, there are other classes to play than Jedi. I know half the appeal of Star Wars is the glowbats, but MB2 is more than just lightsabers and force powers. :p

The problem with Jedi/Sith is how little they're punished for pushing up on gunners across certain distances. For example: Jedi/Sith and gunners should be at equal advantage at long range. Jedi/Sith can reach the gunner, and the gunner isn't hitting hard enough at that distance to drain...

If he were running the 1.00 the game wouldn't let him join at all, it would give him a base version mismatch and he wouldn't be allowed to join any server running 1.01, let alone see a list of servers as I doubt anyone actually runs 1.00 nowadays. Are you running the Steam version of the game...

And this is what happens when I run beta tests and listen to Jorge. 8)

If you have the old temporary fix, which is MBII.pk3 with a bunch of z's in front of it, please delete that from your GameData folder.

What error is it, do you think you can screenshot it before it closes?

So no error messages, nothing? The game starts, then randomly shuts down without giving any sort of prompt? And you are reaching the logo screen?

This bit was included in the installation guide that can be found here:

Reinstall JKA, then MB2, and see if that fixes it. Also what version ATI drivers are you on, and what card?

So it crashes when the MBII logo video starts up? Try updating your DirectX drivers. More often than not that is the cause. Yes, I know all of these suggestions are things you would normally hear from a Microsoft support specialist (haha, funny joke), but they usually work, as sad as it sounds.

If you're using the Steam version you cannot use the launcher unless you choose MBII Client in the options of the launcher. Untrue, launcher will work with Steam under normal circumstances. - Spaghetti

Internal Beta Testers Needed! | Movie Battles II Community https://community.moviebattles.org/forums/betaapp/ Reapply and follow the instructions.

Wilde and I worked directly on the saber system for months, and this was before you were even on the beta team. I can tell you that special moves were what we tried avoiding most when we developed the v0 system, which was based loosely on the RC1 design that I thought would have been perfect if...

It's possible HUB1 is causing the problem, yes, but the server isn't starting with that active, is it? Also, is your g_MinMBPoints set to 300? If so try setting it to 80.

Stagger is a bad mechanic in saber vs. saber, it always has been and it always will be. That's why it has been almost entirely worked out of the game and replaced with better solutions, like in most cases disarm. Disarm however wouldn't have been a good solution due to it's ease of use, and...

Works just fine on my dedicated server. Could you provide post the relevant part of your server config? Just remove any passwords or other nonessential shit.

That's a thing to consider. Can't really restrict those kinds of things more than they already have been when "wait" was taken out of the game. Could also do it with any gaming mouse that has more than the standard right/left/middle click.

He's just annoyed we're trying to remove as many of the complications from the saber system as possible. I don't understand the YDFA change, but it does leave you open so I guess it really doesn't matter in the grand scheme of things. Most changes to the saber system will prioritize the...