Optimize NFT Game Performance
Budget: €3,000 – €5,000 EUR
I run a Unity-based crypto game that mints and trades NFTs directly from the client. Two issues are hurting player retention and revenue:
• Initial load time is far too long. Players abandon the splash screen before the lobby even appears. I suspect bloated asset bundles and un-streamed textures, but I need an expert audit and concrete fixes—Addressables, CDN configuration, compression, whatever will get players in fast.
• Blockchain payments occasionally fail. A user clicks “Buy”, gas is deducted, yet the transaction never finalises and no NFT is assigned. The failure seems to happen around the signing / callback cycle with our smart-contract gateway. I need rock-solid transaction handling and clear user feedback so we never lose a sale.
Deliverables
1. A profiled report pinpointing the current load-time bottlenecks plus implemented code and project-settings changes that cut the initial load to an acceptable target (we’ll agree the exact second count together).
2. A refactored payment flow that retries gracefully, confirms on-chain success, and reconciles item delivery or refund without leaving the player in limbo.
3. Brief hand-off notes outlining what was changed and how to keep things optimised going forward.
If you’re comfortable with Unity performance tooling, Addressables, async scene loading, ERC-721 / ERC-1155 interaction and Web3 wallets, I’d like to get started right away.
• Initial load time is far too long. Players abandon the splash screen before the lobby even appears. I suspect bloated asset bundles and un-streamed textures, but I need an expert audit and concrete fixes—Addressables, CDN configuration, compression, whatever will get players in fast.
• Blockchain payments occasionally fail. A user clicks “Buy”, gas is deducted, yet the transaction never finalises and no NFT is assigned. The failure seems to happen around the signing / callback cycle with our smart-contract gateway. I need rock-solid transaction handling and clear user feedback so we never lose a sale.
Deliverables
1. A profiled report pinpointing the current load-time bottlenecks plus implemented code and project-settings changes that cut the initial load to an acceptable target (we’ll agree the exact second count together).
2. A refactored payment flow that retries gracefully, confirms on-chain success, and reconciles item delivery or refund without leaving the player in limbo.
3. Brief hand-off notes outlining what was changed and how to keep things optimised going forward.
If you’re comfortable with Unity performance tooling, Addressables, async scene loading, ERC-721 / ERC-1155 interaction and Web3 wallets, I’d like to get started right away.