Difference between revisions of "Modding"

From Isleward Wiki
Jump to navigation Jump to search
(added "close" measure to in-game events)
(fix redirect)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
= Modding =
+
#REDIRECT [[Modding:Main_Page]]
−
''Modding may refer to multiple things in [[Isleward]]. See [[Modding (disambiguation)]] for more information.''
 
−
 
 
−
{{wip}}
 
−
 
 
−
'''THIS ARTICLE IS VERY OUTDATED AND INCOMPLETE SINCE NOT MANY MODS HAVE BEEN MADE. ALWAYS CHECK THE CURRENT CODEBASE FIRST TO MAKE SURE THE INFORMATION IS CORRECT.'''
 
−
 
 
−
Isleward allows for server-side mods by dropping a "modpack" into the server source. A few tools are available to assist users with modding, such as the [[Sprite Editor]], [[Map Editor]], [[Tree Editor]], and [[Item Tooltip Generator]].
 
−
 
 
−
{{See also|Mod}}
 
−
 
 
−
== Running the Server ==
 
−
You can run an Isleward server on your own computer if you would like to make/play with mods, test the game, or run a private server.
 
−
 
 
−
First, you'll need to install [https://nodejs.org/en/download/ Node.JS] and NPM.
 
−
NPM should be included in the download linked above.
 
−
 
 
−
There are two ways to get the source code.
 
