Hey stranger, here's a quick follow-up blog update.

to reduce download size and bandwidth costs—for both the user and the developer. That means you and me. If you’ve got time, I’ve started publishing this online and sharing it more widely. You can visit the site, explore the game, and maybe discover a story that you, your friends, or even your neighbors might enjoy.

This isn’t a fictional story—it’s about the real process behind the daily grind. I’d call it “the process behind success,” but I’m not using the word “success” just yet. We’re still in the middle of it. Like I said, this is a challenge.

There are only two outcomes: success or failure. So I’ll call it “the process behind success or failure”—whichever way it goes 😄

It’s up to me to handle this task I’ve given myself. It’s a challenge to use my ideas and skills to exist and grow in this world. One of the biggest goals right now is learning how to promote this project personally. That’s a skill I’m still building—promotion involves speaking, emotion, and strategy.

I need to learn how to handle rejection, and also how not to get overwhelmed when things go well. Whether I win or lose, emotions play a big role—they shape behavior. So I’m learning to manage that while also improving how I speak and share my story. That’s why I’m writing this blog. Promotion is all about storytelling.

If I get better at telling my story, people might spend time reading or engaging with it. And once they do, there’s a better chance they’ll be open to what I’m offering. That’s one principle I’ve learned about negotiation.

Why am I sharing this here? Because maybe you’ve got a project too—something where negotiation skills could help. This is just one of many things I’m learning about that.

Anyway, back to the technical side—I’ve optimized three 3D files that I’ll be importing into my Three.js game website. You’ll see in the screenshots that they’re the same file, just with different sizes. The original was pretty heavy, so I compressed it to reduce the size and lower bandwidth costs on my end. I used multiple compression steps to get there, and it worked.

This helps both users and developers—better runtime performance and faster asset downloads. I still have more to apply to keep costs low, especially for asset-heavy materials I’ll be integrating into the web app.

I’m sharing this for anyone who’s thinking of building their own web-based game or integrating assets into a site. Optimizing file size is a great way to reduce bandwidth and improve the download experience.

That’s it for now. I’ll post another update soon, mostly about the 3D process. It’s one of the most expensive parts of asset integration, so knowing how to handle it is super useful. If not, there are plenty of free and paid assets online. But in my case, I’m building fully custom assets for my game.

Alright, that’s all for today. Catch you again soon, stranger.

Bye!