A multi-platform, modular, universal engine for embedding advanced AI in games.
Embed advanced AI and up your game.
Powerful development
Software should suit you. Grail does. You can change it, mix it, and it will continue doing its job.
- a formal approach to embedding AI in games
- faster development process
- no need to rewrite existing code.
- automated game testing and balancing
- independent modifications by approachable GUI tools
- Plugins for Unreal and Unity
Top-notch scientific approach
Grail’s AI is developed with care by brilliant researchers who bring the quality of academic knowledge to give you proven results.
- stronger AI in games
- scientific results into gamedev
- AI that is explainable and enjoyable
Non-expert ease of use
You shouldn’t have to get a PhD to use software. Grail gives you a clear GUI and extensive documentation for all your needs.
- non-experts make expert AI in a game
- AI without the cost of recruiting
- no maintaining a team of AI experts
-
The AI in Tactical Troops is running on Grail thoroughly. Tactical Troops is a squad-based tactical game with turn-based gameplay and continuous movement without a grid. It fits the frame of an ideal showcase of Artificial Intelligence. Bots need to tackle many challenges in real-time, e.g. choose their current objectives, reason in a dynamic environment, select the right weapon or gadget for the job, attack, take cover, support, etc.
Grail has allowed us to develop AI in Tactical Troops in a modular fashion using two of its three main algorithms. On the top-most level, there is a strategic AI operated by Grail's Utility System. The strategic component sets orders for units e.g. where to go, who to cover or attack. The orders are passed to the tactical AI, which is implemented using Grail's simulation-based methods. The tactical AI plans each turn within certain constraints set by the strategic layer. Both strategic and tactical components operate with their own set of behaviors. They interact with the environment as well as with each other using the blackboard architecture. Publication 2021-04-15 by QED Games.
-
First prototypes of Grail's algorithms were used in Ancestors Legacy, a real-time strategy game by Destructive Creations. For this project, we developed a bot for online multiplayer games, capable of controlling up to five players at once. The approach used in Ancestors was based on a multi-agent system, using utility-based AI to perform various tasks, such as attack target selection on strategic and tactical levels or determining the right build order. The ideas and experiences gathered during our collaboration served as a cornerstone for the techniques used in the final version of the framework.
Frequently asked questions
-
Yes. It can be achieved either by substituting reasoners for more/less detailed ones or it is possible to change data on entity's blackboard to make it consider more/less relevant data.
-
Somewhat. That would require wrapping Behavior Tree execution in Grail Behavior. Then it could be provided to reasoners or manually assigned by user.
-
Yes, all that needs to be done is to make animation system accessible from given Grail AI Entity (i.e. push it on entity's blackboard). Then behavior can interact with animation system in all its methods. For example behavior can be prolonged for animation duration, or when behavior is starting it's execution it can cause animation to be played. If animation is more complication and consisting of few phases behaviors can be connected into a sequence, where each one of them will manage one phase of animation.
-
When constructing AI Manager user can provide number of worker threads which will iterate over registered entities, updating them simultaneously. If user chooses not to do so, all operations on this manager will be done synchronously.
-
Depends on how complicated you need it to be. Simple AI reasoners will not need much memory, but advanced game simulations will cerainly need more.
-
Yes. All you need to do is to tweak their reasoners.
-
It is, you just need to take mobile limitations into consideration while designing Grail reasoners.
-
Yes, grail behaviors are terminated mainly in 3 situations: 1. behavior sucessfully finished 2. behavior is no longer legal and there is no way to continue its execution 3. behavior is overriden with another one, either manually or because reasoner thought that another behavior is more suitable to current situation.
-
We provide plugins for Unity and Unreal Engine 4, which means that in those engines Grail should work out of the box. Hovewer Grail should work with most of the available game engines as long as they can be scripted in either C++ or C# and can include external libraries.
-
C++ and C#.
For price estimates or other questions, feel free to call and email us!
-
Piotr Biczyk
[email protected] +48 510 106 648