Q:

Java design pattern for handling configuration options and responding to changes in them

I'm working on an overlay/HUD for a Java game, where the user should be able to enable or disable certain components and choose configuration options. One such example is a health bar, which the user can choose to either enable or disable and choose its size and color. 
What would be a good design to handle this kind of scenario in Java? I'm particularly wondering how I should handle changes in configuration options, so that all HUD components could follow the same logic.

A:

The usual way to propagate change is through the Observer pattern.
The HUD components register themselves as observers of the object holding the HUD configuration options.
The object holding the HUD configuration options notifies the HUD components of any change to its parameters.

