# Is ignition-module-tools working for version 8.3?

**URL:** <https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105>\
**Category:** Module Development\
**Tags:** perspective\
**Created:** [June 23, 2026, 1:45am UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105 "2026-06-23T01:45:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrick.maltais](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/patrick.maltais/32/3958_2.png) [@patrick.maltais](https://forum.inductiveautomation.com/u/patrick.maltais)\
**Post date:** [June 23, 2026, 1:45am UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/1 "2026-06-23T01:45:07Z")

</div>

Hello,

I'm just starting to explore the SDK. I'm fairly new to this type of development environment, although I consider myself to have a very good knowledge of Ignition itself.

I'm using a clone of **ignition-module-tools** to generate a brand-new project from scratch. From what I can tell, the latest branch on GitHub generates new projects compatible with Ignition 8.1.20.

In my case, I've configured my development environment to test against Ignition 8.3.x, since that's the version used by most of our customers. Unless I've missed some instructions, I haven't been able to get the generated project working with 8.3, even though the build succeeds and I'm able to install the resulting `.modl` file.

Is there a documented procedure somewhere that explains how to modify a newly generated project so that it can be used with Ignition 8.3?

I know that if I use the `ignition-sdk-examples/perspective-component` or `ignition-sdk-examples/perspective-component-minimal` examples, everything works correctly. At that point, I could simply modify one of those projects until it becomes equivalent to a freshly generated project from `ignition-module-tools`.

However, I'd prefer to start with something as clean as possible from the beginning.

Any suggestions?

---

<div class="post-metadata">

**Author:** ![lane.duncan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lane.duncan/32/83700_2.png) [@lane.duncan](https://forum.inductiveautomation.com/u/lane.duncan)\
**Post date:** [June 23, 2026, 6:39am UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/2 "2026-06-23T06:39:00Z")

</div>

> [@patrick.maltais](#):
>
> I could simply modify one of those projects until it becomes equivalent to a freshly generated project

This is what I ended up doing for 8.3.2. Essentially piecing together what I needed to get my first “Hello World” in the place where I needed it.

I have also bookmarked this recent topic for future reference, but have not had time to understand it on any level:

> [@Ignition Module Starter now available](https://forum.inductiveautomation.com/t/ignition-module-starter-now-available/115880):
>
> @alexmarcy Nerd sniped me good today, so I made a Claude skill to help you kick start your Ignition module development. Not tested yet (I'll only do so much on the weekend!), but I welcome your feedback and PRs. [GitHub - inductiveautomation/ignition-module-starter: A Claude Code skill and resources to help new module authors get started with module development. · GitHub](https://github.com/inductiveautomation/ignition-module-starter)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 23, 2026, 3:00pm UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/3 "2026-06-23T15:00:35Z")

</div>

The `ignition-module-tools` extra projects (the generator CLI and the templates themselves) haven't really been touched since they were initially created; mostly down to a lack of time to invest in them. I would personally start a new module today either using the approach Kathy outlined linked above or by editing from a working example.

---

<div class="post-metadata">

**Author:** ![patrick.maltais](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/patrick.maltais/32/3958_2.png) [@patrick.maltais](https://forum.inductiveautomation.com/u/patrick.maltais)\
**Post date:** [June 23, 2026, 3:17pm UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/4 "2026-06-23T15:17:06Z")

</div>

Also my first experience with Claude Code. I suppose a Pro subscription is needed here? Any information on how to feed Claude with the content of this ignition-module-starter files? I'mnot sure what I have to do here.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 23, 2026, 3:33pm UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/5 "2026-06-23T15:33:08Z")

</div>

I mean, literally you can ask Claude. Try this prompt:

> Look at this repository and follow the steps to install it as a local skill, I want to try it out in a new session: [GitHub - inductiveautomation/ignition-module-starter: A Claude Code skill and resources to help new module authors get started with module development. · GitHub](https://github.com/inductiveautomation/ignition-module-starter)

---

<div class="post-metadata">

**Author:** ![patrick.maltais](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/patrick.maltais/32/3958_2.png) [@patrick.maltais](https://forum.inductiveautomation.com/u/patrick.maltais)\
**Post date:** [June 24, 2026, 4:38am UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/6 "2026-06-24T04:38:04Z")

</div>

I haven't had much luck with **ignition-module-starter** and Claude when I asked it to generate a project for me. However, I asked it to use an example from [ignition-sdk-examples](https://github.com/inductiveautomation/ignition-sdk-examples?utm_source=chatgpt.com) and generate a basic project based on **perspective-component-minimal**. I was able to rename the various resources and create a basic component. However, I still need to remove the default functionality (the banana animation). It's making progress...

---

<div class="post-metadata">

**Author:** ![patrick.maltais](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/patrick.maltais/32/3958_2.png) [@patrick.maltais](https://forum.inductiveautomation.com/u/patrick.maltais)\
**Post date:** [June 24, 2026, 3:13pm UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/7 "2026-06-24T15:13:24Z")

</div>

In the end, through trial and error and with the help of AI, I finally managed to create a basic component under a company-specific category. I'll be able to use this as a foundation to implement the desired functionality.

The process also helped me gain a much better understanding of the component registration mechanism.

One thing I still need to figure out is how to specify our company name in the **VENDOR NAME** field. I haven't been able to find where or how this is configured.

Could someone point me in the right direction?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/3/b328b7c8b060805bd33a93d28776bf1131d86916.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 24, 2026, 3:54pm UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/8 "2026-06-24T15:54:05Z")

</div>

If you're signing, it should be read from your cert. Theoretically it's possible to provide it without a cert, if the right key is present in the module.xml file, but our Gradle plugin doesn't appear to provide you any way to actually set that key.

> [@\[IGN-13880\] Ignition 8.3 SDK ServiceConnectorExtensionPoint Bugs/Requests/Questions](https://forum.inductiveautomation.com/t/ign-13880-ignition-8-3-sdk-serviceconnectorextensionpoint-bugs-requests-questions/109567/7):
>
> For final release, the author name will be retrieved from one of two places: The subjectName of the module cert. If no cert is supplied, then the vendorName specified in module.xml will be used. We’re aware this isn’t working in the current builds, but we fully expect it will be repaired before final release.

---

<div class="post-metadata">

**Author:** ![lane.duncan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lane.duncan/32/83700_2.png) [@lane.duncan](https://forum.inductiveautomation.com/u/lane.duncan)\
**Post date:** [June 25, 2026, 5:23am UTC](https://forum.inductiveautomation.com/t/is-ignition-module-tools-working-for-version-8-3/116105/9 "2026-06-25T05:23:59Z")

</div>

> [@paul-griffith](#):
>
> If you're signing, it should be read from your cert.

This is the way. Don’t bother with the no signing option. Signing the module is easier than dealing with the hoops you have to jump through when unsigned.

> [@paul-griffith](#):
>
> The `ignition-module-tools` extra projects (the generator CLI and the templates themselves) haven't really been touched since they were initially created;

A lot of the SDK guide seems to be obsolete. Maybe we will get an updated 8.3 guide in time for the Feb 2027 release.
