Krafties Scripting API - Revision history

Admin at 23:15, 2 October 2023

2023-10-02T23:15:21Z

Admin at 18:53, 17 March 2020

2020-03-17T18:53:53Z

Admin at 18:29, 17 March 2020

2020-03-17T18:29:05Z

Destiny Yheng at 15:53, 19 August 2016

2016-08-19T15:53:20Z

Doroteya at 10:44, 19 August 2016

2016-08-19T10:44:42Z

Doroteya at 10:42, 19 August 2016

2016-08-19T10:42:31Z

Doroteya at 10:40, 19 August 2016

2016-08-19T10:40:55Z

Doroteya at 10:38, 19 August 2016

2016-08-19T10:38:08Z

MyraMidnight at 11:02, 16 September 2014

2014-09-16T11:02:23Z

MyraMidnight at 12:14, 21 August 2014

2014-08-21T12:14:22Z

@@ Line 1: / Line 1: @@
 [[Category:Krafties API]]
 <!-- I added the "code"tags to make the code stand out, and the "nowiki" to prevent the wiki from formatting any of the code when it wasn't supposed to -->
@@ Line 150: / Line 38: @@
 *'''Prim 10 Description:'''  <code><nowiki>(integer)playerExpEarnedLast24Hours + "," + (integer)playerExpEarnedLastWeek + "," + (integer)playerExpEarnedLastMonth + "," + (integer)playerExpEarnedAllTime + "," + (integer)battlesWonLast24Hours+ "," + (integer)battlesWonLast24Week + "," + (integer)battlesWonLast24Month + "," + (integer)battlesWonAllTime</nowiki></code>
-*'''Prim 11 Description:''' <code><nowiki>(integer)getAffinity</nowiki></code>
+*'''Prim 11 Description:''' <code><nowiki>(integer)spellsCanBeCastOnThisCreatureBool</nowiki></code>
 *'''Prim 12 Description:''' <code><nowiki>(string)llList2CSV(weaknesses)</nowiki></code>

@@ Line 3: / Line 3: @@
 :The Krafties Scripting API is a feature which allows you to get data from your Kraftie Creature for your own scripted third party addons.
-:Currently this is read only although gives access to a wide range of possibilities.
+:Currently this is read only, although it still gives access to a wide range of possibilities.
 :This API relies on listening to 1 minute pings on channel '''<code>-748382747</code>''' from inworld Krafties Creatures.
 :Creatures will communicate on this channel once <code>on_rez</code> and then every 60 seconds.
@@ Line 12: / Line 12: @@
 Parsing this string to a list you can get the prims data from the description using <code><nowiki>llGetObjectDetails (PRIM_DESC or PRIM_NAME)</nowiki></code>

@@ Line 40: / Line 40: @@
 *'''Prim 12 Description:''' <code><nowiki>(string)llList2CSV(weaknesses)</nowiki></code>
-*'''Prim 13 Description:''' <code><nowiki>(integer)silverMembershipExpiryUnixTime+";"+(integer)goldMembershipExpiryUnixTime</nowiki></code>
+*'''Prim 13 Description:''' <code><nowiki>(integer)allowSpellAssistance</nowiki></code>
 *'''Prim 14 Description :''' <code><nowiki>(string)currentSpell</nowiki></code>
@@ Line 152: / Line 152: @@
 *'''Prim 12 Description:''' <code><nowiki>(string)llList2CSV(weaknesses)</nowiki></code>
-*'''Prim 13 Description:''' <code><nowiki>(integer)silverMembershipExpiryUnixTime+";"+(integer)goldMembershipExpiryUnixTime</nowiki></code>
+*'''Prim 13 Description:''' <code><nowiki>(integer)allowSpellAssistance</nowiki></code>
 *'''Prim 14 Description :''' <code><nowiki>(string)currentSpell</nowiki></code>

← Older revision		Revision as of 15:53, 19 August 2016
Line 1:		Line 1:
−	~~= Krafties - Spell Receiver API v1.0 =~~
−
−	~~~~ NOTE: You MUST obtain an API key from Krafties before being able to use any of the Krafties APIs! This key is unique to each individual creator and should not be shared.~~
−
−	~~~~ Please see http://krafties.com/wiki for more details on the API and API keys.~~
−
−
−	The Spell Receiver API allows player owned krafties to cast specific spells on any objects you create! The API allows you to then handle and respond to the spells when they are cast with ANY LSL code you put together via linked messages. At this point in time, when a spell is cast the API exposes the name of the spell that was cast, and the type of spell cast. These are all handled in a link_message event.
−
−
−
−	~~---------------------------------------------------------------------------------------~~
−	~~SETUP:~~
−	~~---------------------------------------------------------------------------------------~~
−	~~Step 1) Obtain your unique API Key. If you already have an API Key from a separate Krafties API, that will work for this one as well!~~
−
−
−	~~Step 2) Drop both the "Krafties-API_spellReceiver v1.0" and "KRAFTIES_API Config [SpellReceiver]" scripts into the object you wish to have Krafties spells cast on~~
−
−
−	~~Step 3) Open and configure the "Krafties_API Config [Spell Receiver]" script. All configuration variables are at the top of the script.~~
−	~~a) API_KEY:~~
−	~~- This is the key you get from Krafties that identifies you as a unique creator. Once you have obtained your key, copy/paste it into the script where it says UNIQUE_API_KEY_HERE.~~
−	~~b) SPELL_DISPLAY_TYPES~~
−	- This list determines what types of spells will show up in the menus of a player attempting to cast a spell on this object, if the player's creature has unlocked said spells. Alongside the predefined spell group identifiers, you can also include the names of specific spells or specific element types. Spell group identifiers follow:
−	* SET_SPELL
−	~~- Displays spells that show up when a player clicks their creature, selects "Battles", then selects "Set Spell"~~
−	* OTHER_ACTIVE
−	~~- Displays spells that show up when a player clicks on another player's active creature and then selects "Cast Spell"~~
−	* WILD
−	~~- Displays spells that show up when a player clicks on a wild creature, then selects "Cast Spell"~~
−	* SELF
−	~~- Displays spells that show up when a player clicks on their own active creature, then selects "Cast Spell"~~
−	* OPPONENT
−	~~- Displays spells that show up when a player clicks on an opposing creature in PvP battle~~
−	* TEAMMATE
−	~~- Displays spells that show up when a player clicks in a teammate in PvP battle~~
−	* ENCHANT
−	~~- Displays spells that show up when a creature clicks an enchanting tablet, then selects "Cast Spell"~~
−	* ALCHEMY
−	~~- Displays spells that show up when a creature clicks an alchemy tablet, then selects "Cast Spell"~~
−
−
−	~~Step 4) Save the "Krafties_API Config [Spell Receiver]" script.~~
−
−
−	*** IF ALL WENT WELL, YOU NOW HAVE THE BASIC SPELL CASTING FEATURES SET UP. CLICKING THE OBJECT WILL GIVE YOU A MENU ALLOWING YOU TO CAST SPELLS ON IT IF YOU HAVE A SUITABLE ACTIVE KRAFTIE ATTACHED.
−
−	*** ADVANCED STEPS FOLLOW
−
−
−	You are now ready to handle spells being cast, either in the link_message event of the "KRAFTIES_API Config [SpellReceiver]" script itself or your own script residing in the same object. Note that if you do use your own script, you will want to remove the llSay() provided in the "KRAFTIES_API Config [SpellReceiver]" so as not to detract from the experience you create.
−
−	~~When a spell is cast, this function is called:~~
−	~~- llMessageLinked(LINK_SET, 59377, spellName, spellType);~~
−
−	~~What this does parameter by parameter:~~
−	~~- assuming link_message event structure of: link_message(integer senderNum, integer num, string message, key id)~~
−	* LINK_SET: message is sent to ALL prims in the link set
−	* 59377: message is broadcast with a number identifier of 59377
−	~~- FUN FACT: to 59377 resembles the word "SPELL"~~
−	~~- In your link_message events, you'll want to check if (num == 59377) to verify it is a spell message~~
−	* spellName: the message parameter holds the name of the spell cast
−	~~- in script: string spellName = message;~~
−	* spellType: the id parameter holds the element type of spell cast
−	~~- In script: string spellType = (string)id;~~
−	* Cast to string because actual type of id is key
−
−	~~EXAMPLE:~~
−	~~- Fireplace that lights when any fire spell is cast on it~~
−	* In config step:
−	~~- list SPELL_DISPLAY_TYPES = ["Fire"];~~
−	* IF FLAMETHROWER IS CAST:
−	~~- Link message sent: llMessageLinked(LINK_SET, 59377, "Flamethrower", "Fire");~~
−	~~---------------------------------------------------------------------------------------~~
−
−	~~---------------------------------------------------------------------------------------~~
−
−

	= Creature/Pet API =		= Creature/Pet API =

