Avatar Parameters
When creating a new reciever on your avatar to trigger your QTShock, there are specific requirements for the parameter name for it to properly communicate with the QTHub application.
The parameter name is broken down into 5 different smaller parameters.
Lets take a look at the hitbox reciever parameter on the official QTShock public avatar as an example:
QTS_0_HIT_SHOCK_TASED
Parameter | Example/Value | Value Type | Allowed Values | Description |
---|---|---|---|---|
Prefix | QTS | String | QTS | This must not change, this helps QTHub recognize what parameters are meant specifically for QTHub. |
Shocker | 0 | Int | 0 , 1 , 2 , 3 , 4 | The index of the shocker you want to trigger with this contact reciever. |
Interaction Type | HIT | String | HIT , PUSH | HIT is used when you want to trigger the QTShock via a bool, and will trigger the QTShock when the value is true . PUSH is used when you want to trigger the QTShock via a float, and will trigger the QTShock when the value is above 0.8 . |
Command | SHOCK | String | SHOCK , VIBRATE , BEEP | How you want to trigger your QTShock. I think this is pretty self-explanitory. If you want to shock on this interaction, you put SHOCK here. If you want to vibrate on this interaction, you put VIBRATE here. If you want to beep on this interaction, you put BEEP here. |
Name | TASED | String | All | This can be whatever you want to help you distinguish what parameter is for what. |
So, in the case of this example, if we were to use QTS_0_HIT_SHOCK_TASED
as the parameter for a new contact reciever, it would send a shock command to the shocker at index 0 (the first shocker paired to your QTShock) when the value of this reciever is true