Billz Help Desk

 Chain of Responsibility: JavaScript

This is a simple Chain of Responsibility (CoR) application. Each button represents a different request that the CoR will handle. In this case, the help is in the form of a 'Help Desk' and the CoR finds the appropriate response to the query.

How do I learn about design patterns for ActionScript 3.0
I'm making a game where states keep changing. What would be a good design pattern for dealing with changing states?
My app involves a lot of problem solving with different algorithms? What's a good pattern for dealing with multiple algorithms?
Whenever I create a new object with my Client object, I build up dependencies. Is there a pattern to avoid such dependencies?
What is a primary guiding design pattern principle?
I want to know the truth!

The CoR pattern works sequentially so that as it moves through the chain, you can see each rejected attempt to find the correct handler. (Normally, you wouldn't see those rejected handlers.) It is a very easy pattern to update and add additional handlers.