Jump to content

Home

Winning Saberlock


ZionHikari

Recommended Posts

Saberlocks are automatically won by whoever successfully pulled a feint on you (attack + alt attack). You can break out of such a lock by pressing back + alt attack if your DP or MP aren't in the red.

 

Feints work like this: If an opponent successfully delivers a feint and does not hold down the attack button, then you will get slow bounced and he has an opportunity to attack you. However, if he holds down the attack button when your DP is in the red, then you can instantly die, otherwise he will get slow bounced if your DP isn't in critical range.

 

Overall, it's not that confusing, just avoid having high MP and red DP, and you can break out of locks (but you may get slow bounced still, just that there's more space between the two of you).

Link to comment
Share on other sites

Yes thats a big problem to me as well. The saber manual says almost nothing about saber locking, which is strange because its a big part of saber combat. i didn't know how to escape a saber lock unitl i read it somewhere else on the net. apparently the only way to escape a saber lock is to press Alt + back very quickly. But if you mean how to win a saber lock, who ever starts the saber lock automatically wins.

Link to comment
Share on other sites

The thing that confused me is that one readme states that:

For a riposte, hold attack + ALT attack when you parry.

 

The other says:

Just hold attack.

 

Because when I play vs. a bot, when I do a FAKE when i'm parrying, I don't get a saberlock, I don't get the NORMAL parry, but I do get a slowbounce 9 out of 10 times (so if I parry without a fake, I'll get a ''faster'' slowbounce, fake during parry ''slowbounce''.

 

What's up with that? Because I never found the difference between parrying / fake parrying in a manual.

Link to comment
Share on other sites

So in short:

 

Parry:

  • drives up enemy MP
  • reduces the DP damage inflicted on you
  • great for stopping combos

 

Riposte:

  • cashes in on enemy MP
  • very little DP reduction
  • great for stopping combos and shifting you into the aggressor role after cashing in on enemy MP

 

Riposte happens when you tap attack during the pre-block animation + parry direction. Also works when you tap attack at the end of an attack swing + parry direction when you need to parry following your attack. It used to be that when you successfully riposte, you'll get the saberlock animation, but that's been found to be superfluous. Now you immediately cash in on enemy mishap.

 

You don't slow bounce from a normal parry; a normal parry drives up the opponent's MP meter until it maxes out. When you riposte, you cash in on the enemy MP level, including the slow bounce when the enemy has low MP.

 

I guess that manual needs some serious updating and truncating...

Link to comment
Share on other sites

Strange, I could have sworn I updated it for 0.1.0, but I just checked it a its very different from the one I sent in and teh one thats at this forum. Very out date. Great, and I bet the judges for the contest are clueless about a few of the newer features because of it. :( I really wish they would have taken me up on my offer to show show them the features ingame. Well, thats what happens when things are that rushed. At least we got in ;)

Link to comment
Share on other sites

It used to be that when you successfully riposte, you'll get the saberlock animation, but that's been found to be superfluous. Now you immediately cash in on enemy mishap.

 

Ah, then I guess what I did was ripostes all over the place lol.

 

See, due to the manuals I kept thinking that there was a parry, and a ''saberlock'' parry, but now I know that it's been removed :p. Thanks.

Link to comment
Share on other sites

Ow man .... reposites dont do saber locks??/ oh my god..... that saber manual needs some freakin corrections... you guys tell us to read the saber manual to know how to play because its the most important thing yet its heavily outdated!!! :firemad:

 

 

Guys i have a question thats been itching me... when a random saber lock happens who is the winner of the saber lock?

Link to comment
Share on other sites

well I took a closer look at the manual thats in the the docs folder and its VERY different from mine. In fact, it looks like someone tried to simplify it, but whenever they did it, it must have been a long time ago. They aren't even any reposits in there as far as I can see.

 

EDIT: well I just checked my repository very of the saber manual and its completely updated as far as I can tell. Maybe the the wrong version of the manual was put into 0.1.0. I updated the one in the enhanced folder docs since when I first got the repostory stuff for my new computer, I only seem to have gotten the enhanced folder stuff for some reason. I'm not sure if theres another manual in the rest somewhere that may have gotten used for 0.1.0. Strange :s

Link to comment
Share on other sites

Outcome is random? I thought the purpose of the way saberlocking works now was to eliminate the randomness of saberlocking...

Actually I think he's referring to the RANDOM saberlock that happens if your saberlockfactor is set to 1. That one is won usually by whoever started the swing and it randomly chooses when to create a saberlock. Mosty of us set the saberlockfactor to 0 so we dont have to worry about that crap. If there are random locks, they really should be the way they were in base JKA if at all, Just with non sucky code :p

Link to comment
Share on other sites

actually the g_saberlocking enable/disable lock. The Lock Factor was just how often the lock comes.

 

Actually, I'm pretty sure that disables the attack feint saber lock too which you DONT want in order to have the full gameplay. Setting the saberlockfactor to 0 disables the RANDOM lock that happens and screws up the combat in my opinion since it adds an element of randomness, which is something that OJP has really come tried to eliminate and has only done so in the past several months. The only thing thats random thats left in the combat is the mishap maxout penalty as far as what happens to the person, which is really their own fault if it happens, but I still might just make it just a knockdown in my code :p

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...