Algoryte

Complete services of #Games |#GameArt #Web3Games | #Blockchain | #VR | #XR —— building @hamieverse and @polker_PKR

[Algoryte @algoryte]

The joy of an indie studio crafting animated movie-ready assets is unmatched 🤩

We rarely talk about what we’re creating at Algoryte, and it's time to change that! Here’s an exclusive look at our in-house sci-fi character, built from raw 3D mesh to texturing and final render.

More drops coming from the design lab soon. Rate this bot 1–10 👇

[3D] [IndieDev] [Algoryte] [GameArt]

[Algoryte @algoryte]

https://t.co/JSQV47eOwe

[Algoryte @algoryte]

Don't want to wait for the rest of the series? The complete Hamieverse case study is live now →
https://t.co/KCs43UdKRy

[Algoryte @algoryte]

#DevLogs Pt.4
Hamieverse's leaderboard started as a single, all-time table, reading straight from the database.
Simple, sure.
But loading every player's history at once gets expensive super fast. 🧵 (1/8)

[Algoryte @algoryte]

One schema, built once, reused when it mattered. Next in this thread series: how missions became data instead of code. (7/8)

[Algoryte @algoryte]

The storage strategy changes underneath. The callers never do. Next in this thread series: the leaderboard schema we only had to build once. (7/7)

[Algoryte @algoryte]

By the time Hamieverse reached Beta, its database had already changed shape twice. No player ever noticed. 🧵(1/7)

[Algoryte @algoryte]

None of these swaps touched the layers above them. Prisma acts as a secure pipeline, triggering stored procedures behind a stable interface. (6/7)

[The Hamieverse @hamieverse]

Buffs and debuffs should be readable the moment they hit the board.

We’re testing card status animations for the Hamieverse TCG.

Power up.
Weaken.
React.
Adapt.

Every status change needs to be clear at a glance.

Does the feedback read clean?

[Algoryte @algoryte]

https://t.co/54tN3movRe

[Algoryte @algoryte]

Beta was built entirely on top of this decoupled foundation.
To read the full case, click the link
→ https://t.co/LxxIptZfdh

Next in this thread series: how the backend and database evolved alongside it.

[Algoryte @algoryte]

For @hamieverse 's Pre-Alpha and Alpha, we made a deliberate call: link the UI directly to the game logic, no abstraction layer between them. 🧵 (1/9)

[Algoryte @algoryte]

→ Unity Addressables moved the heaviest assets to cloud storage, keeping the initial download light as the card catalog grew. (8/9)