Plan for adding monthly campaigns?

[Era-Lusiphur]

What's the battle plan on adding monthly campaigns for servers to activate to imitate those seen on retail? Some of these are exclusive sources of items or trusts, some modify EXP/CP, drop rates, add additional drop slots, etc.

[claywar]

I was actually thinking about that today after seeing your PR for Allied Notes. I think perhaps separate modules to enable or disable might be the way, and just override a global table

[zach2good]

+1 for separate modules that can be enabled/disabled with a flag, or that flag can be hooked up to specific times

[Kayanesa]

Is that something that come back the same after a year. Possibly with a few addition from year to year? If so a main table of things they share and another table for each month could work.

[claywar]

These don't seem to follow a specific pattern to make for scheduled events. I would assume this is an item we should break out and allow for server operators to determine on their own.

[Era-Lusiphur]

These monthly Adventurer Campaigns.

[Kayanesa]

I see it's more random than I thought and 2 campaign can be active same time. Different module does seems good so they can be mixed and matched.

[Era-Lusiphur]

Yeah, retail can run a number of them at the same time and usually does. When we're implementing or refactoring things, we're running across parameters where they account for these campaigns now and sometimes it's a shame to just leave a note and not go the extra step to set it up properly.

[Kayanesa]

I personally would love if the setting where moved to the main lua. Setting like these one
local loginCampaignYear = 2022
local loginCampaignMonth = 3
local loginCampaignDay = 18
local loginCampaignDuration = 23 -- Duration is set in Earth days (Average is 23 days)

[TeoTwawki]

just automated start and stop? I'm not sure we'd specify it that way, but we could probably have something to kick it off and end it without having to have admin attention every time

[claywar]

For those modules, perhaps we could leverage a db table to apply and track durations. Something where a command could say, "Enable this module for X days"

[Kayanesa]

WIP so I'm not sure how it would look like but making sure we can control/enable the wanted campaign directly from main.lua as to not force admin to go to different file. The example I gave

local loginCampaignYear = 2022
local loginCampaignMonth = 3
local loginCampaignDay = 18
local loginCampaignDuration = 23

is what I had to go change manually to make a campaign start on my server. Automated start and stop sounds great but I can live with manual one.

[TeoTwawki]

Should not need to track year. your campaigns just need to know when to start and stop. Retail has a monthly maint they do their swap out during, and while we don't necessarily have to do that I don't think we should dedicate a db table to enabling it we otherwise wouldn't have or make even more variable for it either. We're not queuing up multiple months worth of events or auto setting new login items for people each month, we're providing a as retail accurate framework as possible for people to customize. We should limit our scope here.

Also lets be careful not to mix up the monthly random-ass campaigns with the login campaign. Login campaign is a much simpler beast, just need a start day and stop day - thats it. Up to server operators to swap items while its down.

[TeoTwawki]

thats my 2 cents.