Discord: https://discordapp.com/invite/MBxsJBQ

README

Download los and zones files, put it in your server folder

los: https://drive.google.com/open?id=1mmajzgHVQIVi2isdXloFmkBY7dsGnkBf

zones: https://drive.google.com/open?id=1RAVHzU0ADr08HHuU5fdaJ6Ddn1MtE8fw

nuget packages

• If you get an error compiling, complaining about NLog, you may need to force the VS package manager to get NLog. Do the following :
  • install-package NLog
    • Make sure you select the Default Project = Launcher and WarConsoleLauncher
    • If that fails, uninstall-package Nlog, and the install-package NLog
  • install-package Evolve
• You can also look to use Update-Package -reinstall (which should update all the packages for you)

Building and running

• There are really a couple of 'modes' of developing / debugging the solution.
  • Debug the servers
    • Set the solution to start multiple projects (AccountCacher, LauncherServer, LobbyServer, WorldServer). This will start these 4 projects in debug mode. You can then connect the client to these.
  • Debug DB changes
    • You can do this in combination with 'Debug the Servers', but might be better(?) to just run the Servers up without the debugger attached and connect with a Client to see if the changes made work as expected.
  • Debug the Launcher
    • Set the solution to start a single project, Launcher.

Implementing new Battlefield Objectives

Current system uses database file and commands under the name of "Battlefront". The battlefront incorporates all things involving oRvR. The previous system was instanced PQs that were then used for a larger calculation. It looks as if the new system generates some type of 'resources'.

The following two tables work in tandem. If you delete an entry for one, or change something out of bounds for the array, the world server will crash. BOs are currently only spawning in game when a zone is declared a battlefront.

battlefront_objects battlefront_objectives

The .GO SPAWN object 'Battlefield Objective' should not be confused with code/DB driven battlefronts. This object is only a nuetral flag that has been named 'Battlefield Objective'.

T1 and T4 Progression - July 2018

The T1 and T4 Battlefront progressions have been re-written.

T1 is designed to rotate from Emp -> Dwarf -> Elf. This should look and act in a similar fashion to the current T1 flow.

T4 is based upon starting at Praag. Locking that zone will take you to CW or Reik, depending upon the winner of Praag. If that same side locks CW or Reik, the pairing itself will lock and the campaign will move to Dwarf (TM). If the other realm locks, they will return to Praag.

Simple rewards have been added (mail items), this section is not complete.

The process will repeat through Dwarf and into Elf, until one side locks all 9 zones and then the system will reset and you will be back at Praag.

Commands of interest : .campaign status (gives you the status of the T4 region). .campaign setvictorypoints <#> <#> (Number of victory points, and the realm to assign) .campaign lockpairing <#> <#> (locks the current pairing. # - [1 Order, 2 Dest], # - [0 - no reward, 1 - reward]) .campaign advancepairing <#> <#> (moves the pairing # - [1 Order, 2 Dest], # - tier (1 or 4)) .campaign UpdateRegionCaptureStatus (forces a refresh of the progression [ie the client's map]) .campaign SetRegionCaptureStatus <#> <#> (this one is complex # - forces the region progression to change to the first parameter. The first parameter is a list of 9 digits, the first three representing Dwarf, the next three Empire and the final three Elf. Within each of these pairings is the region, eg where 1 is lock to Order, 2 is lock to Dest, 0 is unlocked. So 111111110 is lock all to order except Caledor. # - Open and make active the region Id defined by the number). An example is .campaign SetRegionCaptureStatus 111111110 7

Note : Lockpairing and Advancepairing are only two steps in the 'flip' process. They should only be used by developers (ie dont use them in Production). For testing, it is better to use .campaign setvictorypoints <#> <#>, as this emulates holding BOs/keep takes equivalent to the number of VP.

If it all goes haywire, reset by .campaign SetRegionCaptureStatus 102102102 2