Sinfar - User contributions [en]

Getting Started

2025-10-06T13:25:17Z

Fiery Imp:

Welcome to Sinfar. Unlike most other servers of Neverwinter Nights, Sinfar uses a lot of custom features that are required before you can truly connect. Below you will find all the necessary information to log in and have fun whether you're on Diamond Edition (1.69) with Windows or Linux or if you're using Enhanced Edition.

=== Automatic Installer ===
You can download the Sinfar installer here: https://git.sinfar.net/Fiery_Imp/sinfar-installer

The installer works for both Diamond Edition and EE on Windows, for Linux and Mac users, or if you prefer to not use the installer, please see the manual installation process below.

== WARNING: USE MANUAL INSTALL FOR NOW, INSTALLER DOWNLOAD CURRENTLY BROKEN!!! LINKS BELOW FOR MANUAL INSTALL ==

==== Sinfar Installer ====
Thank you for your interest in the SinfarInstaller, this installer works for both the EE and Diamond edition of Neverwinter Nights.

For any question, you can ask FieryImp on the Sinfar Discord server, or leave a comment in the issues section available on thedownload page.

===== Feedback =====
Please give us feedback about your experience with the SinfarInstaller, whether you think something can be improved to give a smoother experience, or if you run into any kind of issues. Our goal is to make Sinfar as easy as possible to install for new players or old players alike when installing sinfar on a new system.

You may leave feedback in the "Issue" section above, or contact FieryImp on discord directly for immediate questions.

===== For regular users =====
Using the installer is easy, click on the download link below, download the file, unzip it, launch, and follow the instruction!

===== Download links =====
All files are hosted by us.

