(11-10-2013, 05:32 PM)Tassabra Wrote:  quick question:
The crafting bot seems a bit ... slow?
When it starts the craft, the info tab in the crafting tool windows stays on crafting = false for 2 seconds, although the craft ingame has already started. same after finishing a craft, it stays on crafting = true, even though the craft is over, same delay as when starting a craft. Is it just me or is it designed this way?

(11-10-2013, 05:40 PM)darkboz Wrote:  I was going to ask for the same, it seems that previous version skill manager had a 500ms delay by default, the new version is 1000ms and can't be lowered, i think 500ms worked well, any reasons you changed that delay ymko ?

(11-10-2013, 11:34 PM)ymko Wrote:  

(11-10-2013, 05:32 PM)Tassabra Wrote:  quick question:
The crafting bot seems a bit ... slow?
When it starts the craft, the info tab in the crafting tool windows stays on crafting = false for 2 seconds, although the craft ingame has already started. same after finishing a craft, it stays on crafting = true, even though the craft is over, same delay as when starting a craft. Is it just me or is it designed this way?

Yeah it's designed so it makes sure that Synth is correctly up, otherwise it may create problems when server lags.

---

(11-10-2013, 05:40 PM)darkboz Wrote:  I was going to ask for the same, it seems that previous version skill manager had a 500ms delay by default, the new version is 1000ms and can't be lowered, i think 500ms worked well, any reasons you changed that delay ymko ?

The main reason is that it does a lot of checks, and we don't want to be checking a lot. I can let people lower it but that's going to be at their own risk :P It might make it slower or faster if you lower the delay...

(11-11-2013, 08:07 AM)darkboz Wrote:  

(11-10-2013, 11:34 PM)ymko Wrote:  

(11-10-2013, 05:32 PM)Tassabra Wrote:  quick question:
The crafting bot seems a bit ... slow?
When it starts the craft, the info tab in the crafting tool windows stays on crafting = false for 2 seconds, although the craft ingame has already started. same after finishing a craft, it stays on crafting = true, even though the craft is over, same delay as when starting a craft. Is it just me or is it designed this way?

Yeah it's designed so it makes sure that Synth is correctly up, otherwise it may create problems when server lags.

---

(11-10-2013, 05:40 PM)darkboz Wrote:  I was going to ask for the same, it seems that previous version skill manager had a 500ms delay by default, the new version is 1000ms and can't be lowered, i think 500ms worked well, any reasons you changed that delay ymko ?

The main reason is that it does a lot of checks, and we don't want to be checking a lot. I can let people lower it but that's going to be at their own risk :P It might make it slower or faster if you lower the delay...

Ohhh i see, yeah better be safe than sorry you're right, would be nice to be able to lower it when you have no lags (maybe let 1000 by default but allow 500 ? or a little checkbox "X i have no lag !" that allow you to freely change it :))

I had another request for you, could you add something to the CP condition like this, MAX (instead of a fixed number) = your max CP ? So that in my profile i don't have to change manually the CP amount for TOTT each time my max CP change. Or even better (if it's possible) the possibility to do calculation directly into it, like MAX-1 (but maybe that's a bit too complicated when you want something user-friendly ^^)

Thanks :)

(11-11-2013, 12:58 PM)Shaolin2 Wrote:  i have a bug in v. 2.1.0

from time to time stucks the Bot and spamms in the Console
"Can't cast anything please check that your profile set up correctly"

i have watch the bot and Console the profile is set up correct.
He can make 10 crafts or more and then booom bot stuck on Hasty Touch (cross skill)


I have no clue what the cause is

(11-11-2013, 02:17 PM)darkboz Wrote:  Yup it's probably because your current craft doesn't fill any condition in any of your profile entry (like more CP than expected, or an excellent condition or stuff), i recommand activating the debug box (at the top of the tool) and look @ the console for every evaluation to see where it goes wrong.