Search results

Always been that way. Was too lazy to fix it when I touched it a couple builds ago.

Yes. We kept flinch so DR stays for the moment.

Wasn't ready in time. Had to delay it. You'll see it soon enough.

MBII is based on the SDK not OpenJK. The MBII client that is based off of OpenJK (an older build) is completely separate and we have an open github page for that.

Why would you think seeing peoples shadows through walls is a good idea to prevent corner camping?

Then they did something wrong on their end. THEY are the ones that aren't supposed to break compatibility with mods built off of the SDK. We don't do anything special on our end except disable some modifications we made to the engine.

He isn't. You could use them to see players through walls. I don't think OpenJK has fixed that issue either. Rend 2 might have but I haven't seen anything about it. There was nothing on our end done to make shadows this way. Just how the engine is. Not really a good method of doing that.

It adds complexity to the patching, repairing, validation process because it needs to know the difference between the two installs. In 1.4.6 there was also a very clear problem with handling things this way with DOTF. We all tested with all the maps fully loaded in beta, and when we brought it...

Is it revalidating files? I just tested that myself. I said no, it revalidated files, then I could click things again once it was done.

You can download the 1.4.9 update in the DL section, grab the launcher out of it, and tell it not to update. Ill make an alternate DL in a minute. NVM follow Defiant's instructions below.

Maybe a small one because the tutorials and UI updates won't be fully finished so might be better to just do a smaller one for now.

15 years ago today the original Movie Battles released its first full version for Jedi Outcast. Hard to believe isn't it? On eve of the release of a new Star Wars movie none the less! We wanted to take this opportunity to show off some of the upcoming changes to Movie Battles II. However, for...

That error means you saved a texture file as Progressive. Needs to be resaved as baseline.

Clashing as in locking sabers? It was something we tried a long time ago but we couldn't quite get it to work right from a gameplay sense. It wasn't fluid enough, made jedi/sith extra vulnerable to gunners, etc.

P3 has a velocity of 5500 where as M5 and EE3 sniper modes are 9000. Pretty big difference between the two groups. E-11 primary is 5500, secondary 4000 and proj is 10000 for reference.

That is not a good reason to TK someone.

That + ammo reduction. They have way too much ammo right now for what should be a utility weapon. Snipers are only fun to play as, not to be on the receiving end of. I never feel like I got outplayed by the other person unless its a close range quick scope thing. Most of the time its like...

Wasn't the truth that was the problem, it was the usage of that intentionally meant to be an insult rather than a general statement of fact. Context matters, which is why noobs statements shouldn't be flagged for the same thing.

I didn't remember what the previous ban was about but we can definitely change it to permanent.

1) You were banned before by someone else other than me. Those accounts are still banned (more than one). Your account on discord could have at the time been considered ban evasion for past offenses but we let it slide. We were already being lenient with you. 2) You directly insulted someone...