Jump to content

Home

Ghoul 2 causes more problems than it's worth.


QuietSith

Recommended Posts

i can't even see the page cause i decided to stay with IE 5, loop holes and crap(coudn't be bothered messing with ms problems)

but ghoul 2 doesn't exactly do it itself, raven could nerf it if they wanted, they jsut decided not to.

Link to comment
Share on other sites

Change my mind?

 

Um, no, if you read the post:

 

"Ghoul 2 was great at the time for helping prevent backstabs from working great, but we find out that it does two things badly with JK 2 ++:

 

Causes blocking too be way too much.

 

Slows down the gameplay quite a bit.

 

I suggest having Ghoul 2 by default off and sabertrace default off (keeping the blocking as low as possible) and of course dismemberment at 300.

 

We found this is the best setting so far in combination with JK 2 ++."

 

 

Run a server with the following parameters, and hit someone in the back:

 

Ghoul 2 on:

 

g_sabertracesaberfirst 0

g_saberghoul2collision 1

g_dismember 300

 

Now do the samething with it off:

 

Ghoul 2 off:

 

g_sabertracesaberfirst 0

g_saberghoul2collision 0

g_dismember 300

 

Notice the changes in automatic blocking?

 

JK 2 ++ (the mod) already stops assfighting, so Ghoul 2 is overkill and causes too much blocking.

 

Ghoul 2 was/is useful for slowing down assfighting if you are not using JK 2 ++, due to the increased blocking - but it's not nearly as good as simply running JK 2 ++ to stop assfighting.

 

Does that make sense?

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...