Portalith

Portalith is a third-person, single-player survival farming RPG that plunges you into the mystical world of portal mage elves. Explore a richly detailed realm, take on quests from local inhabitants, and overcome magical trials as you uncover the secrets of this enchanted universe.

Game Loop

The game's core loop revolves around exploring the world, collecting items, completing quests, defeating monsters, crafting new gear, leveling up, and growing crops.

Key Features

• Inventory System
• Farming System
• Stat System
• Interaction System
• Day & Night Dynamics
• Currency System
• EOS Login & Achievements
• SaveGame System
• Custom FSM AI
• Cheat Manager and Custom Asset Styles

Technical Insights

All major gameplay systems such as stats and inventory are developed as standalone plugins to ensure modularity and seamless integration into future projects. For core plugins, I prioritize writing the majority of the functionality in C++, exposing key elements to Blueprints so that designers and artists can easily make minor adjustments without touching the underlying code. To improve usability within the Unreal Editor, I take advantage of C++-specific features such as Custom Asset Definitions, Project Settings, and the Data Validator. Additional tools and techniques I use are documented in my Notion Knowledge Base to support efficient and scalable development. Tools such as the Asset Thumbnail Creator help streamline development workflows and reduce iteration time. To further accelerate development, I make extensive use of tools like the Gameplay Debugger, the Cheat Console, which many of my plugins benefit from as well as custom debug visualizations tailored to each system.

Coding Standards & Asset Naming Practices

All C++ code is written in accordance with Epic Games' Coding Standards, and assets are named following their recommended Asset Naming Conventions to maintain clarity and streamline collaboration.

Performance Optimization

• Texture sizes are adjusted to avoid unnecessarily filling up the StreamingTexturePool.
• Static lights are set to Stationary whenever possible, and their Attenuation Radius is kept as small as feasible to reduce performance overhead.
• Lumen Reflections are disabled, and Lumen settings are further optimized for performance.
• Packed Level Instances are used when applicable, as they allow for mesh instancing and better asset reuse across levels.
• I utilized Level Streaming Volumes to efficiently manage the loading and unloading of level segments.
• If ticking is required, SetTimerByEvent is used with a custom tick interval, ensuring the timer only ticks when necessary to minimize CPU usage.
• Soft Object/Class References are used where possible, keeping Size Maps small and enabling faster object loading.
• Where feasible, asset collisions are replaced with primitive shapes to reduce complexity and improve runtime efficiency.

Gallery

More images from the development environment with further insights into the project.