Rogue/Ninja Discussion

**SamanosukeShiva** · 2014-12-04 12:25

still gonna be doing raiton, fuck that noise

**Niiro** · 2014-12-04 12:27

In what way is a faster and easier to execute skill considered "that noise"....

**Arthars** · 2014-12-04 12:32

looking at first glanze, im sure switching to shuriken is better burst DPS for short time... TP is going to burn out so fast tho

sticking to current rotation is prolly still better for the long run, altho shortened

**SamanosukeShiva** · 2014-12-04 12:36

2 mudra u can fit in between GCD, there is no gain in DPS just by doing 1 less mudra. Unless you fuck up your mudras all the time in which case cant help you there.

**Kiarax** · 2014-12-04 13:01

I sure wish my ping was low enough to be able to cast 2 mudra combos without wasting any GCD time. Regardless, Raiton still seems like it'll parse ahead (and dont need to worry about DE ever dropping during cast), but at least having the option will be nice.

**Niiro** · 2014-12-04 13:45

The only place Mudras ever "snap" for me is the housing area, not a lot of raiding going on in the Lavender Beds unfortunately.

**Arthars** · 2014-12-04 14:11

well at least they know the mudras problem amongst everyone

its hard to fix really, cos its more on latency than game mechanics issue

they didnt have exact way to fix for now, but at least they are looking into it

**kisada** · 2014-12-04 14:38

wouldn't setting mudra delay to .1 help, as a starter?

**Niiro** · 2014-12-04 14:54

Or they could just change it so they don't share a recast when Ninjutsu is ready.

ie. Each one has its own .5s recast.

**Sigmakan** · 2014-12-04 14:57

The ninjutsu combo tree needs to be client side. . . .

**Raldo** · 2014-12-04 14:57

I would just set it to zero recast and just bind it by its animation lock. A .1 recast, or splitting each one into its own recast would basically all function like that anyway.

**Kaisha** · 2014-12-04 19:54

Originally Posted by Sigmakan

The ninjutsu combo tree needs to be client side. . . .

Then it'd just become commonplace in the progression scene to use a 3rd-party plugin that makes your client send the "Use this ninjutsu" packet without touching mudras ever.

Only thing I could think of to address the lag issue is to just let you pre-buffer mudras between GCD before the ninjutsu cooldown is up.

**Kari** · 2014-12-04 19:57

Originally Posted by Raldo

I would just set it to zero recast and just bind it by its animation lock. A .1 recast, or splitting each one into its own recast would basically all function like that anyway.

The reason it "lags", presumably, is because the game is waiting to make sure the next Mudra is not on cooldown before casting it. If they had separate cooldowns, it's likely they'd fire faster. 0.1 CD would be about the same, since they'd come off CD before the animation ends. As far as the nerfs go, it's not as bad as I thought, but still seems unnecessary.

**Deadgye** · 2014-12-04 20:20

Originally Posted by Kaisha

Then it'd just become commonplace in the progression scene to use a 3rd-party plugin that makes your client send the "Use this ninjutsu" packet without touching mudras ever.

Only thing I could think of to address the lag issue is to just let you pre-buffer mudras between GCD before the ninjutsu cooldown is up.

The server would then proceed to check that it received the correct mudra commands for the ninjutsu, determine the client is wrong, and tell it to go fuck itself. One of the primary problems currently is that which ninjutsu can be used, displayed client side, is dependent on what the server thinks is available. This is the reason we sometimes start to fire off a 1/2 mudra ninjutsu after using 2-3 mudra and then it stops mid animation waiting for us to press the ninjutsu button again. Making the which-ninjutsu calculation client side would solve that problem and not introduce any security problems like the example you mentioned unless they for some god awful reason also decided to not verify the ninjutsu server side afterward.

**Obsidian** · 2014-12-04 23:23

The server validation is what's causing the fuck-ups. That's the entire point. If the mudras were client-side there would be nothing for the server to check.

**SamanosukeShiva** · 2014-12-04 23:23

one of the worst thing is when sometimes i do huton, i press ninjutsu, i hear the huton whirring sound effect then i proceed to resume the rotation, but the game decided, no fuck you, and i get a bunny instead cause for some reason the ninjutsu execute didnt go through.

**Deadgye** · 2014-12-04 23:35

Originally Posted by Obsidian

The server validation is what's causing the fuck-ups. That's the entire point. If the mudras were client-side there would be nothing for the server to check.

I don't think you quite understood what I was saying. One specific type of validation does not equal all types of validation.

**Obsidian** · 2014-12-04 23:40

Client-side means not server-side. Trusting the client to send you a valid string of commands opens you up to all sorts of packet-related shenanigans. What you said made no sense, which is why I did not understand it.

**Spider-Dan** · 2014-12-05 03:14

Yoshi just said that the reason why NIN does not have directional requirements is because "ninjutsu takes skill." Bunnies because lag is the balance.

Making ninjutsu foolproof would be the equivalent of making directional requirements foolproof for other melee.

**Niiro** · 2014-12-05 11:43

It's poor design because unlike directionals, ninjutsu is all or nothing.

Even SE has realized the flaw in directional requirements at this point and is removing them from DRG (most likely to be made bonuses like MNK).

Saying that lag fucking up ninjutsu was an intended balancing effect is a new and exciting kind of retarded.

Thread: Rogue/Ninja Discussion

Thread Tools

Latest Threads

Up & Coming Threads

Hottest Threads