Required stack
필요 기술
GodotUnityC#GDScriptREST APIUI/UX DesignGame DevelopmentGitWindows BuildNetwork Programming
Project brief
프로젝트 내용
Our desktop slot game has just reached alpha, and I need an experienced Godot or Unity developer to keep the momentum going. The core reels and pay-table logic are already in place; the immediate focus is polishing the user interface and wiring the client to our backend services so we can start live balance updates, authentication, and session tracking.
Here’s what I’m aiming for over the next few sprints:
• Rebuild the lobby and in-game HUD so they scale cleanly on common desktop resolutions (Full HD and 1440p are top priority).
• Implement smooth transitions, button states, win animations, and sound hooks that match the existing art and audio assets.
• Integrate REST endpoints for login, balance fetch, spin requests, and result callbacks. The backend is ready; I’ll provide Swagger docs and test tokens.
• Add basic error handling and reconnection logic so the game fails gracefully when the network drops.
• Final step: package a signed build for Windows (Mac optional but welcome) and hand over well-commented source in Git.
Acceptance criteria will be a playable desktop build that passes a short QA checklist covering UI responsiveness, correct balance updates, and stability through 1000 automated spins.
If you’re comfortable jumping into an alpha-stage codebase, writing clean C# (Unity) or GDScript (Godot), and pushing frequent Git commits, let’s talk.
Here’s what I’m aiming for over the next few sprints:
• Rebuild the lobby and in-game HUD so they scale cleanly on common desktop resolutions (Full HD and 1440p are top priority).
• Implement smooth transitions, button states, win animations, and sound hooks that match the existing art and audio assets.
• Integrate REST endpoints for login, balance fetch, spin requests, and result callbacks. The backend is ready; I’ll provide Swagger docs and test tokens.
• Add basic error handling and reconnection logic so the game fails gracefully when the network drops.
• Final step: package a signed build for Windows (Mac optional but welcome) and hand over well-commented source in Git.
Acceptance criteria will be a playable desktop build that passes a short QA checklist covering UI responsiveness, correct balance updates, and stability through 1000 automated spins.
If you’re comfortable jumping into an alpha-stage codebase, writing clean C# (Unity) or GDScript (Godot), and pushing frequent Git commits, let’s talk.