Native support for game engine binary file parsing (Unity, Unreal, Godot, RPG Maker, GameMaker)

BUSINESS USE CASE: I am building "Gamelocalizer", a professional localization tool for video game developers built on Base44. The app needs to extract translatable strings from game engine files to enable translation workflows. THE PROBLEM: Base44 currently cannot parse binary/proprietary file formats used by major game engines. This makes it impossible to build a complete game localization tool on the platform. REQUIRED FORMATS: Unreal Engine: - .uasset, .umap (binary assets) - .locres, .locmeta (localization files) - .ini (text configs - partially supported) - .uplugin, .ush/.usf (text - partially supported) Unity: - .assets / .sharedassets (binary) - .resource, .bundle (binary) - .asset, .uxml (mixed) Godot: - .pck / .zip (packages) - .tscn / .scn, .tres / .res (scenes/resources) - .gd (scripts - text based) - .mo (gettext) RPG Maker MV/MZ/XP: - .json (text - supported) - .woff, .ttf (fonts) GameMaker: - TXTR, STRG, FONT (custom runtime formats) Other: - .xmb / .xml (text - partially supported) - .swf / .gfx (Flash/Scaleform) - .pdt / .pdr REQUESTED FEATURES: 1. NPM package support for binary file parsing in backend functions 2. Native integration with UnityPy, UAssetAPI, or similar parsing libraries 3. File decompression support (.pck, .zip) 4. Binary-to-JSON conversion pipeline for proprietary formats 5. Official SDK integrations where available (Unreal Localization API, Unity Editor API) MARKET POTENTIAL: The video game localization market is worth $1.5B+ and growing. No no-code platform currently supports this workflow. This would make Base44 the ONLY no-code platform capable of building professional game localization tools. PRIORITY FORMATS (minimum viable): 1. .locres / .locmeta (Unreal) - most requested by localizers 2. Unity .assets / .bundle - largest market share engine 3. Godot .pck - fastest growing open source engine 4. GameMaker STRG - popular indie engine