Separate GUI trigger possible?

Im quite sure I'm misinterpreting "NPC GUI - kits" vs "8753201223" kits.. 

Up until this point, We've just collected all claimable kits under "NPC GUI - kits". 

Is it possible to have 1 trigger for certain kits. I.e:

/kit will give the basic starter, medic, discord, steam kit 

/vip will show gui for another set of kits like VIP, VIP2, VIP3 and so on?

5d66db4201195.jpg?uid=5d66db72ac9cd RyanFromRust

How would that generate a gui for a limited amounts of kits.

/kit would normally show the Kits GUI. If you wanted /kit to just redeem a basic kit granted to the default group, you'd need to replace the /kit with /kit basic1. /vip isn't normally a command, but you could make it one with Alias System, such as /kit.

Maybe your default group could use just chat kits, and the VIP gets the Kits GUI.
5d66db4201195.jpg?uid=5d66db72ac9cd RyanFromRust
/kit would normally show the Kits GUI. If you wanted /kit to just redeem a basic kit granted to the default group, you'd need to replace the /kit with /kit basic1. /vip isn't normally a command, but you could make it one with Alias System, such as /kit.

Maybe your default group could use just chat kits, and the VIP gets the Kits GUI.
I see what you are saying. In the following code, how would you access the kits with description "VIPs Kits" if using it properly? Im sure I'm not understanding properly how this is set up. We throw everything inn under "NPC - GUI KITS". I did an example way at the bottom explains better what i suddenly thought was possible with this plugin. 

"NPC - GUI Kits": {
"1235439": {
      "description": "Welcome on this server, Here is a list of free kits that you can get only once each\n\n                      Enjoy your stay",
      "kits": [
        "kit1",
        "kit2"
      ]
    },
    "8753201223": {
      "description": "VIPs Kits",
      "kits": [
        "kit1",
        "kit3"
      ]
    }
}​
Example
"NPC - GUI Kits": {
"Normal_GUI_Name": {
      "description": "Normal GUI kits accessible by /kit",
      "kits": [
        "kit1",
        "kit2"
      ]
    },
    "VIP_GUI_Name": {
      "description": "VIP GUI kits accessible by /vip",
      "kits": [
        "kit1",
        "kit3"
      ]
    }
}​
Alias System config: 
{
	"alias": [
		{
			"original": "/kit",
			"alias": "/vip",
			"originaltype": "chat",
			"aliastype": "chat",
			"permission": "aliassystem.use"
		},
			{
			"original": "/kit basic1",
			"alias": "/kit",
			"originaltype": "chat",
			"aliastype": "chat",
			"permission": "aliassystem.use"
		},
	]
}​
I'm curious if it'll even work or if /kit will be overwritten and only one would work.. Not sure.

I'm not the best at Chat Kits, @pookins is. Maybe 1235439 is chat kits. See here.

Chat GUI

By default there are no chat gui.
But you may replace the default /kit chat command by a gui.
in the NPC - GUI Kits, instead of putting an NPC id, put: "0".

I read the above like 100 times. It says "There is no GUI by default once loaded the first time, but you can put a 0 to get a GUI to show"
Maybe this is close:

"NPC - GUI Kits": {
"1235439": {
      "description": "Welcome to Another P2W Server!",
      "kits": [
        "chatkit1",
        "chatkit2"
      ]
    },
    "0": {
      "description": "VIPs Kits",
      "kits": [
        "VIP1",
        "VIP2"
      ]
    }
}

Keeping in mind the goal:

/kit will give the basic starter, medic, discord, steam kit 

/vip will show gui for another set of kits like VIP, VIP2, VIP3 and so on?

Interesting approach! But not quite what im looking for. We will probably just keep it the way it is as to changing it to be 50/50 chat kit and gui kit.

I wanted to have two seperate but identical GUIs, one triggered by /kit (displaying a selected amount of kits) and one triggered by /vip (showing obviously vip kits).