Asset Store
Documentation
What is the BulletHell Elemental Template: The BulletHell Elemental Template is inspired by the Swarm mode from League of Legends. Players start with a relatively weak character and progress through increasingly challenging stages. As the difficulty ramps up, players can upgrade their character by enhancing stats.
The template also incorporates elements of RogueLike gameplay, where players can collect cards that boost stats or unlock automatic abilities to help overcome challenges. Players can strategically build their character, as certain abilities can only be upgraded through specific card combinations.
This versatile template allows developers to create fast-paced, action-packed games with endless replayability, where strategy and skill are key to progression.
What systems does the Template have: The BulletHell Elemental Template comes equipped with a wide range of essential systems, including Firebase-based authentication and player data storage, a robust character selection feature, in-game shops, and a beta version of an IAP shop. It also includes a currency system, common and daily quests, a Battle Pass, ranking system, player icons and frames, nickname change functionality, and a dynamic combat system.
For more details on each system, be sure to check out the Asset Store page or the provided documentation.
Game Modes: The BulletHell Elemental Template currently features three distinct game modes:
Survival Time: Players must survive for a set period to complete the map, facing waves of enemies until the timer runs out.
Kill Boss: A boss spawns after a defined wave, and players must defeat the boss to complete the map. Time is not a factor in this mode.
Survival Time + Kill Boss: The ultimate challenge, where players must survive until the timer expires, all while battling waves of mobs. Once time runs out, a boss spawns, and players must defeat it to finish the stage.
Each mode offers a unique challenge, catering to different playstyles and levels of difficulty.
“Will the package receive updates?”
Yes! I plan to continuously update this template with new systems based on developer feedback and needs, as long as they align with the template’s vision.
Additionally, I’ll provide system improvements and bug fixes when necessary to ensure the template remains up-to-date and efficient.
About using Firebase as a backend: Pros and advantages
The template uses a streamlined system designed for ease of use, agility, and cost efficiency—often at zero cost—by leveraging Firebase. Data is loaded from the database and stored locally for UI updates and basic queries, minimizing the number of requests to the database. This approach helps stay within Firebase’s free tier limits. Player data is only updated in the database during key events like purchases, game completions, or reward claims, ensuring an optimized flow.
Advantages:
- Developer-friendly with simplified setup
- Low or no server costs
- Easy maintenance and updates for your live games
- Comprehensive backend handling authentication and player data
- Simple management of Battle Pass seasons
Future Update: Optional Server-Side Logic with Cloud Functions
I plan to release a future update that will introduce the option to shift the logic completely to the server side using Firebase Cloud Functions. This update will be free for all current buyers of the template. However, developers who choose to implement this feature will need to upgrade their Firebase plan, as Cloud Functions require a paid plan. Additionally, server costs will increase significantly with this approach, but it will offer enhanced security against malicious players trying to alter game data.
Firebase Considerations:
The specific considerations below refer to the Firebase SDK and not the Template which just uses it as a tool.
- Initial Setup Requirements: The Firebase SDK requires specific configurations before your project can successfully connect to the database. However, the documentation includes a complete step-by-step guide, and there is also a video tutorial available on the Asset Store page, walking you through the process from start to finish.
- External Dependency Issues: The Google External Dependency Manager (installed automatically) can sometimes cause errors, especially if the Android or iOS modules are not properly installed. These build errors can be tricky to resolve, but I’ve identified and filtered the most common issues in the documentation, along with a list of potential solutions.
Note: Around 80% of build errors are typically caused by selecting an Android version lower than the minimum required by the Firebase SDK in the Build Settings menu.
