the same exception happened 3 times
Code:[Tick] Exception during execution:Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Object reference not set to an instance of an object. at HREngine.Bots.PenalityManager.getHPBuffPenality(Card card, Minion target, Playfield p, Int32 choice) in ***********\Routines\DefaultRoutine\Silverfish\ai\PenalityManager.cs:line 282 at HREngine.Bots.PenalityManager.getPlayCardPenality(Card card, Minion target, Playfield p, Int32 choice, Boolean lethal) in ***********\Routines\DefaultRoutine\Silverfish\ai\PenalityManager.cs:line 166 at HREngine.Bots.Movegenerator.getMoveList(Playfield p, Boolean isLethalCheck, Boolean usePenalityManager, Boolean useCutingTargets) in ***********\Routines\DefaultRoutine\Silverfish\ai\Movegenerator.cs:line 292 at HREngine.Bots.MiniSimulator.doallmoves(Playfield playf, Boolean isLethalCheck) in ***********\Routines\DefaultRoutine\Silverfish\ai\MiniSimulator.cs:line 140 at HREngine.Bots.Ai.doallmoves(Boolean test, Boolean isLethalCheck) in ***********\Routines\DefaultRoutine\Silverfish\ai\Ai.cs:line 123 at HREngine.Bots.Ai.dosomethingclever(Behavior bbase) in ***********\Routines\DefaultRoutine\Silverfish\ai\Ai.cs:line 299 at HREngine.Bots.Silverfish.updateEverything(Behavior botbase, Boolean runExtern, Boolean passiveWait) in ***********\Routines\DefaultRoutine\silverfish_HB.cs:line 210 at HREngine.Bots.DefaultRoutine.<OurTurnLogic>d__1c.MoveNext() in ***********\Routines\DefaultRoutine\DefaultRoutine.cs:line 751 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult() at HREngine.Bots.DefaultRoutine.<Logic>d__3.MoveNext() in ***********\Routines\DefaultRoutine\DefaultRoutine.cs:line 488 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Triton.Bot.Logic.Bots.DefaultBot.DefaultBot.†„.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Triton.Bot.Logic.Bots.DefaultBot.DefaultBot.„.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Triton.Bot.Logic.Bots.DefaultBot.DefaultBot.€„.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Triton.Bot.Logic.Bots.DefaultBot.DefaultBot.™.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Buddy.Coroutines.Coroutine.’”.Ž›.MoveNext() --- End of inner exception stack trace --- at Buddy.Coroutines.Coroutine.›(Boolean ›) at Buddy.Coroutines.Coroutine.Resume(Boolean ›) at Buddy.Coroutines.Coroutine.Resume() at Triton.Bot.Logic.Bots.DefaultBot.DefaultBot.Tick() at Triton.Bot.BotManager.Tick(IBot )
also the bot takes too long to play if you have many minions
it will calculate for 3-6 seconds, play and then repeat all over again resulting in losing your turn eventually
Please attach a full log, and we'll look into fixing the SF issue.
The current issues with speed of play are known and are being worked on as well. It's a bit tricky though, but as long as it's working, we can improve it, we just need to get to that point of things fully working (even if it's not that good to start).
73 and 75 (i skiped 74) crash very often. i use 72, and that play 25-30 games and then crash.
75 now was crashed on second turn of first game. 73 was about the same.
73 has new function - skip ranked after win. But i uncheck this option, and play unranked constructed. but problem is. So may this option in HSB code have a bug?
Please post a full log from any session that crashed. So far, there are no known crash issues.
If you're having an issue with concede, please post that log too. I've tested that logic and it's working as I expect, so if you don't think it's working I'll need a log.
It's *only* for ranked play, and it keeps track of the next ranked game to concede. Ii you mean you:
1. played ranked game and won with option on,
2. turned option off, played constructed game,
3. played ranked game and it conceded,
That is intended since you wanted to concede your next ranked game, whenever you next played it. The bot keeps track of that so you don't lose your rank. Once again, please attach a full log and I'll double check it.

The decision-making with some of the new GvG cards isn't optimal.
For example, I was watching the bot play as mage (using a mech deck).
The opponent had a bunch of 1/1 creatures on the board. I had a snow chugger and a goblin blastmage in my hand.
It ended up playing the blastmage,THEN the snow chugger (losing me the game).
The SF AI is not tuned for GvG yet, as only support for the cards has been added. It'll be a lengthy process updating everything to work more fine tuned like the old SF did before GvG, but please keep in mind that GvG is still brand new, and trying to "optinally" play all cards in relation to everything else is no easy task.
10 games played with version #75 and 5/5 stats.
Seen nice, no crash yet
Good to hear, thanks for the feedback, it does help.
