KamoCRM

Eliminate hexhead spawn overlap by computing unique column positions

Fixkamo-internal
Ya
11 Machi 2026, 19:34 UTC
Mwandishi
kamo
Ahadi ya
0e781cf

Each head now initialises its MotionValue at its own home-row column X and below the viewport (h + SIZE), then springs up to its final slot. Previously all heads shared (spawnX, spawnY) as the initial position, causing every head to visually stack on top of each other during the fly-in animation before flyToHomeRow could redistribute them. Also guards finishSpawn against duplicate-add if a remove event arrives while the avatar fetch is in flight.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei