User Tools

Site Tools


cherrycore

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
cherrycore [2024/05/07 17:48] – onslaughtcherrycore [2024/05/07 17:52] – onslaught
Line 10: Line 10:
 ==== Cherry Add-ons List==== ==== Cherry Add-ons List====
  
-^ ^ Addon^+^ ^ Add-on^
 | {{:cherry:core_addon_logo.png?100|}}| **[[cherrycore|Cherry Core]]** | | {{:cherry:core_addon_logo.png?100|}}| **[[cherrycore|Cherry Core]]** |
 |:::                                  |This add-on. Cherry Core is required for all other Cherry add-ons     | |:::                                  |This add-on. Cherry Core is required for all other Cherry add-ons     |
 | {{:cherry:telegram_addon_logo.png?100|}}| **[[cherrytelegram|Cherry Telegram]]** | | {{:cherry:telegram_addon_logo.png?100|}}| **[[cherrytelegram|Cherry Telegram]]** |
 |:::                                  |Utilizes Telegram's bot technology to transfer messages back and forth to the game. Telegram is free and creating a bot is free as well as easy. No coding skills are needed. Follow the instructions carefully to ensure that you don't have any issues| |:::                                  |Utilizes Telegram's bot technology to transfer messages back and forth to the game. Telegram is free and creating a bot is free as well as easy. No coding skills are needed. Follow the instructions carefully to ensure that you don't have any issues|
 +| {{:cherry:discord_wiki_logo.png?100|}}| **[[cherrydiscord|Cherry Discord]]** |
 +|:::                                  |Send in game messages directly to your discord server. Utilize commands to communicate directly with your friends and free company members and any other message based usage you can think of. Directly command and receive message from supported add-ons mods.|
  
  
-====Cherry Connect API Referance==== 
  
-Cherry Connect allows your add-on to send and receive messages from any Cherry communication addon the user has installed. When Your add-on requests access Cherry Connect automatically registers with all communication add-ons that the user currently employs. The user has full control over which if any communication add-ons your add-on is allowed to connect to. Cherry Connect abstracts the individual details away and allows you to focus on sending and receiving messages without the details of the specific communication client that the user has deployed.+ 
 + 
 +====Cherry Connect API Reference==== 
 + 
 +Cherry Connect allows your add-on to send and receive messages from any Cherry communication add-on the user has installed. When Your add-on requests access, Cherry Connect automatically registers with all communication add-ons that the user currently employs. The user has full control over which, if any, communication add-ons your add-on is allowed to connect to. Cherry Connect abstracts the individual details away and allows you to focus on sending and receiving messages without the details of the specific communication client that the user has deployed.
  
 The Cherry Connect API is fairly simple and is accessed by the global variable  The Cherry Connect API is fairly simple and is accessed by the global variable 
Line 30: Line 35:
 === Main Communication function === === Main Communication function ===
  
-The function that is passed to CherryConnect.Register will be the function that which most user messages and commands will be routed. The exception would be CherryConnect.MessageOptions where the user-selected option will be routed directly to the specially supplied function.+The function that is passed to CherryConnect.Register will be the function that which most user messages and commands will be routed. The exception would be Cherry Connect.MessageOptions where the user-selected option will be routed directly to the specially supplied function.
  
 The When the user sends a message or command that is routed to cmd_func The signature will be function(result). The result will either be an error or a message result: The When the user sends a message or command that is routed to cmd_func The signature will be function(result). The result will either be an error or a message result:
Line 163: Line 168:
  
 The mod name cannot conflict with any other mod or command. Mods do not share a 1 to 1 relationship with an add-on, so a single add-on can register multiple mods. The mod name cannot conflict with any other mod or command. Mods do not share a 1 to 1 relationship with an add-on, so a single add-on can register multiple mods.
-**MOD_ID** Will be used in all the other API calls to identify which mod is making the call. The **MOD_ID** must be saved for as long as Cherry Core is not unloaded or until the mod is unregistered. Once the mod is unregistered you must re-register the mod to access a new **MOD_ID**+**MOD_ID** Will be used in all the other API calls to identify which mod is making the call. The **MOD_ID** must be saved for as long as Cherry Core is not unloaded or until the mod is unregistered. Once the mod is unregistered, you must re-register the mod to access a new **MOD_ID**
  
 {{:cherry:mod_view.png?600|}} {{:cherry:mod_view.png?600|}}
Line 177: Line 182:
  
 //Notes// //Notes//
-Most of the time you will not need to unregister a mod. The mod will need to be re-registered anytime the addons are all reloaded and a new mod_id will be generated. If you're going to lose the mod_id and you need to re-register your mod without reloading Cherry Core, Then you will need to unregister the mod.+Most of the time, you will not need to unregister a mod. The mod will need to be re-registered anytime the add-ons are all reloaded and a new mod_id will be generated. If you're going to lose the mod_id and you need to re-register your mod without reloading Cherry Core, Then you will need to unregister the mod.
  
  
Line 223: Line 228:
  
   * **mod_id** - //required//   * **mod_id** - //required//
-    * The id of the mod that has been registered.+    * The ID of the mod that has been registered.
   * **options** - //required//   * **options** - //required//
     * A list of options that the user has to select from. The options are in the format of: {"Option1","Option2","Option3",...}      * A list of options that the user has to select from. The options are in the format of: {"Option1","Option2","Option3",...} 
Line 259: Line 264:
 Usage: Usage:
 <code> CherryConnect.MessageResponse(mod_id, callback_id, message)</code> <code> CherryConnect.MessageResponse(mod_id, callback_id, message)</code>
-Let's the user's client know That the option has been received successfully+Let the user's client know That the option has been received successfully
  
  * **mod_id** - //required//  * **mod_id** - //required//
Line 268: Line 273:
     * A simple message to the user acknowledging that the option was selected.     * A simple message to the user acknowledging that the option was selected.
  
-**returns**+**Returns**
  
 On errors: On errors:
cherrycore.txt · Last modified: 2024/05/07 17:54 by onslaught

Page Tools