* [https://git.sinfar.net/Fiery_Imp/sinfar-installer/releases/download/2.0.0/sinfar-installer.zip Download installer 2.0.0]

===== Anti-virus false positive =====
The download of the zip file and the unzipping of it seems to trigger false positive alert from windows defender sometimes. This doesn't always happen and I have to find the cause of it.

Windows Defender will identify a supposed virus as ''Trojan:Script/Sabsik.FL.A!ml'' . It's a well known error for installer programmed that are unsigned. We do not yet have means to sign the installer unfortunately as this could cost several hundred dollars per year.

Please let us know if you run into this issue, and we'll keep working on trying to get that false positive to stop showing up.

===== For developers of the Installer =====
I'll try to list here what's needed here in order to compile the Installer.

===== Requirement =====

* Rust SDK (Download here)

=== Manual Installation ===
You can also install everything manually. For detailed instructions, please see the relevant pages:

[[Getting Started - Diamond Edition]]

[[Getting Started - Diamond Edition on Linux]]

[[Getting Started - Enhanced Edition]]

Getting Started

2025-10-06T13:24:47Z

Fiery Imp:

Welcome to Sinfar. Unlike most other servers of Neverwinter Nights, Sinfar uses a lot of custom features that are required before you can truly connect. Below you will find all the necessary information to log in and have fun whether you're on Diamond Edition (1.69) with Windows or Linux or if you're using Enhanced Edition.

=== Automatic Installer ===
You can download the Sinfar installer here: https://git.sinfar.net/Fiery_Imp/sinfar-installer

The installer works for both Diamond Edition and EE on Windows, for Linux and Mac users, or if you prefer to not use the installer, please see the manual installation process below.

== WARNING: USE MANUAL INSTALL FOR NOW, INSTALLER DOWNLOAD CURRENTLY BROKEN!!! ==

==== Sinfar Installer ====
Thank you for your interest in the SinfarInstaller, this installer works for both the EE and Diamond edition of Neverwinter Nights.

For any question, you can ask FieryImp on the Sinfar Discord server, or leave a comment in the issues section available on thedownload page.

===== Feedback =====
Please give us feedback about your experience with the SinfarInstaller, whether you think something can be improved to give a smoother experience, or if you run into any kind of issues. Our goal is to make Sinfar as easy as possible to install for new players or old players alike when installing sinfar on a new system.

You may leave feedback in the "Issue" section above, or contact FieryImp on discord directly for immediate questions.

===== For regular users =====
Using the installer is easy, click on the download link below, download the file, unzip it, launch, and follow the instruction!

===== Download links =====
All files are hosted by us.

* [https://git.sinfar.net/Fiery_Imp/sinfar-installer/releases/download/2.0.0/sinfar-installer.zip Download installer 2.0.0]

===== Anti-virus false positive =====
The download of the zip file and the unzipping of it seems to trigger false positive alert from windows defender sometimes. This doesn't always happen and I have to find the cause of it.

Windows Defender will identify a supposed virus as ''Trojan:Script/Sabsik.FL.A!ml'' . It's a well known error for installer programmed that are unsigned. We do not yet have means to sign the installer unfortunately as this could cost several hundred dollars per year.

Please let us know if you run into this issue, and we'll keep working on trying to get that false positive to stop showing up.

===== For developers of the Installer =====
I'll try to list here what's needed here in order to compile the Installer.

===== Requirement =====

* Rust SDK (Download here)

=== Manual Installation ===
You can also install everything manually. For detailed instructions, please see the relevant pages:

[[Getting Started - Diamond Edition]]

[[Getting Started - Diamond Edition on Linux]]

[[Getting Started - Enhanced Edition]]

Getting Started

2025-05-13T13:26:19Z

Fiery Imp: Added details

Welcome to Sinfar. Unlike most other servers of Neverwinter Nights, Sinfar uses a lot of custom features that are required before you can truly connect. Below you will find all the necessary information to log in and have fun whether you're on Diamond Edition (1.69) with Windows or Linux or if you're using Enhanced Edition.

=== Automatic Installer ===
You can download the Sinfar installer here: https://git.sinfar.net/Fiery_Imp/sinfar-installer

The installer works for both Diamond Edition and EE on Windows, for Linux and Mac users, or if you prefer to not use the installer, please see the manual installation process below.

==== Sinfar Installer ====
Thank you for your interest in the SinfarInstaller, this installer works for both the EE and Diamond edition of Neverwinter Nights.

For any question, you can ask FieryImp on the Sinfar Discord server, or leave a comment in the issues section available on thedownload page.

===== Feedback =====
Please give us feedback about your experience with the SinfarInstaller, whether you think something can be improved to give a smoother experience, or if you run into any kind of issues. Our goal is to make Sinfar as easy as possible to install for new players or old players alike when installing sinfar on a new system.

You may leave feedback in the "Issue" section above, or contact FieryImp on discord directly for immediate questions.

===== For regular users =====
Using the installer is easy, click on the download link below, download the file, unzip it, launch, and follow the instruction!

===== Download links =====
All files are hosted by us.

* [https://git.sinfar.net/Fiery_Imp/sinfar-installer/releases/download/2.0.0/sinfar-installer.zip Download installer 2.0.0]

===== Anti-virus false positive =====
The download of the zip file and the unzipping of it seems to trigger false positive alert from windows defender sometimes. This doesn't always happen and I have to find the cause of it.

Windows Defender will identify a supposed virus as ''Trojan:Script/Sabsik.FL.A!ml'' . It's a well known error for installer programmed that are unsigned. We do not yet have means to sign the installer unfortunately as this could cost several hundred dollars per year.

Please let us know if you run into this issue, and we'll keep working on trying to get that false positive to stop showing up.

===== For developers of the Installer =====
I'll try to list here what's needed here in order to compile the Installer.

===== Requirement =====

* Rust SDK (Download here)

=== Manual Installation ===
You can also install everything manually. For detailed instructions, please see the relevant pages:

[[Getting Started - Diamond Edition]]

[[Getting Started - Diamond Edition on Linux]]

[[Getting Started - Enhanced Edition]]

Getting Started

2025-05-13T13:22:32Z

Fiery Imp: Updated the description that was copied from Gitea to remove typos, also added a direct dowload link

Welcome to Sinfar. Unlike most other servers of Neverwinter Nights, Sinfar uses a lot of custom features that are required before you can truly connect. Below you will find all the necessary information to log in and have fun whether you're on Diamond Edition (1.69) with Windows or Linux or if you're using Enhanced Edition.

=== Automatic Installer ===
You can download the Sinfar installer here: https://git.sinfar.net/Fiery_Imp/sinfar-installer

The installer works for both Diamond Edition and EE on Windows.

==== Sinfar Installer ====
Thank you for your interest in the SinfarInstaller, this installer works for both the EE and Diamond edition of Neverwinter Nights.

For any question, you can ask FieryImp on the Sinfar Discord server, or leave a comment in the issues section available on thedownload page.

===== Feedback =====
Please give us feedback about your experience with the SinfarInstaller, whether you think something can be improved to give a smoother experience, or if you run into any kind of issues. Our goal is to make Sinfar as easy as possible to install for new players or old players alike when installing sinfar on a new system.

You may leave feedback in the "Issue" section above, or contact FieryImp on discord directly for immediate questions.

===== For regular users =====
Using the installer is easy, click on the download link below, download the file, unzip it, launch, and follow the instruction!

===== Download links =====
All files are hosted by us.

* [https://git.sinfar.net/Fiery_Imp/sinfar-installer/releases/download/2.0.0/sinfar-installer.zip Download installer 2.0.0]

===== Anti-virus false positive =====
The download of the zip file and the unzipping of it seems to trigger false positive alert from windows defender sometimes. This doesn't always happen and I have to find the cause of it.

Windows Defender will identify a supposed virus as ''Trojan:Script/Sabsik.FL.A!ml'' . It's a well known error for installer programmed that are unsigned. We do not yet have means to sign the installer unfortunately as this could cost several hundred dollars per year.

Please let us know if you run into this issue, and we'll keep working on trying to get that false positive to stop showing up.

===== For developers of the Installer =====
I'll try to list here what's needed here in order to compile the Installer.

===== Requirement =====

* Rust SDK (Download here)

=== Manual Installation ===
You can also install everything manually. For detailed instructions, please see the relevant pages:

[[Getting Started - Diamond Edition]]

[[Getting Started - Diamond Edition on Linux]]

[[Getting Started - Enhanced Edition]]

Custom Emote

2024-01-02T14:43:44Z

Fiery Imp:

== Description ==
Custome emote token with a specific animation and phenotype can be created to be easily reusable. This allows you to access certain emotes that are necessarily accessible with the animation menu.

== The command ==
'''!CE:SET [CUSTOM NAME]'''

Then there are different parameters that can be added to that command that will be applied to the token

'''ANIM [ANIM ID] [PHENOTYPE ID]''' (Required)

'''MOVE''' (TODO with more detail)

'''DELAY''' (TODO wtih more detail)

'''FREEZE'''

'''UNFREEZE'''

'''FOLLOW'''

=== Example ===

'''!CE:SET HUG ANIM 29 0'''

Custom Emote

2024-01-02T14:43:19Z

Fiery Imp: Created page with "== Description == Custome emote token with a specific animation and phenotype can be created to be easily reusable. This allows you to access certain emotes that are necessarily accessible with the animation menu. == The command == '''!CE:SET [CUSTOM NAME]''' Then there are different parameters that can be added to that command that will be applied to the token '''ANIM [ANIM ID] [PHENOTYPE ID]''' (Required) MOVE (TODO with more detail) DELAY (TODO wtih more d..."

== Description ==
Custome emote token with a specific animation and phenotype can be created to be easily reusable. This allows you to access certain emotes that are necessarily accessible with the animation menu.

== The command ==
'''!CE:SET [CUSTOM NAME]'''

Then there are different parameters that can be added to that command that will be applied to the token

'''ANIM [ANIM ID] [PHENOTYPE ID]''' (Required)

MOVE (TODO with more detail)

DELAY (TODO wtih more detail)

FREEZE

UNFREEZE

FOLLOW

=== Example ===

'''!CE:SET HUG ANIM 29 0'''

Event System

2023-12-14T15:33:04Z

Fiery Imp:

== OUTDATED ==
This page is outdated, instead check [[Variable Based Events|Variable based events]]

== OUTDATED ==
The way to get an event parameter has been standardized... now instead of calling functions from inc_x_events or getting local variable, parameters are stored in an array:

They can be obtained all at once with the '''GetEventParams()''' function or one by one, here are all functions to deal with the new events system:

Code: Select all

<syntaxhighlight>
int GetEventParamInt(int nParamIndex);

object GetEventParamObject(int nParamIndex);

string GetEventParamString(int nParamIndex);

float GetEventParamFloat(int nParamIndex);

effect GetEventParamEffect(int nParamIndex);

array GetEventParamArray(int nParamIndex);

dictionary GetEventParamDictionary(int nParamIndex);

location GetEventParamLocation(int nParamIndex);

vector GetEventParamVector(int nParamIndex);

array GetEventParams();

int GetEventParamType(int nParam);

int GetEventParamCount();

void BypassEvent();

void SetEventResultInt(int nResult);

void SetEventResultObject(object oResult);

void SetEventResultString(string sResult);

void SetEventResultFloat(float fResult);

void SetEventResultEffect(effect eResult);

void SetEventResultArray(array aResult);

void SetEventResultDictionary(dictionary dResult);

void SetEventResultVector(vector vResult);

void SetEventResultLocation(location lResult);

void RunEvent(string sScript, object oTarget, array aParams);

int RunEventInt(string sScript, object oTarget, array aParams);

object RunEventObject(string sScript, object oTarget, array aParams);

string RunEventString(string sScript, object oTarget, array aParams);

float RunEventFloat(string sScript, object oTarget, array aParams);

effect RunEventEffect(string sScript, object oTarget, array aParams);

array RunEventArray(string sScript, object oTarget, array aParams);

dictionary RunEventDictionary(string sScript, object oTarget, array aParams);

vector RunEventVector(string sScript, object oTarget, array aParams);

location RunEventLocation(string sScript, object oTarget, array aParams);
</syntaxhighlight>

And the reference for most existing events:

<syntaxhighlight lang="text">
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type

pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object
</syntaxhighlight>
[[Category:Builders Tools]]

Variable Based Events

2023-12-14T15:23:08Z

Fiery Imp: more events

Those events will run only run for a specific object so they are optimal and should be your preferred way to register an event.

=== Registering / Unregistering a variable Event ===
As you can guess, it is using local variables, for example:
[[File:Variable based 20190311-000047.png]]

Will cause the myerf_useitem script to be called when the item on which the variable is set is used.

You can also register multiple script to the same event:
[[File:Variable based 20190311-001248.png]]

With the variables above, all scripts (myerf_useitem, myerf_useitem2, myerf_useitem3 and myerf_useitem4) will run when the item is used.

You can register / unregister a variable event dynamically with the following functions:
<syntaxhighlight lang="c">
void RegisterVariableEvent(object oObject, string sEvent, string sScript, int bNoByPass=FALSE);
void UnregisterVariableEvent(object oObject, string sEvent, string sScript);
</syntaxhighlight>

=== Accessing the Parameters ===
# The registered scripts will run in the same context as the calling script so for example: <code>EVENT_USE</code> is called by [https://nwn.sinfar.net/res_nss_edit.php?name=pc_ev_useitem pc_ev_useitem] so you can still get the item with <code>GetEventParamObject(0)</code>.
# A variable event can also have its own parameters, they can be accessed with the following functions: <syntaxhighlight lang="c">
array GetCurrentVariableEventParams();
</syntaxhighlight>
# You can get the object on which the variable event was registered (it may not be the caller) and the currently running variable event (in case that you decide to register the same script to many events) with the following functions: <syntaxhighlight lang="c">object GetCurrentVariableEventTarget();
string GetCurrentVariableEvent();</syntaxhighlight>

=== Creating / Running a Variable Based Event ===
You can trigger a variable event on an object by calling one of those functions:
<syntaxhighlight lang="c">
int RunVariableEvent(object oObject, string sEvent);
int RunVariableEventWithParams(object oObject, string sEvent, array aParams);
</syntaxhighlight>
They will return TRUE if the <code>BypassVariableEvent()</code> was calling during the execution of one of the registered scripts.

=== List of events ===
More information here for now (to be merged here most likely): [[Event System]]<syntaxhighlight lang="text">
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type

pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object

EVENT_EQUIP
object oItem = GetPCItemLastEquipped();
object oPC = GetPCItemLastEquippedBy();

EVENT_UNEQUIP
object oItem = GetPCItemLastUnequipped();
object oPC = GetPCItemLastUnequippedBy();

EVENT_ACQUIRE
todo

EVENT_ATTACKROLL
todo
</syntaxhighlight>
[[Category:Builders Tools]]
[[Category:Sinfar Supporters]]

Variable Based Events

2023-12-14T15:19:55Z

Fiery Imp: Adde equip and unequip event

Those events will run only run for a specific object so they are optimal and should be your preferred way to register an event.

=== Registering / Unregistering a variable Event ===
As you can guess, it is using local variables, for example:
[[File:Variable based 20190311-000047.png]]

Will cause the myerf_useitem script to be called when the item on which the variable is set is used.

You can also register multiple script to the same event:
[[File:Variable based 20190311-001248.png]]

With the variables above, all scripts (myerf_useitem, myerf_useitem2, myerf_useitem3 and myerf_useitem4) will run when the item is used.

You can register / unregister a variable event dynamically with the following functions:
<syntaxhighlight lang="c">
void RegisterVariableEvent(object oObject, string sEvent, string sScript, int bNoByPass=FALSE);
void UnregisterVariableEvent(object oObject, string sEvent, string sScript);
</syntaxhighlight>

=== Accessing the Parameters ===
# The registered scripts will run in the same context as the calling script so for example: <code>EVENT_USE</code> is called by [https://nwn.sinfar.net/res_nss_edit.php?name=pc_ev_useitem pc_ev_useitem] so you can still get the item with <code>GetEventParamObject(0)</code>.
# A variable event can also have its own parameters, they can be accessed with the following functions: <syntaxhighlight lang="c">
array GetCurrentVariableEventParams();
</syntaxhighlight>
# You can get the object on which the variable event was registered (it may not be the caller) and the currently running variable event (in case that you decide to register the same script to many events) with the following functions: <syntaxhighlight lang="c">object GetCurrentVariableEventTarget();
string GetCurrentVariableEvent();</syntaxhighlight>

=== Creating / Running a Variable Based Event ===
You can trigger a variable event on an object by calling one of those functions:
<syntaxhighlight lang="c">
int RunVariableEvent(object oObject, string sEvent);
int RunVariableEventWithParams(object oObject, string sEvent, array aParams);
</syntaxhighlight>
They will return TRUE if the <code>BypassVariableEvent()</code> was calling during the execution of one of the registered scripts.

=== List of events ===
More information here for now (to be merged here most likely): [[Event System]]<syntaxhighlight lang="text">
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type

pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object

EVENT_EQUIP
object oItem = GetPCItemLastEquipped();
object oPC = GetPCItemLastEquippedBy();
EVENT_UNEQUIP
object oItem = GetPCItemLastUnequipped();
object oPC = GetPCItemLastUnequippedBy();
</syntaxhighlight>
[[Category:Builders Tools]]
[[Category:Sinfar Supporters]]

Standardized aura script

2023-12-14T12:43:33Z

Fiery Imp: Added list of VFX link

{{DISPLAYTITLE:Aura standardized script}}

== Information ==
Script name: '''lat_stand_aura'''

Associated variables

* AURA_ID
* AURA2_ID
* AURA3_ID
* AURA4_ID
* AURA5_ID

=== How to use ===
[[File:Onusepowerselfonlyunlimuse.png|thumb|319x319px]]
Item needs the following property (see image on the right)

The script name must be set in EVENT_USE according to the [[Variable Based Events|Variable based event system]].

The script can support up to 5 VFX, to add a VFX, give the ID of desired VFX in the associated variable mentioned in the information section.

'''Its important to set all the AURA_ID variable to -1, otherwise they are set to 0 by default and you will get a blue glow VFX on the character.'''

The list of VFX can be found here : https://www.sinfar.net/visualeffects.html

== Alternative ==
As an alternative, you can make your own aura script if needed with the help of the '''lat_inc_aura''' include script.

Here is an example on how to use it. The resulting script must of course be applied the same as the standardized script described above.<syntaxhighlight lang="c++" line="1">
#include "lat_inc_aura"

//Standardized Aura Script to be applied on EVENT_USE

void main()
{
//These variable are available as well
// oItem = the item which triggered the script
// oPC = the character possessing oItem

//Nothing else need to be added before this, check with FieryImp or Badger if you think you need something before the if.

if(LAT_CanApplyAura())
{
//This where you set the VFX, the only function call you will ever need to make here is LAT_SetVFX(int iVfxId);
LAT_SetVFX(0); //Call this as many time as needed to set a VFX where 0 can be replaced with teh vfx id of your choice.
}
}
</syntaxhighlight>
[[Category:Builders Tools]]
{{DEFAULTSORT:Aura standardized script}}

Standardized aura script

2023-12-14T12:30:56Z

Fiery Imp: Fixed errors

{{DISPLAYTITLE:Aura standardized script}}

== Information ==
Script name: '''lat_stand_aura'''

Associated variables

* AURA_ID
* AURA2_ID
* AURA3_ID
* AURA4_ID
* AURA5_ID

=== How to use ===
[[File:Onusepowerselfonlyunlimuse.png|thumb|319x319px]]
Item needs the following property (see image on the right)

The script name must be set in EVENT_USE according to the [[Variable Based Events|Variable based event system]].

The script can support up to 5 VFX, to add a VFX, give the ID of desired VFX in the associated variable mentioned in the information section.

'''Its important to set all the AURA_ID variable to -1, otherwise they are set to 0 by default and you will get a blue glow VFX on the character.'''

== Alternative ==
As an alternative, you can make your own aura script if needed with the help of the '''lat_inc_aura''' include script.

Here is an example on how to use it. The resulting script must of course be applied the same as the standardized script described above.<syntaxhighlight lang="c++" line="1">
#include "lat_inc_aura"

//Standardized Aura Script to be applied on EVENT_USE

void main()
{
//These variable are available as well
// oItem = the item which triggered the script
// oPC = the character possessing oItem

//Nothing else need to be added before this, check with FieryImp or Badger if you think you need something before the if.

if(LAT_CanApplyAura())
{
//This where you set the VFX, the only function call you will ever need to make here is LAT_SetVFX(int iVfxId);
LAT_SetVFX(0); //Call this as many time as needed to set a VFX where 0 can be replaced with teh vfx id of your choice.
}
}
</syntaxhighlight>
[[Category:Builders Tools]]
{{DEFAULTSORT:Aura standardized script}}

Standardized aura script

2023-12-12T15:46:12Z

Fiery Imp:

{{DISPLAYTITLE:Aura standardized script}}

== Information ==
Script name: '''lat_stand_vfx'''

Associated variables

* AURA1_ID
* AURA2_ID
* AURA3_ID
* AURA4_ID
* AURA5_ID

=== How to use ===
[[File:Onusepowerselfonlyunlimuse.png|thumb|319x319px]]
Item needs the following property (see image on the right)

The script name must be set in EVENT_USE according to the [[Variable Based Events|Variable based event system]].

The script can support up to 5 VFX, to add a VFX, give the ID of desired VFX in the associated variable mentioned in the information section.

'''Its important to set all the AURA_ID variable to -1, otherwise they are set to 0 by default and you will get a blue glow VFX on the character.'''

== Alternative ==
As an alternative, you can make your own aura script if needed with the help of the '''lat_inc_aura''' include script.

Here is an example on how to use it. The resulting script must of course be applied the same as the standardized script described above.<syntaxhighlight lang="c++" line="1">
#include "lat_inc_aura"

//Standardized Aura Script to be applied on EVENT_USE

void main()
{
//These variable are available as well
// oItem = the item which triggered the script
// oPC = the character possessing oItem

//Nothing else need to be added before this, check with FieryImp or Badger if you think you need something before the if.

if(LAT_CanApplyAura())
{
//This where you set the VFX, the only function call you will ever need to make here is LAT_SetVFX(int iVfxId);
LAT_SetVFX(0); //Call this as many time as needed to set a VFX where 0 can be replaced with teh vfx id of your choice.
}
}
</syntaxhighlight>
[[Category:Builders Tools]]
{{DEFAULTSORT:Aura standardized script}}

Standardized aura script

2023-12-12T15:45:14Z

Fiery Imp:

Standardized aura script

2023-12-12T15:43:56Z

Fiery Imp: Added category

== Information ==
Script name: '''lat_stand_vfx'''

Associated variables

* AURA1_ID
* AURA2_ID
* AURA3_ID
* AURA4_ID
* AURA5_ID

=== How to use ===
[[File:Onusepowerselfonlyunlimuse.png|thumb|319x319px]]
Item needs the following property (see image on the right)

The script name must be set in EVENT_USE according to the [[Variable Based Events|Variable based event system]].

The script can support up to 5 VFX, to add a VFX, give the ID of desired VFX in the associated variable mentioned in the information section.

'''Its important to set all the AURA_ID variable to -1, otherwise they are set to 0 by default and you will get a blue glow VFX on the character.'''

== Alternative ==
As an alternative, you can make your own aura script if needed with the help of the '''lat_inc_aura''' include script.

Here is an example on how to use it. The resulting script must of course be applied the same as the standardized script described above.<syntaxhighlight lang="c++" line="1">
#include "lat_inc_aura"

//Standardized Aura Script to be applied on EVENT_USE

void main()
{
//These variable are available as well
// oItem = the item which triggered the script
// oPC = the character possessing oItem

//Nothing else need to be added before this, check with FieryImp or Badger if you think you need something before the if.

if(LAT_CanApplyAura())
{
//This where you set the VFX, the only function call you will ever need to make here is LAT_SetVFX(int iVfxId);
LAT_SetVFX(0); //Call this as many time as needed to set a VFX where 0 can be replaced with teh vfx id of your choice.
}
}
</syntaxhighlight>
[[Category:Builders Tools]]

User:Fiery Imp

2023-12-12T15:42:02Z

Fiery Imp: Created page with "An imp."

An imp.

Standardized aura script

2023-12-12T15:40:48Z

Fiery Imp: /* Alternative */

Standardized aura script

2023-12-12T15:31:52Z

Fiery Imp:

== Information ==
Script name: '''lat_stand_vfx'''

Associated variables

* AURA1_ID
* AURA2_ID
* AURA3_ID
* AURA4_ID
* AURA5_ID

=== How to use ===
[[File:Onusepowerselfonlyunlimuse.png|thumb|319x319px]]
Item needs the following property (see image on the right)

The script name must be set in EVENT_USE according to the [[Variable Based Events|Variable based event system]].

The script can support up to 5 VFX, to add a VFX, give the ID of desired VFX in the associated variable mentioned in the information section.

'''Its important to set all the AURA_ID variable to -1, otherwise they are set to 0 by default and you will get a blue glow VFX on the character.'''

== Alternative ==
As an alternative, you can make your own aura script if needed with the help of the '''lat_inc_aura''' include script.

Here is an example on how to use it.<syntaxhighlight lang="c++" line="1">
#include "lat_inc_aura"

//Standardized Aura Script to be applied on EVENT_USE

void main()
{
//These variable are available as well
// oItem = the item which triggered the script
// oPC = the character possessing oItem

//Nothing else need to be added before this, check with FieryImp or Badger if you think you need something before the if.

if(LAT_CanApplyAura())
{
//This where you set the VFX, the only function call you will ever need to make here is LAT_SetVFX(int iVfxId);
LAT_SetVFX(0); //Call this as many time as needed to set a VFX where 0 can be replaced with teh vfx id of your choice.
}
}
</syntaxhighlight>

Standardized aura script

2023-12-12T15:29:26Z

Fiery Imp:

Standardized aura script

2023-12-12T15:27:53Z

Fiery Imp:

Standardized aura script

2023-12-12T02:24:23Z

Fiery Imp: /* How to use */

Standardized aura script

2023-12-12T02:22:12Z

Fiery Imp: Created page with "== Information == Script name : '''lat_stand_vfx''' Association variables * AURA1_ID * AURA2_ID * AURA3_ID * AURA4_ID * AURA5_ID === How to use === 319x319px Item needs the following property (see image on the right)"

== Information ==
Script name : '''lat_stand_vfx'''

Association variables

* AURA1_ID
* AURA2_ID
* AURA3_ID
* AURA4_ID
* AURA5_ID

=== How to use ===
[[File:Onusepowerselfonlyunlimuse.png|thumb|319x319px]]
Item needs the following property (see image on the right)

File:Onusepowerselfonlyunlimuse.png

2023-12-12T02:21:32Z

Fiery Imp:

Variable Based Events

2023-12-11T15:20:05Z

Fiery Imp: Added list of events

Event System

2023-12-09T17:02:02Z

Fiery Imp:

The way to get an event parameter has been standardized... now instead of calling functions from inc_x_events or getting local variable, parameters are stored in an array:

They can be obtained all at once with the '''GetEventParams()''' function or one by one, here are all functions to deal with the new events system:

Code: Select all

<syntaxhighlight>
int GetEventParamInt(int nParamIndex);

object GetEventParamObject(int nParamIndex);

string GetEventParamString(int nParamIndex);

float GetEventParamFloat(int nParamIndex);

effect GetEventParamEffect(int nParamIndex);

array GetEventParamArray(int nParamIndex);

dictionary GetEventParamDictionary(int nParamIndex);

location GetEventParamLocation(int nParamIndex);

vector GetEventParamVector(int nParamIndex);

array GetEventParams();

int GetEventParamType(int nParam);

int GetEventParamCount();

void BypassEvent();

void SetEventResultInt(int nResult);

void SetEventResultObject(object oResult);

void SetEventResultString(string sResult);

void SetEventResultFloat(float fResult);

void SetEventResultEffect(effect eResult);

void SetEventResultArray(array aResult);

void SetEventResultDictionary(dictionary dResult);

void SetEventResultVector(vector vResult);

void SetEventResultLocation(location lResult);

void RunEvent(string sScript, object oTarget, array aParams);

int RunEventInt(string sScript, object oTarget, array aParams);

object RunEventObject(string sScript, object oTarget, array aParams);

string RunEventString(string sScript, object oTarget, array aParams);

float RunEventFloat(string sScript, object oTarget, array aParams);

effect RunEventEffect(string sScript, object oTarget, array aParams);

array RunEventArray(string sScript, object oTarget, array aParams);

dictionary RunEventDictionary(string sScript, object oTarget, array aParams);

vector RunEventVector(string sScript, object oTarget, array aParams);

location RunEventLocation(string sScript, object oTarget, array aParams);
</syntaxhighlight>

And the reference for most existing events:

<syntaxhighlight lang="text">
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type

pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object
</syntaxhighlight>

Event System

2023-12-09T17:01:34Z

Fiery Imp:

The way to get an event parameter has been standardized... now instead of calling functions from inc_x_events or getting local variable, parameters are stored in an array:

They can be obtained all at once with the GetEventParams() function or one by one, here are all functions to deal with the new events system:

Code: Select all

<syntaxhighlight>
int GetEventParamInt(int nParamIndex);

object GetEventParamObject(int nParamIndex);

string GetEventParamString(int nParamIndex);

float GetEventParamFloat(int nParamIndex);

effect GetEventParamEffect(int nParamIndex);

array GetEventParamArray(int nParamIndex);

dictionary GetEventParamDictionary(int nParamIndex);

location GetEventParamLocation(int nParamIndex);

vector GetEventParamVector(int nParamIndex);

array GetEventParams();

int GetEventParamType(int nParam);

int GetEventParamCount();

void BypassEvent();

void SetEventResultInt(int nResult);

void SetEventResultObject(object oResult);

void SetEventResultString(string sResult);

void SetEventResultFloat(float fResult);

void SetEventResultEffect(effect eResult);

void SetEventResultArray(array aResult);

void SetEventResultDictionary(dictionary dResult);

void SetEventResultVector(vector vResult);

void SetEventResultLocation(location lResult);

void RunEvent(string sScript, object oTarget, array aParams);

int RunEventInt(string sScript, object oTarget, array aParams);

object RunEventObject(string sScript, object oTarget, array aParams);

string RunEventString(string sScript, object oTarget, array aParams);

float RunEventFloat(string sScript, object oTarget, array aParams);

effect RunEventEffect(string sScript, object oTarget, array aParams);

array RunEventArray(string sScript, object oTarget, array aParams);

dictionary RunEventDictionary(string sScript, object oTarget, array aParams);

vector RunEventVector(string sScript, object oTarget, array aParams);

location RunEventLocation(string sScript, object oTarget, array aParams);
</syntaxhighlight>

And the reference for most existing events:

<syntaxhighlight lang="text">
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type

pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object
</syntaxhighlight>

Event System

2023-12-09T17:00:31Z

Fiery Imp:

The way to get an event parameter has been standardized... now instead of calling functions from inc_x_events or getting local variable, parameters are stored in an array:

They can be obtained all at once with the GetEventParams() function or one by one, here are all functions to deal with the new events system:

Code: Select all

<syntaxhighlight>
int GetEventParamInt(int nParamIndex);

object GetEventParamObject(int nParamIndex);

string GetEventParamString(int nParamIndex);

float GetEventParamFloat(int nParamIndex);

effect GetEventParamEffect(int nParamIndex);

array GetEventParamArray(int nParamIndex);

dictionary GetEventParamDictionary(int nParamIndex);

location GetEventParamLocation(int nParamIndex);

vector GetEventParamVector(int nParamIndex);

array GetEventParams();

int GetEventParamType(int nParam);

int GetEventParamCount();

void BypassEvent();

void SetEventResultInt(int nResult);

void SetEventResultObject(object oResult);

void SetEventResultString(string sResult);

void SetEventResultFloat(float fResult);

void SetEventResultEffect(effect eResult);

void SetEventResultArray(array aResult);

void SetEventResultDictionary(dictionary dResult);

void SetEventResultVector(vector vResult);

void SetEventResultLocation(location lResult);

void RunEvent(string sScript, object oTarget, array aParams);

int RunEventInt(string sScript, object oTarget, array aParams);

object RunEventObject(string sScript, object oTarget, array aParams);

string RunEventString(string sScript, object oTarget, array aParams);

float RunEventFloat(string sScript, object oTarget, array aParams);

effect RunEventEffect(string sScript, object oTarget, array aParams);

array RunEventArray(string sScript, object oTarget, array aParams);

dictionary RunEventDictionary(string sScript, object oTarget, array aParams);

vector RunEventVector(string sScript, object oTarget, array aParams);

location RunEventLocation(string sScript, object oTarget, array aParams);
</syntaxhighlight>

And the reference for most existing events:

<syntaxhighlight lang="text" line="1">
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type
</syntaxhighlight>pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object

Event System

2023-12-09T16:58:00Z

Fiery Imp: added code block

The way to get an event parameter has been standardized... now instead of calling functions from inc_x_events or getting local variable, parameters are stored in an array:

They can be obtained all at once with the GetEventParams() function or one by one, here are all functions to deal with the new events system:

Code: Select all

<syntaxhighlight>
int GetEventParamInt(int nParamIndex);

object GetEventParamObject(int nParamIndex);

string GetEventParamString(int nParamIndex);

float GetEventParamFloat(int nParamIndex);

effect GetEventParamEffect(int nParamIndex);

array GetEventParamArray(int nParamIndex);

dictionary GetEventParamDictionary(int nParamIndex);

location GetEventParamLocation(int nParamIndex);

vector GetEventParamVector(int nParamIndex);

array GetEventParams();

int GetEventParamType(int nParam);

int GetEventParamCount();

void BypassEvent();

void SetEventResultInt(int nResult);

void SetEventResultObject(object oResult);

void SetEventResultString(string sResult);

void SetEventResultFloat(float fResult);

void SetEventResultEffect(effect eResult);

void SetEventResultArray(array aResult);

void SetEventResultDictionary(dictionary dResult);

void SetEventResultVector(vector vResult);

void SetEventResultLocation(location lResult);

void RunEvent(string sScript, object oTarget, array aParams);

int RunEventInt(string sScript, object oTarget, array aParams);

object RunEventObject(string sScript, object oTarget, array aParams);

string RunEventString(string sScript, object oTarget, array aParams);

float RunEventFloat(string sScript, object oTarget, array aParams);

effect RunEventEffect(string sScript, object oTarget, array aParams);

array RunEventArray(string sScript, object oTarget, array aParams);

dictionary RunEventDictionary(string sScript, object oTarget, array aParams);

vector RunEventVector(string sScript, object oTarget, array aParams);

location RunEventLocation(string sScript, object oTarget, array aParams);
</syntaxhighlight>

And the reference for most existing events:
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type?

pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object

Event System

2023-12-09T16:53:01Z

Fiery Imp: Created page with "The way to get an event parameter has been standardized... now instead of calling functions from inc_x_events or getting local variable, parameters are stored in an array: They can be obtained all at once with the GetEventParams() function or one by one, here are all functions to deal with the new events system: Code: Select all int GetEventParamInt(int nParamIndex); object GetEventParamObject(int nParamIndex); string GetEventParamString(int nParamIndex); float Ge..."

The way to get an event parameter has been standardized... now instead of calling functions from inc_x_events or getting local variable, parameters are stored in an array:

They can be obtained all at once with the GetEventParams() function or one by one, here are all functions to deal with the new events system:

Code: Select all

int GetEventParamInt(int nParamIndex);

object GetEventParamObject(int nParamIndex);

string GetEventParamString(int nParamIndex);

float GetEventParamFloat(int nParamIndex);

effect GetEventParamEffect(int nParamIndex);

array GetEventParamArray(int nParamIndex);

dictionary GetEventParamDictionary(int nParamIndex);

location GetEventParamLocation(int nParamIndex);

vector GetEventParamVector(int nParamIndex);

array GetEventParams();

int GetEventParamType(int nParam);

int GetEventParamCount();

void BypassEvent();

void SetEventResultInt(int nResult);

void SetEventResultObject(object oResult);

void SetEventResultString(string sResult);

void SetEventResultFloat(float fResult);

void SetEventResultEffect(effect eResult);

void SetEventResultArray(array aResult);

void SetEventResultDictionary(dictionary dResult);

void SetEventResultVector(vector vResult);

void SetEventResultLocation(location lResult);

void RunEvent(string sScript, object oTarget, array aParams);

int RunEventInt(string sScript, object oTarget, array aParams);

object RunEventObject(string sScript, object oTarget, array aParams);

string RunEventString(string sScript, object oTarget, array aParams);

float RunEventFloat(string sScript, object oTarget, array aParams);

effect RunEventEffect(string sScript, object oTarget, array aParams);

array RunEventArray(string sScript, object oTarget, array aParams);

dictionary RunEventDictionary(string sScript, object oTarget, array aParams);

vector RunEventVector(string sScript, object oTarget, array aParams);

location RunEventLocation(string sScript, object oTarget, array aParams);

And the reference for most existing events:
pc_ev_useitem -> item:EVENT_USE
self : user
p0: item
p1: target object
p2: target position
p3: sub type?

pc_ev_examine -> player:EVENT_EXAMINE
self: player
p0: target object

pc_ev_attack -> attacker:EVENT_ATTACK
self: attacker
p0: target object
p1: attack type

pc_ev_trap -> target:EVENT_TRAP
self: trapper
p0: type
p1: target object
p2: target position

pc_ev_firetrap -> target:EVENT_FIRETRAP
self: trigger
p0: type
p1: target

pc_ev_useskill -> user:EVENT_USESKILL, user:EVENT_USESKILL_%skill%
self: user
p0: skill
p1: target
p2: target position
p3: item

pc_ev_usefeat -> user:EVENT_USEFEAT, user:EVENT_USEFEAT_%feat%
self: user
p0: feat
p1: target
p2: target position

pc_ev_togglemode -> user:EVENT_TOGGLEMODE, user:EVENT_TOGGLEMODE_%mode%
self: user
p0: mode

pc_ev_castspell -> caster:EVENT_CASTING, caster:EVENT_CASTING_%spell%
self: caster
p0: target
p1: target position
p2: spell
p3: meta magic
p4: class
p5: is instant

ilr_canequip -> item:EVENT_CAN_EQUIP
self: equip by
p0: item

pc_ev_setlike setter:EVENT_SETLIKE
self: setter
p0: type
p1: target

pc_ev_party
self: setter
p0: type
p1: target

pc_ev_pickpocket
self: attacker
p0: target object

Multi-pages book system

2023-12-04T01:03:48Z

Fiery Imp: Created page with " = What does it do? = Basically allows to create a book item that has many pages, to "flip" the pages, the player uses the book and it opens up a conversation with options. Upon clicking on an option the description of the book is changed in accordance with the selected option. = How does it work? = == Script == == Item == == 2DA =="

= What does it do? =
Basically allows to create a book item that has many pages, to "flip" the pages, the player uses the book and it opens up a conversation with options. Upon clicking on an option the description of the book is changed in accordance with the selected option.

= How does it work? =

== Script ==
== Item ==
== 2DA ==

File:Téléchargement.png

2023-11-24T13:20:47Z

Fiery Imp: The Colonel Atlassian

== Summary ==
The Colonel Atlassian

Main Page

2023-11-24T12:24:36Z

Fiery Imp: /* Getting started */

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

Fiery Imp was here. [ugly spray painted tag]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]