CoreAPI

Core MENU API is known as CoreAPI

version 2.xx

What’s inside?

[A] – CoreAPI (transfer)(copy)

[B] – Install (copy)

[C] – Notecard with _CONFIGxxxx

What do you need to prepare?

Any compatible API plugin scripts that will let you load it on CoreAPI.

Installation setup.

  1. Drop [A] in your empty build.
  2. Drop any API feature scripts or plugin scripts into the build
  3. Rename the note card [C] with the given note card name provided on the chat screen.  View and edit the note card [C] and make sure you have all the essential configuration setup well.
  4. Drop that already edited note card [C] into your builds and initialize the configurations.  All needed or special configurations will be automatically loaded.
  5. Enjoy the program you have just built.

Note card configurations is essential on this version. This system will not be activated without prior note card setup.  First you drop [A] from the inventory and it will not notice anything until you have insert [B] into your build. Finally you will see a requirement of a specific note card to be inserted into the build as well.   To have a successful configuration for the setup, you will need to rename any note card with that specific note card name and put the following information on the note card.

Essential NC information

This is necessary for the following information to present the note card to specify your custom build from your project.  Normally you will have a product name (PROJECTNAME), a demo name (PROJECTNAMEINDEMO) in case that product is necessary to have a demo mode which provide a period of time for the potential customers to try on the product, and a product version (PRODUCT_VERSION) where a 3 or 4 decimal is taking places.  Here is an example to configure the initialization where is shown in quotations.

PROJECTNAME my awesome kawaiii doll

The product name for this build

PROJECTNAMEINDEMO my awesome kawaiii doll  demo

The demo product name for this build

PRODUCT_VERSION 1.231

A specified version number in 4 decimals to check with the server data.

Optional Functional Configurations For Advanced Builders

All examples are shown in quotation.

These set valuables are helping builders to develop their products systematically.  This provides a gateway to update the product constrained by rezzing the build on the ground. SERVER valuable is taking place to provide an object destination (UUID) to communicate from this product.  If this product is determined to be out updated, the server will send an updated product to the customer automatically.

SERVER <36 chars uuid>

A 36-character UUID appoints to your inventory server when the update feature is actived.  An email will be sent to the server to obtain an updated version.

 

PERMISSION_CONTROL 3

Permission value are ranged from integer 0 to 6.  Default value is 0.  This permission control valuable allows builders to preset the permission values before the end user changing it.  Owner the object can override all permission settings in all time. Each number are stand for these configurations:

  • 0 – OWNER CONTROL ONLY
  • 1 – GROUP ACCESS
  • 2 – PUBLIC ACCESS
  • 3 – Allow everyone but for the the people in the banned list.
  • 4 – No one but trusted people
  • 5 – Group people and trusted people
  • 6 – Trusted people in the group only

 

TOUCHTRIGGER_CONTROL 1

TRUE/FALSE value by using “1” /”0″. Default value is 1. Determine whether not using touch event to trigger the menu.  This feature allows the build to be triggered by touching or using other method such as using internal communication method, LinkMessage integer number.

 

ATTACHMENT_ENFORCE 0

TRUE/FALSE value by using “1” /”0″. Default value is 0.  By enabling this valuable, end users will not able to ground rez the product and they need to wear or attach it onto any part of the body including the HUD screen.  This feature enables the capability to protect end users to rez the object directly onto the ground.  This feature is recommended for any wearing objects such as HUDs, glasses, guns, weapons, sexual organs, clothings, shoes, and demo shoes.

Optional button layout configurations

These are the available button layout that can be remapped. Remember there must a space to separate the layout value and the new remapped button name.

“MORE”,”PERMISSION”,”BACK”,”GROUP”,”OWNER”, “ABOUT”,”PUBLIC”,”BANNED”,”TRUSTED”,

“TOGROUP”, “T_AND_GROUP”,”UPDATES”,”COMMUNITY”,”ASSISTANCE”,”ACCESS”, “TRUSTEDLIST”,”BANNEDLIST”,”ADD”,”REMOVE”,”CLEARMEM”,”VIEWLIST”,”NEXTFACE”,”PREFACE”.

Each line represent one interface button shown on the menu, you can freely change those button name or even change them into your language. Caution: Do not to put more than 20characters in each custom interface button.  For example:

BACK <<<

Caution

version 1.xx

One response to “CoreAPI

  1. Pingback: todo list for today « HKM United

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s