# Ignition script editor, it kinda sucks

**URL:** <https://forum.inductiveautomation.com/t/ignition-script-editor-it-kinda-sucks/29313>\
**Category:** General Discussion\
**Tags:** scripting\
**Created:** [October 23, 2019, 11:46am UTC](https://forum.inductiveautomation.com/t/ignition-script-editor-it-kinda-sucks/29313 "2019-10-23T11:46:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![RadicalRumin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/radicalrumin/32/11543_2.png) [@RadicalRumin](https://forum.inductiveautomation.com/u/RadicalRumin)\
**Post date:** [October 23, 2019, 12:20pm UTC](https://forum.inductiveautomation.com/t/ignition-script-editor-it-kinda-sucks/29313/3 "2019-10-23T12:20:58Z")

</div>

Fair enough. I’m personally not very familiar with most of the Ignition specific functions yet, so I have been making use of the script editor for those few helpful Ignition specific features it does have.

I did find an interesting thread about someone who had made a library of mock system functions however. [Ignition mock scripts on GitHub](http://forum.inductiveautomation.com/t/ignition-mock-scripts-on-github/16468)

Still, it’d be perfect if you were somehow able to make use of you editor of choice in the Designer itself.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-script-editor-it-kinda-sucks/29313)._