Search results

This wont be MB2 related.

your best bet at finding what is interfering would be to try and browse to http://update.moviebattles.org/MB2Core.xml

V1.6.2.1 Update Gameplay: Fix: Sweep kick should now knockdown as intended vs crouched targets. Fix: Wook slap should no longer stagger vs crouched Sith. Fix: Push / Pull knockback now working as intended. Fix: Wookiee should now be properly immune to projectiles and some explosives. Fix...

Sounds like some over zealous anti-virus in this case.

In these two cases it wasn't us using an API that caused problems and needed testing to fix. We generally don't use platform specific APIs, but may be using more in the future. If the day comes that a certain API is unavailable on XP that is needed for a feature then there will be nothing we can...

The answer is maybe. The upcoming hotfix will have the discord dll switched over to be delay loaded, and some code added that should stop any discord function being called for anything earlier than Windows 7. Will it work....hopefully.

Its not quite as simple as that. MBII/JKA does not exist in a vacuum. Be it underlying software, hardware or interfaces, all of them combine to make the operating environment. As that environment changes and we want to do more modern things it will become increasingly difficult to keep it going...

Thats right - More than ever. a 100% increase. Two games now run properly, a massive increase from the one previous option.

https://www.microsoft.com/en-gb/windows/windows-7-end-of-life-support-information

From an MBII perspective there are three reasons. Firstly new technologies are not developed for older systems. If new features had required say the 2015 or 2017 runtime, I don't think these will even install on XP, maybe they will but eventually the steady march of progress will mean MBII...

Sorry puppytine i cant allow you to distribute modified binaries. I will do an official build with the compiler flag set and post it here shortly. This is likely a result of bumping the compiler version, this is a requirement for upcoming new features, if we can avoid breaking compatibility...

In that case, sacrifice a lamb and say Microsoft backwards three times in front of a mirror. I cant tell you how to defeat the demon that appears, but good luck.

You can either use launcher with the mono framework which will run CLR applications, or you can use the manual installation steps. Launcher used to work for installation on MacOS but i dont have any up to date information, it is broken on several linux distros.

Will be in C:\Windows\SysWoW64 for 64-bit Windows.

Updated the guide to state that MBII now requires Microsoft Visual C++ 2013.

Try installing this version of the VS redistributable - https://aka.ms/highdpimfc2013x86enu

MBII must be installed on the same drive as steam if you wish to use steam JAMP. One does wonder if this could be worked around using volume mount points, but that's some advanced stuff.

No one as far as i know really looks after MBII Client - it certainly hasn't been updated in a couple of years, the work arounds are known and in some cases desirable.

Is there a crash log?

Indeed. This sounds like a bad design. Open mode with class limits should be in a first come basis.