> For the complete documentation index, see [llms.txt](https://docs.libiengine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.libiengine.com/developer-community.md). # Developer Community There are a variety of ways to get building on KIP. Using templates with drag and drop, node based editor for adding new functionalities. We plan to release Javascript library and LUA scripting too. Given the modular nature of our engine, you can also create your own interface to the engine. ### How to get started: **Node based Scripting** Similar to Unreal's blueprint, we use a node based system to easily create sophisticated 3D scenes without the need to code. #### **Javascript Library (Coming soon)** For those familiar with three.js or babylon.js #### LUA Programming (Coming soon) LUA scripting is great for customising and has seen good adoption with Roblox. This is on our roadmap too. If you have any suggestions feel free to contact the team on [`Discord`](https://discord.gg/Nqse2JfRbf): --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.libiengine.com/developer-community.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.