Updating from 1.x to 2.0

For owners of nc_party 1.x, nc_rift 1.x or nc_dungeon 1.x. In 2.0 the three resources use two shared resources: nc_bridge (library: framework, inventory, notices, themes, EXP, death, party) and nc_assets (one pack of peds, weapons, animations, effects, interiors and sounds, with no duplicate files). If you do not update, the 1.x versions keep working on their own.

Before you start

• Stop the server: nc_assets starts only with the server, never with players inside (the clients crash).
• Make a copy of the old folders, above all of the files you changed: config.lua, config/, config_custom.lua, locales/, open/ and data/editor/ (dungeons and presets saved by the editor).

What to remove

The simplest way: delete the old nc_party, nc_rift and nc_dungeon folders, copy the new ones whole and then put your values back (section "Your config files"). The old asset folders must leave resources/ (deleted or moved out): if your resources start from a group folder (for example ensure [nc]), removing the ensure line is not enough.

What to add

• nc_bridge: it is in every 2.0 pack. If you have several copies keep only one folder, the newest (the version line of its fxmanifest.lua): old functions stay.
• nc_assets: it is in every 2.0 pack, with the part that pack needs. If you own several packs, copy all the nc_assets folders into the same nc_assets folder: files with the same name are identical and the fxmanifest.lua is the same.
• The new nc_party, nc_rift and nc_dungeon 2.0 (only the ones you bought).

Ensure order

In server.cfg, after the framework and the inventory. Keep only the lines of the resources you have:

ensure nc_bridge
ensure nc_assets
ensure nc_party
ensure nc_rift
ensure nc_dungeon

nc_bridge and the three resources can be restarted whenever you want; nc_assets only with the server.

Your config files

• Put the values you had changed into the new files, instead of copying the old files over them: 2.0 has new options (for example Config.Bridge, read by nc_bridge: framework, notices, theme; see the nc_bridge configuration guide).
• 1.x configs still work, the old names are translated when they load:
  • nc_dungeon: nc_dungeon_* models, weapons, animations and effects become the original names of nc_assets (warning in the server console: write the new names and the warning goes away);
  • graphic style: followRift / followParty still work, the new name is Config.UI.follow;
  • nc_rift: the AddItem / AddMoney functions used in your open/ files still work (they now go through nc_bridge).
• Your own sounds go into nc_assets/web/sounds (the config values stay the same, for example 'zombie/aggro_1.ogg').
• Your own mods (peds, weapons, animations) stay in a separate resource started before the NC resources.

Check

1. Start the server and look at the console.
2. No red warning from nc_assets about the old asset resources (it shows 5 seconds after start if one is still running).
3. nc_rift prints config check: 0 warning(s); nc_dungeon no [nc_dungeon][WARN] config: line apart from the warnings about old names.
4. Join and try: /party, an nc_rift mob, the dungeon NPC.