Skip to content
Gehrman Dante edited this page Dec 7, 2020 · 5 revisions


This project’s wiki contains all the information required to use the Low Poly Shooter Pack, alongside cool tips and tricks and lots of other useful content for developers looking to make their games even better.

From here, you can find all the interesting sections in the sidebar at the right-hand side of the screen.

Note: This wiki is constantly being updated and improved. If you can’t find something you’re looking for here, you can Contact Us.


The purpose behind having all this content in a wiki is to allow us to iterate quickly on it and have a unified place where all the information on the asset can be found.

Developers currently working on projects using the Low Poly Shooter Pack can come here and get information on any of the features the asset offers. That way using the pack as the basis for a game can be made easier by virtue of having it all nicely documented.

Style Guide

A style guide is a set of standards for the writing, formatting and design of documents or projects.

We find it very important to adhere to some sort of standard, and thus we decided that we would need a proper style guide for our project, to help in guiding our decisions and keep us on track when updating the asset.

For this purpose, we decided to “write” a style guide to use. And write we did, or at least we wrote some parts of it, most of it comes from Michael Allar’s Github page, where one of the best Unreal Engine 4 project style guides can be found.

As we previously mentioned, our does not differ radically from the aforementioned one, so if you’re familiar with the style guide, you’ll be right at home navigating the Low Poly Shooter Pack.

Why is the style guide public?

We made it public so developers could understand why we structured the project the way we did and thus be able to more easily navigate and use it to its fullest extent.


The documentation side of the wiki covers everything there is to know about the project, from how everything works, to why it works the way it does. We strive to constantly improved our imperfect documentation and sincerely hope that it helps developers both make splendid games and learn from our mistakes.