@@ Line 20: / Line 20: @@
 Step 3) Open and configure the "Krafties_API Config [Spell Receiver]" script. All configuration variables are at the top of the script.
-a) API_KEY:
+    a) API_KEY:
-- This is the key you get from Krafties that identifies you as a unique creator. Once you have obtained your key, copy/paste it into the script where it says UNIQUE_API_KEY_HERE.
+        - This is the key you get from Krafties that identifies you as a unique creator. Once you have obtained your key, copy/paste it into the script where it says UNIQUE_API_KEY_HERE.
-b) SPELL_DISPLAY_TYPES
+    b) SPELL_DISPLAY_TYPES
-- This list determines what types of spells will show up in the menus of a player attempting to cast a spell on this object, if the player's creature has unlocked said spells. Alongside the predefined spell group identifiers, you can also include the names of specific spells or specific element types. Spell group identifiers follow:
+        - This list determines what types of spells will show up in the menus of a player attempting to cast a spell on this object, if the player's creature has unlocked said spells. Alongside the predefined spell group identifiers, you can also include the names of specific spells or specific element types. Spell group identifiers follow:
              * SET_SPELL
                  - Displays spells that show up when a player clicks their creature, selects "Battles", then selects "Set Spell"
@@ Line 53: / Line 53: @@
 When a spell is cast, this function is called:
-- llMessageLinked(LINK_SET, 59377, spellName, spellType);
+    - llMessageLinked(LINK_SET, 59377, spellName, spellType);
 What this does parameter by parameter:
-- assuming link_message event structure of: link_message(integer senderNum, integer num, string message, key id)
+    - assuming link_message event structure of: link_message(integer senderNum, integer num, string message, key id)
          * LINK_SET: message is sent to ALL prims in the link set
          * 59377: message is broadcast with a number identifier of 59377
@@ Line 68: / Line 68: @@
 EXAMPLE:
-- Fireplace that lights when any fire spell is cast on it
+        - Fireplace that lights when any fire spell is cast on it
              * In config step:
                  - list SPELL_DISPLAY_TYPES = ["Fire"];

@@ Line 1: / Line 1: @@
-********************************************************
+= Krafties - Spell Receiver API v1.0 =
 ~~ NOTE: You MUST obtain an API key from Krafties before being able to use any of the Krafties APIs! This key is unique to each individual creator and should not be shared.
@@ Line 80: / Line 77: @@
 ---------------------------------------------------------------------------------------

