v1.1.20
v1.1.20
Fixes an editor crash when building Niagara systems from a spec, and lets feedback be filed without an executed python workaround.
Bug fixes
-
Niagara system/emitter creation no longer crashes the editor.
create_niagara_system_from_spec(andcreate_niagara_emitter) built their assets with a bare object allocation, leaving the emitter without a graph source and the system without its spawn/update scripts or editor data. Adding such an emitter to a system then dereferenced the missing state and hard-crashed the editor with an access violation. Both are now built through the same factories the content browser uses, so the assets are fully initialized. As defense in depth, the add-emitter paths verify an emitter has a graph source first and return a clean error (or skip it, surfaced in the result) instead of crashing. -
Feedback no longer requires a python workaround.
feedback(submit)rejected any report that lacked an executedexecute_pythonworkaround, which blocked the most valuable reports - a tool that crashed, a missing action, a dead-end gap where there is nothing to work around. Submissions are now gated on placeholder/spam shape only (a specific title and a substantive summary);pythonWorkaroundandidealToolstay as optional enrichment.