What problem does it solve? Building NetEase Minecraft UIs requires coordinating JSON UI files with Python backend logic through hash-derived binding names, and mistakes in paths, decorators, or escaping cause silent UI failures that are hard to debug. ## Core Features & Use Cases - JSON UI Authoring: Rules for text escaping (%% for percent, \n for newlines), clip_ratio progress bars, dynamic texture binding via binding_name_override, and button bindings through $pressed_button_name. - Declarative Binding Backend: ScreenNodeWrapper pages with nested Bindable classes using @bindString, @bindFloat, @onButtonUp, @toggle, @editBox, @slider, and @collection decorators driven by centralized UIPath constants. - Binding Name Stability: Hash names derived from md5(path + type tag), with the gen_bindable_map.py tool to detect drift when paths change. - Use Case: When adding a settings page with a toggle, slider, and input box, declare UIPath constants, write the Bindable class with composite decorators, wire the JSON bindings, and regenerate the bindable map to verify hashes. ## Quick Start Ask the assistant to create a new NetEase Minecraft UI page with a close button and a progress bar using the NekansLibs binding decorators.