Basic Navi Guide

To get started we’re going to copy from an existing mod Man that you can grab from keristero.xyz. You can download the file to resources/mods/players then run the game. The game should extract the zip to a folder with the same name.

Here is what it looks like on my computer:

You can ignore the forms folder for now.

Some of the changes you’ll want to do is a simple asset swap for the images such as icon.png, and preview.png. The other image assets such as battle.png and overworld.png come with animation files. If your navi is not the exact same size you’ll need to modify the animation file or create a new one using keristero’s animation tool

For adjusting basic attributes we’ll need to edit the entry.lua file that comes with the mod, but don’t worry you won’t need any programming experience to do this. There are just a few bits of text and numbers that you may want to modify.

Here is Man’s entry.lua with the parts we’ll be working with highlighted:

A brief overview of what you’re looking at:

• package_init contains basic information about the navi and paths to textures and animations used outside of battle. You won’t need to change any of the paths as they have pretty general names.

• player_init contains everything that matters to battles. (you can ignore everything below “--simple megaman form” as this guide is not going over forms, and we’ll be removing it later in the guide)

First, you’ll want to adjust the package id for your navi. You can find that in the package_init function:

The package id is what’s used to track your last used navi in your save file, as well as identify your package for whitelists. If you use the same package id as another package, the engine will only load one of the packages using the same id.

To keep your package unique from other modders, you’ll want to include a prefix that is unique to yourself for the package id. Some people use email, a website domain they own, or another form of account. Here I’m using my discord account as com.discord.Konstinople#7692 with player added on to avoid conflicting with the possibility of a Man chip or enemy.

Other than package id, you should only really change the special description in package_init:

Here is what the entry looks like after modification, you shouldn’t see too much of a difference:

Now we’ll mess with some battle attributes. We can find that in player_init:

We’re going to skip forms in this guide so you can just remove the mega form and forms folder:

This is what your player_init should look like now.

There are only a few lines you’ll want to mess with, we can start with the name and element:

You can find more info on available elements in the battle docs

For health, you should likely avoid modifying it. Most players are balancing navis to work with 1000 HP and additional HP modification can come through NCP.

The height attribute depends on your sprite it’s used for some visual effects in the game. You can use the Debug ncp to make sure it’s perfect:

The last remaining piece you’ll want to mess with is the charge position and color.

This is how it currently looks:

A quick example modification to base_charge_color and set_charge_position:

The format for colors is “Color.new(red, green, blue, alpha)” with every component being a number from 0 to 255. The color we changed the charge to is a solid pure green.