The mobile update will be rolled out gradually, with users randomly receiving it at different times. Depending on your settings, Struckd may update automatically once the new version becomes available.
We are happy to introduce exciting new racing assets! You can take a sneak peek at the gif below.
Please note that the new assets will be visible now, but you'll only be able to use them after updating Struckd to the newest version (2.115).
You will find 63 new racing assets, 3 new skins for your modular houses, and 3 new vehicles: a plane, a car, and a skate (each one of them with at least 2 different skins).
All the tracks from the racing assets have 2 skins as well: classic and futuristic.
Full list of new assets and skins|
Modular House Skins|
Street Racing Car|
Floor Finishing Line|
Slippery Oil Puddle|
Race Arch Checkpoint|
Wall Corner Ornament|
Repair Kit Pickup|
Sandbag Wall 3|
Surprise Box Pickup|
We have done some performance improvements by reducing the memory usage and physics impact for a smoother experience.
In addition to that, we've also implemented an adaptive performance package for Android devices. This should make your gaming experience more stable, while giving your battery a little extra life.
From now on, users will receive a notification if any rule breach is detected. In addition to that, necessary actions will be taken to ensure a fair and enjoyable gaming space for everyone.
A one-time "Try Struckd Studio" pop-up will be displayed the next time you open Struckd after the update.
We fixed an issue that was causing drafts with a large amount of assets to have extremely low FPS.
NPCs assigned to defend assets were wrongly attacking instead. We've resolved this issue, and now your NPCs will protect as intended.
We've fixed an issue where gates and doors were ignoring unlocking conditions.
There was an issue preventing proper interaction with the 'dirt path' asset. This issue has been fixed now.
We have addressed an issue where the premium item exchange UI was not updating, leading to the display of a red warning. This problem has been resolved.
Thanks for reading this new changelog. We can't wait to read all your feedback :)