# Script Editor Documentation

**URL:** <https://forum.inductiveautomation.com/t/script-editor-documentation/29658>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [November 4, 2019, 11:35pm UTC](https://forum.inductiveautomation.com/t/script-editor-documentation/29658 "2019-11-04T23:35:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [November 5, 2019, 1:01pm UTC](https://forum.inductiveautomation.com/t/script-editor-documentation/29658/2 "2019-11-05T13:01:12Z")

</div>

> [@User object functions](http://forum.inductiveautomation.com/t/user-object-functions/28211/4):
>
> Unfortunately, at some level (and it’s easy to do, so there’s no real way to tell you exactly when it will be) you “break out” of the expected areas where we’ve documented things and end up in the base Java classes that we’re using internally. Jython automatically wraps these up so they mostly seem like Python objects, so it’s hard to tell exactly when you get there. What I generally recommend, if you’re encountering something unfamiliar and want to see what you can do with it: Start with run…

---

_[View the full topic](https://forum.inductiveautomation.com/t/script-editor-documentation/29658)._