Property BotHero
- Namespace
- GrindFest
- Assembly
- GrindFest.dll
BotHero
Current hero's AutomaticHero (bot API — same methods players use in bot scripts).
protected AutomaticHero BotHero { get; }Property Value
Remarks
Reading this where the bot cannot exist throws DevTestSkipException instead of returning null, so the test is recorded as skipped rather than failing with a NullReferenceException inside its own lambda. Measured 2026-09-20 in a WebGL player: 60 of a run's failures were this one null - the bot is produced by compiling its script at runtime, and an ahead-of-time build has no JIT to load it with.
Only the impossible case skips. Where the compiler does exist but no bot is attached yet (a compile still in flight, say) the old behaviour is kept and null is returned, because that is a real problem and swallowing it would hide it.