Stylized Axe Low poly

Enhance your game projects with this meticulously crafted stylized axe! Featuring a pendant made of teeth, held together by a rugged rope, this axe brings a fierce and primal aesthetic to your scenes. A unique hole at the base of the handle adds character and a distinctive silhouette, perfect for fantasy, adventure, or survival-themed environments. Optimized for games, this low-poly asset is ready to be integrated into your real-time projects, offering both high detail and performance. Fully customizable and game-ready!

Good topology for editing.

Technical descriptions:

Materials:4

Polycount:25826

Vertex Count:12913

Note: this is because this asset comes with some additional features like the horn,rope,ring

------------------------------------

REFUND POLICY

All sales are generally **non-refundable**. The asset is provided as “what you see is what you get,” 

and the product page accurately represents the contents through previews, descriptions, and examples.

Refunds will NOT be granted for the following reasons:

• Lack of knowledge on how to import, connect, or configure textures or materials in game engines 

  or 3D software.

• Misunderstanding of how PBR workflows, texture maps, or nodes work.

• User inexperience leading to incorrect setup, errors, or unexpected results.

It is expected that the customer has the basic technical knowledge required to use standard PBR 

textures, file structures, and material workflows. The folder organization and texture naming inside 

the asset are self-explanatory for users familiar with industry-standard practices.

Refunds may only be considered if:

• The files are corrupted,  

• Missing critical content

Any refund consideration remains entirely at the discretion of the seller.

--------------------------------------------------------

Copyright © [2005] [Nachovsky].  

All rights reserved — this license grants only the permissions described below.

By downloading, installing, or otherwise using these asset files (“Assets”), you (“Licensee”) agree to the following license terms:

### 1. License Grant  

a) Licensor grants Licensee a non-exclusive, worldwide, perpetual, royalty-free license to use, modify, and incorporate the Assets (or any modified version thereof) into digital media, interactive applications or games (“Final Products”).  

b) Licensee may distribute, sell or otherwise commercially publish Final Products that include or embed the Assets (or modified versions) as part of the Final Product.  

### 2. Prohibited Uses / Restrictions  

a) Licensee may **not** re-sell, redistribute, sub-license or otherwise make the Assets (or modified versions) available as standalone files, asset packs, templates, or libraries — for sale or for free.  

b) Licensee may **not** share, upload or otherwise distribute the Assets in source file form (or modified source files) such that third parties obtain the raw asset files.  

c) The Assets must be embedded or compiled into the Final Product in a way that they are not easily extractable as standalone assets.  

d) Licensee may not claim copyright or authorship of the original Assets (or modified versions) — only their own contributions.  

### 3. Attribution (Optional)  

Credit to the original author is **not required**, but appreciated. If you choose to credit, a typical credit format is:  

“Some assets in this product © [Nachovsky], used under license.”  

### 4. Warranty & Liability  

The Assets are provided “as-is,” without any warranties. Licensor is not liable for any damages resulting from the use of the Assets.  

### 5. Acceptance  

Using or distributing any Final Product that includes the Assets constitutes acceptance of this License.  

---------------------------------------------

USAGE GUIDE

The asset has blend files, and exported in a lot of common formats for game engines inclusion.  Textures for the game engines are divided in folders and it's pretty self explanatory what the channels do

It is expected that the user knows how to connect PBR maps in any engine or 3d software

Ao channel is recommended to be multiplied by the base color to give the effect i intended in the asset (user might tune it how it wants)

Since my project has many texture maps there wasn't an easy way to automate the node connections of the textures (Ao map,Base color,roughness,metallic,Normal map) will have to connect in your intended workingspace.

In case of unreal and unity try using the FBX file for importing the model, it's possible you need to manually connect the textures in the intended game engine. Materials should be created in the engine (if case it's not, you can contact me). In case of UE5 disable virtual shadows to avoid getting graphical glitches on the object.