Shared Link | Sunday, August 4, 2019

Achievement Design 101

Achievement Design 101 Link preview image

A guide about how to stop putting terrible achievements in games.

Site iconGame Developer — December 2, 2009

It’s nearly ten years old, but this fourteen-point guide by Greg McClanahan of Kongregate is still by far the best resource I’ve ever seen for learning how to design good achievements and avoid common pitfalls. I still say it should be required reading for anyone designing achievements.

Tags: Shared Link, TOPIC: Achievements

⇐ PREVIOUS LINK: The time I tried to ruin Halo 2 ⇒ NEXT LINK: Habitat Chronicles: The Untold History of Toontown's SpeedChat (or BlockChat(tm) from Disney finally arrives)

Search Pixel Poppers

About/FAQ

First time here? Lost or confused? Got any questions? Start here!

Related Content

  • [SHARED LINK] Emotional Context In Decision Design
  • [SHARED LINK] What Breath Of The Wild Is Like For Someone Who Doesn't Play Games
  • [SHARED LINK] "Winning and measuring engagement is no longer enough"
  • [SHARED LINK] When Theme and Mechanics Collide
  • [SHARED LINK] Two Hat: Stop tweaking your game and start fixing your community

Top Tags

  • Review (357)
  • Thought (333)
  • Shared Link (132)
  • TOPIC: Consumer Experience (77)
  • Article (61)
  • TOPIC: Difficulty (56)
  • Video (49)
  • PLAYLIST: CAPSULE REVIEWS (39)
  • TOPIC: Storytelling (34)
  • GAME: Animal Crossing: New Horizons (27)
  • TOPIC: Marketing (24)
  • TOPIC: Preservation (20)
  • TOPIC: Authorial Intent (19)
  • TOPIC: Psychology (19)
  • GAME: Dragon Quest Builders 2 (14)
  • TOPIC: Completionism (13)
  • TOPIC: Player Choice (13)
  • TOPIC: Learning (12)
  • GAME: Bubsy: Paws on Fire! (10)
  • GAME: World of Warcraft (10)
All Tags

Newest Posts

  • [ANNOUNCEMENT] Dan Yums
  • [THOUGHT] My Top Games of 2024
  • [THOUGHT] The Platform is the Playstyle: Going the Distance
  • [REVIEW] Cat Quest III
  • [REVIEW] Dungeons of Hinterberg
All Posts

© 2025 Pixel Poppers. All rights reserved. Site powered by Hugo. Comments powered by HashOver. Search powered by Lunr.