-
Notifications
You must be signed in to change notification settings - Fork 29
Other Managers
Managers available in knowledge are
Contains improved data from units
Unit cache
Handles and allows preventing duplicate actions especially when using real time.
Handles zone data and updates. Zones are areas where a townhall can be built and resources can be gathered.
Keeps track of enemy units.
Should probably be renamed to ability_manager, keeps track of what abilities are available for all units.
Solves optimal building positions.
Keeps track of our income and attempts to estimate enemy income.
Attempts to guess enemy build. If your bot detects a build, you can use step with a condition to formulate a counter.
Step(lambda k: k.build_detector.rush_build == EnemyRushBuild.RoachRush, your_counter_here)
Attempts to guess what units enemy might have, based on what they have now and how much income they have.
Keeps track of what units have been killed during the game.
Analyzes the state of game and tries to guess which side has advantage.
Functions to make chatting easier during the game. Easy usage is to use a key and use a function or lambda to generate text message
await self.knowledge.chat_manager.chat_taunt_once("key", lambda: "my chat message")
Keeps track of units in previous frame. Needed by other managers.
Allows writing data in order to optimize strategies in future games. You can announce your build to data_manager
to have it automatically record your results
self.knowledge.data_manager.set_build(build_name)
Remembers the last known enemy positions.
- Plans and Build Order
- Settings, debug and logging
- Structure and Life Cycle
- Unit Roles
- Unit Cache
- Running Games
- Converting Sharpy bot from before 2.0 version
- Converting Sharpy KnowledgeBot to SkeletonBot
- Converting Python bot to minimal Sharpy bot
- OLD: Extending Your Existing Bot With Sharpy
- Packaging For Ladders
- Extending Sharpy
- Advanced Build Order tricks
- Machine Learning With Sharpy