Search results

Not locked. See earlier reply. And i am actively looking. I mean the last time i broke it the cheaters clients started crashing. Like i said, arms race.

All exploits that are reported get looked at and fixed, but this is an on going arms race.

Why do you want to know?

Do you crash if you try and load the map locally?

Does it matter which team? Does it matter which class? Which part of the menu exactly does it crash on? Do you have custom models? Have you removed any custom models to see if the issue persists?

I will do a dev diary on the first month of gamestats when we reach that point. It will be a warts and all over view of the data, the good the bad and the ugly.

Was this after a map change or anything? As much detail about what was happening at the time would be helpful. No matter how insignificant.

Yes, it is related to gamestats. Stats are sent at the start of a new round, things like RTV which issue map commands at inhuman speeds seem to be able to cause issues on new rounds. This should be fixed in the next release.

And that execs after a map change?

What is your rotation and how is it configured?

Do you run RTV, if so how is it configured?

It's not something coded at the moment, but the data is there so it's trivial to add.

V1.7.0.1A V1.7.0.2 Update General Fix: Addressed issue where selected points were not being fully applied to classes. Fix: Player model RGB color should now be preserved during private duels. Models Fix: Bastilla holds lightsabers correctly again. Maps Change / Fix: mb2_deathstar Fixed...

It's being tested right now.

Make sure your connection settings and com_maxfps setting didnt get lost during the update. Because a number of cvar names changed some peoples configs may have been reset.

Just added a small note to the main post about Ubuntu systems of atleast 16.04 and earlier and the required package for libcurl.

Just a little update on the behind the scenes stuff you cant see. Only after a few hours here is how the death star heatmap for kills is already taking shape. At this stage the data we are getting back is really promising and giving me great confidence that this unseen feature is going to be of...

We just pushed a small fix out via launcher to bring the version to 1.7.0.1 to address a crash that would occur on servers after so many kills had occured.

V1.7 Update Gameplay: Change: In Open and Duel mode lightsabers now use a standardised hilt for hit detection. Hilts with different emitter locations have shorter or longer blades displayed to match the standardised reach. Change: Show a cooldown timer for Droideka deployment. Fix: Speed...

You can reset launcher by running the file reset_mbii_launcher.bat in your GameData folder.