Battleground Game Framework
Battleground Framework
$15.00
(no ratings)
|
Date |
Price |
|---|---|
|
日期和时间 |
价钱($) |
|
03/19(2018) |
15.0 |
|
11/08(2024) |
15.0 |
Jump AssetStore
ON SALE! (Reg Price: $35+)
Make your battlefields COME ALIVE with our complete action game framework!
Inspired by the epic battles of popular open-field war games, our kit empowers you to create the large scale battles you've always dreamed of!
* This is in Beta Early Release / Beta Pricing*
Third Person Battle |
Spectator Battle |
Online Manual | FAQ
Features:
-Third Person Controller (C# source commented)
-Mechanim-Powered Animations
-Intermediate-Level Open-World A.I.
-A.I. Can Attack / Chase / Wander
-A.I. Waypointing w/ Obstacle Avoidance
-3 A.I Types: Soldier / Vehicle / Hovercraft
-Tank A.I. w/ Rotating Turrets
-2 Opposing Teams Using Unity Tags
-Weapon System w/ Splash Damage
-Call in Orbital Strikes (Artillery)
-Weapon Inventory System
-Object Pool System
-Spawn System
-Easily swap sounds & special fx
-Core Features Editable in Unity Editor (no coding)
-Commented C# Source Code
-Expandable w/ Our Additional Addons
-Includes an intense battle scene
-Bonus terrain & battlefield environment
PRE-SALE NOTES
(Read Before Buying!)
-Warning: Not for Absolute Beginners!
-Core functionality does not require coding - only use the Editor
-Full customization requires intermediate C# skills
-Desktop & Console focus
-Mobile: Only very high-end devices supported at this time
-The A.I. does not have pathfinding / NavMesh support
-A.I. has an open-world focus & not recommended for heavy indoor environments
-Plenty of commented C# code, but core functionality is precompiled DLL
-Public functions & variables allow for easy scripting
-If you have no programming exp, please learn some basic concepts first!
-We love to provide tech support, but will not teach you how to code :)
Installation Instructions:
Import into blank project & examine files to make sure there are no conflicts with your existing project. Otherwise, your files might get overwritten.
We took care & developed the code in its own namespace, so there should be no conflicts, but you should still install into a blank project first.
