and yeah... the server my buddy picked to move too that i also went to, is located in Canada and my latency is like 300ms even with tunnels... so GG
I am from australia and the server i play on is about 270ms.
and yeah... the server my buddy picked to move too that i also went to, is located in Canada and my latency is like 300ms even with tunnels... so GG
Can you guys please try running this version and then post your log after a failed raiton.
All the servers are located in either Canada or Japan, and from what I hear, the latency is better for Australians on the Japanese servers.
Yeah I need to work on the conditions for ninjutsu. I just wanted some feedback on if it worked for other people because I still can't do 3 step ninjutsus yet.That one seems to be alot better, there are some occurrences where it lag's slightly and casts the wrong ninjutsu by mistake. But aside from that, i didn't see a failed ninjutsu either. Also, why when huton is 30 secs or less left, why does it not cast any ninjutsu?
Yeah I plan on adding something like this eventually once I get the mudra stuff ironed out. Right now for pulling it just focuses on maximum dps and keeping combos going, but with grinding fates I can see the value in having something that pulls with ranged attacks so you don't end up stuck in a big group of enemies and get a ton of aggro and AoE attacks. I'll add it some time.is it possible to make a shot range option for user change themself?
Yeah I need to work on the conditions for ninjutsu. I just wanted some feedback on if it worked for other people because I still can't do 3 step ninjutsus yet.
I saw some really interesting stuff in your log though. For some reason it seems like the cooldown I am watching to determine if a ninjutsu actually got casted vs the routine attempting to cast is getting stuck for some reason. I'll work on it a little more tomorrow to see if I can figure out why or a way to eliminate this problem. Thanks.
It's weird that it works better for you since the only change is the additional logging. Out of curiosity, what kind of FPS are you getting when it's messing up?
I've put a new version up that may help. Let me know if it's better or worse. There's now a debug toggle at the bottom of combat settings. Set that to true before submitting a log so I can get a better idea of what's going on when there's problems.
[02:10:39.063 N] Ninjutsu Cooldown = 0
[02:10:39.063 N] lastspellused = Ninjutsu
[02:10:39.063 N] MudraState = Ninjutsu
[02:10:39.092 N] Ninjutsu Cooldown = 0
[02:10:39.092 N] lastspellused = Ninjutsu
[02:10:39.092 N] MudraState = Ninjutsu
[02:10:39.107 N] Ninjutsu Cooldown = 0
[02:10:39.107 N] lastspellused = Ninjutsu
[02:10:39.107 N] MudraState = Ninjutsu
[02:10:39.136 N] Ninjutsu Cooldown = 0
[02:10:39.136 N] lastspellused = Ninjutsu
[02:10:39.136 N] MudraState = Ninjutsu
[02:10:39.151 N] Ninjutsu Cooldown = 0
With your latest version, it seems incapable of doing fates for me. It paths to the fate perfectly, but then gives an error message regarding the ninja routine. I will get the log soon, but if anyone could confirm if it happens to them or not, it would be great.
With your latest version, it seems incapable of doing fates for me. It paths to the fate perfectly, but then gives an error message regarding the ninja routine. I will get the log soon, but if anyone could confirm if it happens to them or not, it would be great.
[09:18:24.675 N] Connection closed! [TCP-E-S] 192.168.178.23:46077 -> 192.99.148.87:31214 (BRK7mAySCkmG17nCoOqR3Q)
[09:18:24.684 D] System.NullReferenceException: Object reference not set to an instance of an object.
at Kupper.Rotations.Ninja.OnPulse() in c:\Users\Scott\Documents\rb\Routines\Kupper\Rotations\Ninja.cs:line 73
at Kupper.KupperRoutine.Pulse() in c:\Users\Scott\Documents\rb\Routines\Kupper\KupperRoutine.cs:line 61
at ff14bot.Behavior.Pulsator.Pulse(PulseFlags CurrentPulseFlags)
at ff14bot.TreeRoot.()