LobbyFacade has now been split into a common Facade (which will be used to setup logging currently and eventually message queues), log4j2 is now used for logging - the configuration file is XML based and is generated by the distribution module. It will be the same for both lobby and realm. Individual facades can have their own logger configuration or default back to either lobby or default configurations as needed. This fallback structure will probably need some standardised robustness as I probably haven't utilised log4j2 to its full configurable potential. For now though it will log and fallback correctly if a certain logger isn't present. It should be noted that the configuration file is referenced from a System.setProperty call rather than bundled with the jar