Placement Proxy Pipeline
Init.c Proxy Converter Pro
Convert SpawnObject placement lines into MapGroupPos, MapGroupProto, and types.xml snippets in one workflow. Built for faster map content pipeline updates with cleaner copy/export handling.
MapGroupPos output
MapGroupProto output
Types.xml entries
1) Conversion Setup
Operator Guide: Proxy Converter Tap or click to collapse
Step 1: Configure Names
Set group, usage, and category names for output tags.
Step 2: Paste SpawnObject Data
Input one or more SpawnObject lines from init.c data.
Step 3: Convert
Generate MapGroupPos, MapGroupProto, and Types entries together.
Step 4: Copy or Download
Use section-level copy/export to move outputs into your files.
- Custom usage/category values require matching limitsdefinitions.xml entries.
- Malformed lines may produce empty or partial output rows.
- All processing is client-side in browser only.
?
Example: BaseWalls_NWAF creates BaseWalls_NWAF_0, BaseWalls_NWAF_1, etc.
?
Leave blank to use Wall.
?
Leave blank to use wall.
?
Required Input Format
Use init.c placement lines only. Each row should be a SpawnObject call with type, position, and orientation values.
Valid:
SpawnObject("Land_Wall_Gate_F", "7523.12 0.00 3338.90", "0.00 90.00 0.00");
Not supported here:
{"type":"Land_Wall_Gate_F","position":[7523.12,0,3338.90],"orientation":[0,90,0]}
Paste SpawnObject data and click Convert.
2) Output Previews
MapGroupPos Output XML
0 lines
MapGroupProto Output XML
0 lines
Types.xml Output XML
0 lines
What each output is for
- MapGroupPos: world placement coordinates for each generated group node.
- MapGroupProto: usage/category and proxy dispatch metadata for those group nodes.
- Types.xml: economy type entries for object classes referenced in input rows.
- Typical workflow: convert, copy each block, then merge into mapgrouppos.xml, mapgroupproto.xml, and types.xml.