Proto Construction Pipeline

MapGroupProto Generator Pro

Generate MapGroupProto loot groups or proxy entries directly from init.c SpawnObject placement lines. This tool does not parse JSON ObjectSpawner formats.

Requires init.c SpawnObject lines Usage/category tagging Output preview

1) Generator Configuration

Operator Guide: MapGroupProto Generator Tap or click to collapse
Step 1: Set Structure + Type Choose structure name and output type (Proxy or Loot).
Step 2: Configure Loot Fields For Loot mode, set range/height and select usage/category tags.
Step 3: Paste SpawnObject Data Input valid SpawnObject lines from your build placement source.
Step 4: Generate + Export Generate output, review in preview pane, then copy or download.
  • Input source must be init.c style SpawnObject(...) lines, not JSON ObjectSpawner data.
  • First SpawnObject line is used as anchor in Loot mode.
  • Loot mode creates grouped point entries with tags.
  • Proxy mode creates direct proxy lines per SpawnObject object.
?

Example: Land_Shed_M1 or Custom_Base_Walls.

?

Choose Proxy for direct proxy output, or Loot for full grouped loot config.

?

One SpawnObject entry per line gives the most predictable output.

Input Requirement: init.c SpawnObject syntax only
Use lines like the valid example below. JSON arrays/objects from ObjectSpawner exports are not accepted by this parser.
Valid example:
SpawnObject("Land_Shed_M1", "7501.23 0 3310.92", "0 0 0");

Not supported:
{"type":"Land_Shed_M1","position":[7501.23,0,3310.92],"orientation":[0,0,0]}
Paste init.c SpawnObject lines, configure fields, then click Generate.
Mode: Proxy
Spawn lines: 0
Output: pending

For multi-select tags: hold Ctrl on Windows or Command on Mac while selecting options.

2) Code Preview

Input Preview SpawnObject 0 lines
Generated Output MapGroupProto XML 0 lines

How to use generated output

  • Proxy mode: use output as proxy-focused group entries for MapGroupProto workflows.
  • Loot mode: output includes usage/category tags and configured range/height values.
  • After generate, review preview first, then copy/download and merge into your target XML file.
  • If using custom usage/category names, ensure corresponding economy definitions exist server-side.