If you use AGB make sure you don't touch the TickPerSecond option, leave it at the lowest.
Leave it at the lowest = More CPU %, 20 ticks more than 40 i think.
Higher = more cpuLeave it at the lowest = More CPU %, 20 ticks more than 40 i think.
What ? no
Higher = more cpu
You won't notice much performance difference aside from a higher cpu usage if you increase it more than say 15.
20 tps ( ticker per second ) means you need your code to take less than 2ms to execute or it's not gonna be running at 20 tps.
The bot is probablly running at around maybe 12-16 when you set it to anything above 10.
It all depends on how well optimized and profiled your code is.
The What ? No was to mephuser
Your totally right of course on the more TPS = more CPU usage part.
However, 40 TPS should correspond to 25ms per tick and not 2 and with ticks that may end in some part of the BT where theres no action to be taken or that gets aborted because some pointer got invalidated it should take way below than that.
10 TPS is actually too slow for the vaulting / combat portion of AGB, 20 elevates most of the slowdowns 25 makes em disappear completely even if my TreeStart hook returns Success and anything above that is just overkill![]()
new Decorator(
ret => ProfileManager.CurrentProfile != null && ProfileManager.CurrentProfile.CreateGameParams != null,
new Sequence(
new Action(
ctx =>
{
var @params = ProfileManager.CurrentProfile.CreateGameParams;
ZetaDia.Service.Games.CreateGame(
@params.Act,
@params.Difficulty,
@params.Quest,
@params.Step,
@params.ResumeFromSave,
@params.IsPrivate
);
Thread.Sleep(1500);
// Pause the bot until we make sure we are ingame.
BotMain.PauseWhile(() => !ZetaDia.IsInGame || ZetaDia.IsLoadingWorld, 1500);
})
)
)