← Older revision		Revision as of 10:38, 19 August 2016
Line 1:		Line 1:
		+	********************************************************
		+	Krafties - Spell Receiver API v1.0
		+	********************************************************
		+
		+
		+	~~ NOTE: You MUST obtain an API key from Krafties before being able to use any of the Krafties APIs! This key is unique to each individual creator and should not be shared.
		+
		+	~~ Please see http://krafties.com/wiki for more details on the API and API keys.
		+
		+
		+	The Spell Receiver API allows player owned krafties to cast specific spells on any objects you create! The API allows you to then handle and respond to the spells when they are cast with ANY LSL code you put together via linked messages. At this point in time, when a spell is cast the API exposes the name of the spell that was cast, and the type of spell cast. These are all handled in a link_message event.
		+
		+
		+
		+	---------------------------------------------------------------------------------------
		+	SETUP:
		+	---------------------------------------------------------------------------------------
		+	Step 1) Obtain your unique API Key. If you already have an API Key from a separate Krafties API, that will work for this one as well!
		+
		+
		+	Step 2) Drop both the "Krafties-API_spellReceiver v1.0" and "KRAFTIES_API Config [SpellReceiver]" scripts into the object you wish to have Krafties spells cast on
		+
		+
		+	Step 3) Open and configure the "Krafties_API Config [Spell Receiver]" script. All configuration variables are at the top of the script.
		+	a) API_KEY:
		+	- This is the key you get from Krafties that identifies you as a unique creator. Once you have obtained your key, copy/paste it into the script where it says UNIQUE_API_KEY_HERE.
		+	b) SPELL_DISPLAY_TYPES
		+	- This list determines what types of spells will show up in the menus of a player attempting to cast a spell on this object, if the player's creature has unlocked said spells. Alongside the predefined spell group identifiers, you can also include the names of specific spells or specific element types. Spell group identifiers follow:
		+	* SET_SPELL
		+	- Displays spells that show up when a player clicks their creature, selects "Battles", then selects "Set Spell"
		+	* OTHER_ACTIVE
		+	- Displays spells that show up when a player clicks on another player's active creature and then selects "Cast Spell"
		+	* WILD
		+	- Displays spells that show up when a player clicks on a wild creature, then selects "Cast Spell"
		+	* SELF
		+	- Displays spells that show up when a player clicks on their own active creature, then selects "Cast Spell"
		+	* OPPONENT
		+	- Displays spells that show up when a player clicks on an opposing creature in PvP battle
		+	* TEAMMATE
		+	- Displays spells that show up when a player clicks in a teammate in PvP battle
		+	* ENCHANT
		+	- Displays spells that show up when a creature clicks an enchanting tablet, then selects "Cast Spell"
		+	* ALCHEMY
		+	- Displays spells that show up when a creature clicks an alchemy tablet, then selects "Cast Spell"
		+
		+
		+	Step 4) Save the "Krafties_API Config [Spell Receiver]" script.
		+
		+
		+	*** IF ALL WENT WELL, YOU NOW HAVE THE BASIC SPELL CASTING FEATURES SET UP. CLICKING THE OBJECT WILL GIVE YOU A MENU ALLOWING YOU TO CAST SPELLS ON IT IF YOU HAVE A SUITABLE ACTIVE KRAFTIE ATTACHED.
		+
		+	*** ADVANCED STEPS FOLLOW
		+
		+
		+	You are now ready to handle spells being cast, either in the link_message event of the "KRAFTIES_API Config [SpellReceiver]" script itself or your own script residing in the same object. Note that if you do use your own script, you will want to remove the llSay() provided in the "KRAFTIES_API Config [SpellReceiver]" so as not to detract from the experience you create.
		+
		+	When a spell is cast, this function is called:
		+	- llMessageLinked(LINK_SET, 59377, spellName, spellType);
		+
		+	What this does parameter by parameter:
		+	- assuming link_message event structure of: link_message(integer senderNum, integer num, string message, key id)
		+	* LINK_SET: message is sent to ALL prims in the link set
		+	* 59377: message is broadcast with a number identifier of 59377
		+	- FUN FACT: to 59377 resembles the word "SPELL"
		+	- In your link_message events, you'll want to check if (num == 59377) to verify it is a spell message
		+	* spellName: the message parameter holds the name of the spell cast
		+	- in script: string spellName = message;
		+	* spellType: the id parameter holds the element type of spell cast
		+	- In script: string spellType = (string)id;
		+	* Cast to string because actual type of id is key
		+
		+	EXAMPLE:
		+	- Fireplace that lights when any fire spell is cast on it
		+	* In config step:
		+	- list SPELL_DISPLAY_TYPES = ["Fire"];
		+	* IF FLAMETHROWER IS CAST:
		+	- Link message sent: llMessageLinked(LINK_SET, 59377, "Flamethrower", "Fire");
		+	---------------------------------------------------------------------------------------
		+
		+	---------------------------------------------------------------------------------------
		+
		+
		+
		+
		+
		+	Enjoy! Please see http://krafties.com/wiki for additional information
		+
		+
		+
		+
		+
	[[Category:Krafties API]]		[[Category:Krafties API]]
	<!-- I added the "code"tags to make the code stand out, and the "nowiki" to prevent the wiki from formatting any of the code when it wasn't supposed to -->		<!-- I added the "code"tags to make the code stand out, and the "nowiki" to prevent the wiki from formatting any of the code when it wasn't supposed to -->

← Older revision		Revision as of 12:14, 21 August 2014
Line 90:		Line 90:

	*Player Eliminated		*Player Eliminated
−

	These messages will be send on the corresponding event. There are 2 lists delimited by <code>","</code> & <code>"\|"</code> into a string.		These messages will be send on the corresponding event. There are 2 lists delimited by <code>","</code> & <code>"\|"</code> into a string.