Hey! Here's a quick update on the behind-the-scenes from this past week:

1. Code Refactoring:

• Tackling Inefficiency: I've been fine-tuning my code, focusing on the way I handle game items like weapons, armor, and more. Previously, I used a combination of Structs and Data Tables to store item details (like name, meshes, and stats). However, this method was proving to be a bit like trying to herd cats - unpredictable and time-consuming.

• Blueprints & Structs: These tools, although great, were causing some headaches. Blueprint Structs, when paired with Data Tables, had a tendency to be unstable, throwing unexpected errors and often requiring manual refreshes.

• Efficiency Issues: Additionally, my method for retrieving item data from these tables wasn't exactly lightning-fast. Imagine having to check every single item in a long list to find the one you want – not ideal, especially as the game world grows richer with more items.

2. Switching to Data Assets:

• Why Data Assets?: To streamline things, I've shifted to using Data Assets. These are more stable and efficient, kind of like giving each item its own ID card that never gets lost or mixed up. This means fewer errors, less manual fixing, and a direct, no-nonsense way for my game to access item information.

3. Code Cleanup:

Blueprints Overhaul: I've also been organizing the Blueprints. What was once a chaotic mess...

...is now a better mess, easier to understand and work with.

4. Adapting to the New Data Asset System: Inventory Revamp

• Character Inventory Malfunction: The switch to Data Assets initially left our characters in a bit of a Adanic state (read: without armor). But don't worry, they're all geared up again.

• Inventory System Tweaks: The inventory code got some love too, making it more robust. Let's just say I've been testing it with an absurd amount of apples.

That's the wrap for this week! As always, thanks for being a part of this journey. Your support fuels my quest to make an incredible game. Stay tuned for more updates.