KamoCRM

Eliminate hexhead spawn overlap by computing unique column positions

Fixkamo-internal
تم شحنها
11 مارس 2026 في 7:34 م UTC
صاحب البلاغ
kamo
إرتكب
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.

جميع التغييرات

مثل ما ترى الشحن؟?

كلّه يصل إلى مكان عملك لوحده ابدأي بالخطه المجانيه و اقرأي هذه الصفحة مرة اخرى بعد شهر.

ابدأوا حراً للأبدخصخصة الفيو