Example custom server build. Management Process - choose a map - players - style - objectives - events - weather - time. All are customizable nodes containing individual node groups/associations - visual xml node trees. Could also reflect where .C files are called/interact. Chernarus Map Node; opened, reveals the xml network of sub nodes reflecting that aggregation - every static object and its coordinates - events - entities variables - spawn probability etc. Opening the node; display structure would reflect the most commonly edited variables for efficiency/convenience. Players Node; opens an editable network of game styles (PVP PVE ) - Presets - Each Avatars Default Load-outs - Customization's - heli pilot,infantry, hunter, scout, base builder etc represents team mission type/style - the player side might be greeted with limited vacancies as the roles are taken. Customization node; generically represents custom mods - coordinates - functions - event triggers Co loured Node Tree Groups could reflect the homogeneous relationship associations with other nodes also highlight requirements and deficiencies. Each Node is a separate/preset - entity which can be add to library for efficient server build. e.g weather, mission, players, map. Simply drag each preset node to their relative position on the node editor time line. Press Test < One could include surrogate AI Node for testing purposes - load out checks, event triggers etc