Ramikad

The author seems vanished. His last activity on the forum dates back to march 2013... so it would probably be more convenient to redo it from scratch.

Haven't been playing it for a long while, so I may be wrong, but wasn't that "client mismatch" error fixed simply deleting the jampconfig.cfg in the MBII folder?

And to help with that: http://forums.massassi.net/vb3/showthread.php?60565-Death-Star-%28JA%29 Too bad it was never completed.

I second this.

There's also the possibility that this particular design might involve some lore reasons beyond the hilt guard aspect.

I disagree. That design doesn't really seem to serve that purpose - the saber blade will just slip on that blade, until it either cuts off the main emitter or the side ones.

I agree. And quoting for the truth, DT85... And now that EP7 stormtrooper is complete...

Pretty much the same as Ping and Afinity; if anything, I'll miss a few mods and files, but frankly it didn't have enough for me to love it or miss it, especially when it all started going downhill.

Lightsabers already work underwater, just add the line onInWater 1 in the .sab file. There's a whole lot of these lines to achieve the most various results, from playing an animation when activating the lightsaber, to restricting certain Force powers, etc.

Use with caution, in my tests I didn't really get appreciable results.

With all the due respect, I wouldn't call it "good looking". Admittedly, though, there weren't many more options available to achieve it.

I think that fog.tga is only a help when mapping, it doesn't even exist in base JA but only in mapextras.pk3. About the caustic effect... I don't know. Honestly I'd rather have it "hard-mapped", with specific textures and shaders.

Apparently we can - checked out the fog shaders: textures/fogs/fog1 { qer_editorimage textures/fogs/fog.tga qer_nocarve surfaceparm nonsolid surfaceparm nonopaque surfaceparm fog surfaceparm trans q3map_nolightmap fogparms ( 0 0 0 ) 256.0 cull twosided } The ( 0 0 0 ) indicates the RGB color, and the 256 (in this case) is the distance at which the fog turns completely opaque.

Almost two: one for swimming and one for standing still, even though I noticed somewhere in the code that it could support a backward swim animation. I tried with a fog brush not too long ago and the effect isn't that bad. The underwater blue hue however ruins it a lot.

Make sure the path is correct - it should be weapons2, not weapon2, also make sure the texture paths are correct.

Yeah, also properly known as Caustic Effect.

That water... that water...

Raise that data rate - I doubt it's the solution to this, but it helps listing more servers and at more decent pings.

JKHub has taken ovah.

Then I can imagine the cheat-only Level 4 effect: Black Screen Of Death.

Not sure if -lomem could fix it, as far as I know it's only used when dealing with memory limits. Pande might know more, I recall reading something he posted after compiling his DOTF map about it being "so saturated with lightmap info" that even the Menu was having troubles. Can't seem to find it though.

Let it rest, then. Personally I prefer having Dark Forces and the JK series this way, holding a special place in my heart, instead of having them rebooted and butchered helplessly.

Are you sure? I think I once had a misc_model going out in the void with no problem at all, except for shadows where it touches the void.