−
The first way uses [https://git-scm.com/downloads Git], a Source Control Management program.
 
−
The second way is to download the source files from the repository yourself, which doesn't require you to install another program but it is more difficult to update your server version later on.
 
−
 
 
−
'''Method 1:''' This way works best because you can run a single command to download the latest version without having to manually set up the files again.
 
−
Once you install [https://git-scm.com/downloads Git], navigate to the parent directory of where you want to install the server.
 
−
Run <code>git clone https://gitlab.com/Isleward/Isleward.git FOLDER</code>, replacing <code>FOLDER</code> with whatever you want to call the folder you are installing [[Isleward]] into.
 
−
After that, <code>cd</code> into <code>FOLDER/src/server</code>.
 
−
The server is now downloaded.
 
−
 
 
−
'''Method 2:''' This way doesn't require a download but is harder to maintain.
 
−
Open [https://gitlab.com/Isleward/isleward/ this page] in your browser.
 
−
Click on the download button and download the source in a format of your choice.
 
−
Extract the downloaded files into a directory you want to install [[Isleward]] into.
 
−
Navigate to <code>FOLDER/src/server</code>
 
−
 
 
−
Both methods will get you to the same place.
 
−
Make sure you are in <code>FOLDER/src/server</code> and run <code>npm install</code>.
 
−
If you installed Node.JS and NPM correctly, it should start installing.
 
−
Wait for it to install.
 
−
It should install everything it needs on its own without needing you to install other dependencies.
 
−
If you encounter other errors, try running it again with administrative permissions and try other basic troubleshooting problems.
 
−
The [[Isleward]] [https://discord.gg/0w9fgEmdtEpUESHK Discord] might also be able to help you with your problem.
 
−
 
 
−
Now that you have all the dependencies installed, you should be ready to go!
 
−
Run <code>node --expose-gc index.js</code> (in <code>FOLDER/src/server</code>) and you should see something like <pre>Server: ready
 
−
(M estuary): Ready
 
−
(M sewer): Ready
 
−
(M cave): Ready
 
−
(M tutorial): Ready</pre>
 
−
If you see something like that (zone names may be different), your server is running.
 
−
Head over to http://localhost:4000/ and you should see the game running!
 
−
 
 
−
You can change the message shown in the console (the <code>Server: ready</code> part) and the port that it runs on in <code>FOLDER/src/server/config/serverConfig.js</code>, the file should be pretty self-explanatory.
 
−
 
 
−
=== Using Mods ===
 
−
You can use a modpack by dropping it into the "mods" folder of the server source code.
 
−
 
 
−
== Events ==
 
−
A list of events available.
 
−
 
 
−
=== onAfterGetLayerObjects ===
 
−
=== onBeforeBuildLayerTile ===
 
−
=== onBeforeGetAnimations ===
 
−
=== onBeforeGetClasses ===
 
−
=== onBeforeGetDialogue ===
 
−
=== onBeforeGetEffect ===
 
−
First, look at this code snippet from the effect component (<code>src/server/components/effects.js</code>):
 
−
 
 
−
<pre>
 
−
var type = options.type[0].toUpperCase() + options.type.substr(1);
 
−
var result = {
 
−
    type: type,
 
−
    url: 'config/effects/effect' + type + '.js'
 
−
};
 
−
this.obj.instance.eventEmitter.emit('onBeforeGetEffect', result);
 
−
 
 
−
typeTemplate = require(result.url);
 
−
</pre>
 
−
 
 
−
It fires an event, in case a mod wants to modify the path which the effect is loaded from. Because the code allows us to mod this easily, we use (in our mod's <code>index.js</code>, bound to the event, of course):
 
−
 
 
−
<pre>
 
−
onBeforeGetEffect: function(data) {
 
−
    if(data.type == "newType") {
 
−
        data.url = 'mods/newTypeMod/newType.js'
 
−
    }
 
−
}
 
−
</pre>
 
−
 
 
−
Then, in our mod's <code>newType.js</code>:
 
−
 
 
−
<pre>
 
−
module.exports = {
 
−
    type: 'newType',
 
−
    events: {
 
−
        beforeTakeDamage: function(damage, source) {
 
−
            damage.failed = true;
 
−
           
 
−
            // have not tested whether we need this, probably do
 
−
            this.obj.instance.syncer.queue('onGetDamage', {
 
−
                id: this.obj.id,
 
−
                event: true,
 
−
                text: 'newType cancel'
 
−
            });
 
−
        }
 
−
    }
 
−
}
 
−
</pre>
 
−
 
 
−
This creates an example effect that cancels all damage and shows a message (mostly copied paraphrased from the ReflectDamage effect in the core codebase).
 
−
Be warned, this hasn't been tested yet, but in theory it should work.
 
−
 
 
−
=== onBeforeGetEventList ===
 
−
=== onBeforeGetFactions ===
 
−
=== onBeforeGetHerbConfig ===
 
−
=== onBeforeGetItemTypes ===
 
−
=== onBeforeGetMtxList ===
 
−
=== onBeforeGetQuests ===
 
−
=== onBeforeGetResourceList ===
 
−
=== onBeforeGetSkins ===
 
−
Called with an Object of all the skins. Each skin is its own Object that looks like this:
 
−
<pre>
 
−
'skin key': {
 
−
    name: 'Full Skin Name',
 
−
    sprite: [ 0, 0 ],
 
−
    class: 'wizard',
 
−
    spritesheet: 'optional path to spritesheet',
 
−
    default: true
 
−
}
 
−
</pre>
 
−
This will likely change in future updates, with the addition of Spirits and the removal of class-restricted skins.
 
−
 
 
−
=== onBeforeGetSpellsConfig ===
 
−
=== onBeforeGetSpellsInfo ===
 
−
=== onBeforeGetSpellTemplate ===
 
−
=== onBeforeGetZone ===
 
−
 
 
−
== Other Tips ==
 
−
<code>cpn</code> refers to a component.
 
−
 
 
−
<code>obj</code> refers to an object.
 
−
 
 
−
<code>ttl</code> is an object's "time to live." When it runs out, the object is destroyed.
 
−
 
 
−
== In-Game Event System Findings ==
 
−
A player is considered close to an event if:
 
−
 
 
−
* The events needed distance is -1 (marks the player as participating as well)
 
−
* The event doesn't have a needed distance
 
−
* The player is within the needed distance from any object that is part of the event (usually mobs spawned by the even)
 
−
* The player has already been marked as participating in the event (if you participate and leave, the event will still show up)
 
−
 
 
−
 
 
−
 
 
−
== Code Samples ==
 
−
Below are some code samples for common things to do in mods.
 
−
 
 
−
=== Only run on the main thread ===
 
−
<pre>
 
−
let isMapThread = !!process.send;
 
−
</pre>
 
−
If the variable is true, then it is a map thread, of course.
 
−
 
 
−
=== Add a new skin ===
 
−
In the mod's init:
 
−
<pre>
 
−
this.events.on('onBeforeGetSkins', this.onBeforeGetSkins.bind(this))
 
−
</pre>
 
−
The <code>onBeforeGetSkins</code> part:
 
−
<pre>
 
−
onBeforeGetSkins: function(skins) {
 
−
skins['renamed thief'] = {
 
−
name: 'Renamed Thief 1 Skin',
 
−
sprite: [ 6, 0 ],
 
−
class: 'thief',
 
−
default: true
 
−
}
 
−
}
 
−
</pre>
 
−
 
 
−
=== A component that saves ===
 
−
In <code>yourNewComponent.js</code>:
 
−
<pre>
 
−
module.exports = {
 
−
    type: 'killStats',
 
−
 
 
−
    kills: {},
 
−
 
 
−
    init: function (blueprint) {
 
−
        this.kills = blueprint.kills || {};
 
−
    },
 
−
 
 
−
    simplify: function (self) {
 
−
        if (!self)
 
−
            return null;
 
−
 
 
−
        return {
 
−
            type: 'killStats',
 
−
            kills: this.kills
 
−
        };
 
−
    },
 
−
 
 
−
    events: {
 
−
        afterKillMob: function (mob) {
 
−
            this.kills[mob.name] = (this.kills[mob.name] || 0) + 1;
 
−
        }
 
−
    }
 
−
};
 
−
</pre>
 
−
In your mod's index file:
 
−
<pre>
 
−
module.exports = {
 
−
name: 'Your New Mod',
 
−
 
 
−
init: function () {
 
−
this.events.on('onBeforeGetComponents', this.onBeforeGetComponents.bind(this));
 
−
},
 
−
 
 
−
onBeforeGetComponents: function (components) {
 
−
components.yourNewComponent = require('./yourNewComponent');
 
−
}
 
−
 
 
−
        // Need to add the kill counter component to the player somehow
 
−
}
 
−
</pre>
 
−
 
 
−
=== Fire an event on the client ===
 
−
<pre>
 
−
fireClientEvent = function (obj, event, data = {}) {
 
−
if (obj.socket)
 
−
obj.socket.emit('events', { [event]: [data] });
 
−
else
 
−
obj.instance.syncer.queue(event, data, [obj.serverId]);
 
−
}
 
−
</pre>
 
−
Call this helper function with the object to send to, the event to send, and the data of the event, and it will work on the main thread or the map threads.
 
−
 
 
−
<!-- i'm going to finish this later -->
 
−
<!-- === Give a player an item ===
 
−
<pre></pre> -->
 

Latest revision as of 01:45, 16 November 2018

Redirect to:

Retrieved from "https://wiki.isleward.com/index.php?title=Modding&oldid=3941"