Map Release Schedule #5
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: StrafesNET/maps-service#5
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The "Algorithm" for the release schedule is located here. All it does it release the map 1 week from now to the second.
My favourite idea so far is to use a cron job which runs once a month at the beginning of every month, and releases all "pending release" maps starting at the beginning of the month after. So when the job runs on April 1st, the maps it adds to the release schedule appear starting March 1st and ending March 31st. This means that as long as maps keep being made, there is always maps for at least one month, and the longest you have to wait for maps to release in the worst case is 2 months (for the last map to release, right after the job runs). Alternatively, this may be better to do seasonally, i.e. 3 months at a time with up to a 6 month wait.
Here is a striking diagram explaining the process, with the black ticks representing the release periods:
I am not a programmer who does programming things so I will write about the non-program-y bits
The energy for new maps is still there and very present during AoRs, but I think the current model of dripfeeding maps to the playerbase is not ideal. When you have a map releasing every 1-2 days, there is some activity on the map for that day, but there is little community hype, and most maps are seldom forgotten after release. A map update just means new (sometimes old) maps being added to the daily dripfeed. So I think a weekly, biweekly, or even a monthly release schedule is inherently better, and maps would be released in large enough batches to get people excited. Another thing I would change is revivifying the old idea of making a lot of maps immediately available to the playerbase. In an ideal world around 1/3 or 1/2 of the new maps are instantly released, while the remaining maps are occasionally dripfed to the playerbase in batches.
I like the idea of releasing a percent right away. Thinking about 3 month release grouping, I find release labels such as "Surf Fall 2025 Maps" "Bhop Summer 2025 Maps" intensely appealing, makes things really simple and provides a good work period and then deadline for map making. Can even have a dedicated web page to view release history / upcoming releases.
i like releasing a good amount of the maps right away but the problem will be in deciding which get released, and having to explain to the mappers why their map wasnt released with the rest of them. or just make it random i guess.
i think most people do want maps to release faster though, almost every new map dies in a couple days once everyone has played it once or twice and it just becomes a normal map again. I would rather have each map release faster and then there be no backlog by the time the next aor happens. faster releases means people playing more new maps sooner and more map makers happy that they dont have to wait ages, and running out of new maps to constantly play leaves a gap and makes people want to play the new maps more after aor
Another proposal has come from discussion on discord. Map releaser gets a frontend interface usable by the map admin. Pick # of maps to release instantly (slider), release interval for remaining maps (every 3 days, 7 days etc.), create specialized release dates for select holiday maps. Click big release button, releaser runs.
Validation: Release Scheduleto Map Release Schedule