Jump to content

Home

GHOUL 2 and anti Push/Pull + Backstab server config demo


Emon

Recommended Posts

Posted

Lately I have been messing around with different server variables in order to create multiplayer duels that are much more like singleplayer, and that offers some protection against the Push/Pull + Backstab combination that some of us know all too well. The major component was enabling GHOUL 2, Jedi Outcast's animation and hit detection system. Now in singleplayer, GHOUL 2 collisions (poly-to-poly) are already enabled, however they are not in multiplayer. Enabling this creates much more intense duels, and it's much harder to do the Push/Pull + Backstab combo and actually win with it. This also enables much more accurate blocking.

 

Since people still can use the Push/Pull + Backstab combo with these settings, no Force is the best with these following settings. Hopefully in the next patch, plus the following settings will be the ultimate in multiplayer saber dueling...

 

Here are the variables and their commands in which I used in my demo (which you can download below):

 

seta g_sabertracesaberfirst 1 <--- This command is enabled by default, but enter it just in case.

 

seta g_saberghoul2collision 1 <--- This is the big one. It enables GHOUL 2 hit detection for lightsabers in multiplayer. While this will increase network traffic, it won't be very noticeable (if at all) for low ping users such as cable and DSL users. Don't be discouraged to use this because of slightly increased network traffic, because it's not a lot!

 

seta g_dismember 300 <--- This is purely cosmetic. It enables dismemberment, nothing else. Most servers have this already.

 

 

And to demonstrate these settings in multiplayer with a few bots on the Jedi Master skill level (still fairly stupid), download the following demo. To install it, extract it to your Jedi Outcast\GameData\base\demos folder. If you don't have one, make one. Then go into multiplayer, select Play Demo from the Play screen and watch the demo (don't press any keys during the demo, it will abort it).

 

Here is the URL to the download: http://www23.brinkster.com/emon1337/GHOUL2_Test.zip

 

 

I hope more server admins start using this! Enjoy!

 

 

P.S.

I know this won't solve ALL backstabbing problems,

but it should help to make saber combat more

realistic and fun, especially on servers with no

Push/Pull, like limited Force or no Force.

Posted

why isn't ghoul2 enabled by default? is it THAT much more network traffic? seems like a good idea to me...

 

also, how does ghoul2 affect gameplay in this...meaning, could u do more damage by striking one's head etc?

Posted

I just tested them out, and they work great!

 

For the first time I actually had fun fightin' a bot.

 

The saber blocking is alot more accurate with these commands, it looks more real. And yes, i noticed a difference with the backsweep/stab, it is no longer unblockable as long as you are facing the swinging blade.

 

 

I'll see if the server i regular will put in these commands, they friggin' rocks!

Posted

Yeah I just tried it too, and it's totally awesome...from what I gathered it's harder to pull off the backstab/sweep because I think they have to be directly behind you...

 

But the saberfighting rules...

Posted

The saber trace just reduces blocking to 1.02, you might want it if you're on an NF server (no pulling, quicker kills).

Posted

I hope these settings will be used on servers, especially on finnish servers (They won't be used there, though, because the people running the servers won't be looking here for server tips... :( ).

Posted

This Ghoul and SaberTrace stuff will save the game - Raven!

 

Plus, give us kick back as a single tap option.

 

If you make these ghoul and sabertrace things server side rules so we can find servers running them it'll be good.

Posted

I tried it using g_sabertracesaberfirst 0 and found that although it made for a little less blocking, the gameplay was more fun when leaving it set to 1.

 

Use both settings as originally posted and it rocks! Will remain on my server.

Posted

Hi.

 

We really do need servers running those settings.

 

Hey but how about a rule?

 

Such as in MOH:AA you had to put CKR or CPR depending on the sever-side mod.

 

So how about 3 letters that signify the 3 settings:

 

1 - if one setting

2 - if two of em

3 - if all three

 

so like GSD

 

G = Ghoul 2:

 

seta g_saberghoul2collision 1

 

S = Saber 1.02:

 

seta g_sabertracesaberfirst 0

 

D = Dismemberment:

 

seta g_dismember 300

 

All you would have to do is have it so servers that run these settings have it in their name...

 

Example:

 

QuietSith's Darkside GSD

 

Or GS if I only wanted Ghoul 2 and Dismemberment.

 

Whatchya think?

Posted

Uh.. exactly it's for server's - but the clients can't see what the settings are - they don't display as rules.

 

So we need a way of having servers tell the clients.

 

Get it?

Posted

The following info is not available for the server info, if a client wants to know:

 

seta g_sabertracesaberfirst 0

 

seta g_saberghoul2collision 1

 

seta g_dismember 300

 

Please check the factuality of your responses before you respond.

 

Stop trolling, thanks.

Posted

Only if the game reports those settings.

 

That's the problem, it doesn't.

 

So no program can find settings that are not reported.

 

It'd have to be patched or modded in the game to have it report the settings.

Posted

Then the program will have to:

server side: make a info file on the server (whit info on how it's set)

client : look for that file and get the info.

 

+ ohter game finding options

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...