PyroTech03

I know this is old but it's something I'm using extensively so wanted to mention it here. In a recent update we now have item based event calls that allow you to call a common event within the item. Two of which are "on equip" and "on unequip" You can now do the same thing but without having to use an autorun as the trigger, thus not having an event needlessly running for every player.

That solves my issues then! Looking forward to being able to try it out.

Registering on client directly sounds good. I remember reading on your page though saying it would disable normal login/registration on the WordPress site though. I was just suggesting that you had a way to tell WordPress to associate your WordPress account with your intersect account afterwards for sites that are already established. Similar in a way you can connect your socials on sites. Example, I have about 120 accounts on my WordPress site. According to what you have at https://intersect-connect.tk/intersect-management-wordpress-plugin/ you are saying default WordPress login/registration should be off. By making the system where users can tell the plugin what their account is and then verify it, it would allow the default functionality of WordPress. Otherwise you're asking users who have established WP sites to stop their normal operation. And by that point, it's an easier decision for most to probably just install the CMS and get the shop functionality that way.

Cool. On the plugin I'd like to suggest making a way to link accounts to their intersect game accounts instead of requiring new users. Most people who go the route of using WP likely already have established websites. Other than that, the more you can put in it the better I guess.

Hey was looking at this and saw you are doing something for wordpress. How much will that plugin handle vs what the CMS does? I have an existing WP site for my gaming community and trying to figure out what way to go with website stuff.

Does this spreadsheet exist anywhere? It's gone from Google.

I know this is old, but would love to see this make it into the core engine. It's so useful and looks like it could solve a few of the issue's I've been having trying to find some workarounds in my project!