René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Transform ObjectEditingOutput to proper Standard Library Usage","articleBody":"So currently when parsing a map, all the object data is output into the `objectEditingOutput` folder in the `_build` directory. This is nice, however the output is in a very raw format, example for a custom ability based on the \"slow\" ability:\n\n```\n@compiletime function create_w3a_A01M()\n\tlet def = createObjectDefinition(\"w3a\", 'A01M', 'Aslo')\n\t..setLvlDataString(\"abuf\", 1, 0, \"B01P\")\n\t..setLvlDataUnreal(\"acdn\", 1, 0, 10.0)\n\t..setLvlDataInt(\"amcs\", 1, 0, 25)\n\t..setLvlDataUnreal(\"Slo1\", 1, 1, 0.3)\n\t..setLvlDataUnreal(\"Slo2\", 1, 2, 0.3)\n\t..setLvlDataUnreal(\"adur\", 1, 0, 35.0)\n\t..setLvlDataUnreal(\"ahdu\", 1, 0, 8.75)\n\t..setLvlDataUnreal(\"aran\", 1, 0, 800.0)\n```\n\nIn the standard library, there exists a wrapper for this class https://github.com/wurstscript/WurstStdlib2/blob/master/wurst/objediting/AbilityObjEditing.wurst\nindentified by the 'Aslo' base ability being used. It would be very nice if the output would make use of these standard library classes to produce more useful output instead of this raw format.\n","author":{"url":"https://github.com/Frotty","@type":"Person","name":"Frotty"},"datePublished":"2025-06-25T08:20:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1092/WurstScript/issues/1092"}