MaGek Postat Aprilie 7 Postat Aprilie 7 Among Us is a multiplayer social deduction game developed by the indie studio Innersloth. While it was released in 2018, it didn't achieve "viral" status until 2020. For a developer, it serves as a masterclass in how simple mechanics and cross-platform compatibility can outweigh high-end graphics. 1. Core Gameplay Mechanics The game is built on the Social Deduction model: The Objective: Crewmates must complete a list of "tasks" (mini-games) to maintain their ship. The Conflict: One or more "Impostors" are randomly assigned to sabotage the ship and eliminate crewmates without being caught. The Social Layer: The real game happens during the Emergency Meetings, where players use chat or voice to argue, deflect, and deduce who the killer is. 2. Technical Architecture & Programming From a Computer Science perspective, the game’s build is fascinating due to its efficiency. A. Game Engine: Unity The game was built using the Unity Engine. This choice was strategic because Unity’s C# scripting environment allows for rapid prototyping and, most importantly, seamless Cross-Platform Play between PC (Steam), Android, and iOS. B. Networking and State Synchronization Client-Server Model: Among Us uses a dedicated server model to handle game lobbies. The Challenges: When the game exploded in 2020, the original networking code (the "Netcode") wasn't designed for millions of concurrent users. The developers had to quickly optimize how "state" (player position, task progress, etc.) was broadcasted to prevent desync. RPCs (Remote Procedure Calls): The game uses RPCs to trigger events across all clients, such as when a body is reported or a sabotage starts. C. Game Design Logic (Finite State Machines) Each player’s state is managed through logic that dictates what they can do. For example: State: Alive (Can do tasks, can vote). State: Ghost (Can do tasks, move through walls, cannot vote). State: In-Meeting (Movement disabled, UI focused on voting). 3. The "Among Us 2" Cancellation & Technical Debt In 2020, Innersloth initially announced a sequel because the original code was "fragile" and difficult to update (a classic case of Technical Debt). However, they decided to cancel the sequel and instead "re-factor" the original code to support new features, showing how maintaining a legacy codebase is often more valuable than starting over if the user base is already there. 4. References and Sources If you are citing this for a college report or research, here are the primary sources: Innersloth Official Devlog: (Innersloth.com) – Provides insights into their transition from a small project to a massive infrastructure. Unity Technologies Case Studies: (Unity.com) – Often features Among Us as a prime example of successful mobile-to-PC porting. "How Among Us Deals with Cheaters" (Technical Articles): Look into Gamasutra/GameDeveloper.com for analyses on their server-side validation updates. Steam Database (SteamDB): For statistical data regarding player concurrency and technical growth. Sources https://www.innersloth.com/the-future-of-among-us/ https://www.google.com/search?q=https://unity.com/case-study/among-us 7 1 1
Postări Recomandate