Use the lib to create a stacked bar chart for every day showing the number of runs and their outcome

https://www.chartjs.org/

After an import the world and the corresponding logs should be compressed and moved to an archive location.

The world loader service must be able to use the normal server directory as well as the compressed archives seamlessly, so an outside caller can use it without thinking about where and how the world is stored.

Insert manual input into a run to

Override

• Finish Time
• Outcome

Extend

• Youtube Link
• Speedrun Link

Adjust the time of the End Split so that the overall runtime matches the manual input. Check for validity obviously.

Since mojang auto deletes older logs of the day during a speedrun session with more than seven attempts the logs will be copied after every run. This new location must be considered from now on when parsing logs.

Find a way to access the level dat nbt data to extract the seed of the world and attach it to the run.

Add an action in operations tab to delete content of temp folder
Show the size of the temp folders

• check for current renderings
• check for current imports

When determining the Playtime of the world check the start time of the next run if the logs are not sufficient.

Detect if a world is currently running and if so, don't even try to import it.

Next to every timing of a run section in the run details page show how that time relates to other times of the same section.

Show the percentile compared to every other run

Add action to operations tab to scan for map renderings and check if they are linked correctly.
If not linked correctly, it must be repaired

Create a model for each player where data of every run can be aggregated. This results in a new area on the website where this stats can be viewer for each player.

Use overviewer.py to generate maps from the dimensions.
Use nginx to make the output accessible via minecraft.thefipster.com/overviewer/{worldname}/index.html
Create link and attach to dimension info of run
Find a way to handle the data amount by discarded the last generated or oldest world or something like that
The request must be async because it will take some time to generate.
There must be a way to determine if the render is completed and only then the link should be attached

Ingest server.properties file to show basic infos about the server

Use this lib to create a funnel chart showing the outcome of every run

https://github.com/greghub/funnel-graph-js

Use the lib to create a box plot of the time distribution per run section

https://plotly.com/javascript/box-plots/#fully-styled-box-plot

Make a detail page for the attempts card on the landing page.

It should contain a chart with the relative outcomes based on today (last day, last week, last month, last year

and it should contain a chart with the outcomes by period. Every day, week, month, year

Probably a stacked line/area chart is suitable for the later while a table view for the first outcomes makes for sense at the current moment.

Search for worldname in log and use that as the starting point.

Extract meta information from the imports on a sync operation. This should include outcomes, finish times, split times

This could be achieved by using decoraters to hook into the sync process.
For every aspect a seperate repository should be used

Showing server start, joins, set time, advancements etc.

Landing Page

• Remove display of sessions

Finished Runs

• Only show Position, Time ago, Finish time and maybe Icons if fits

Other Runs

• Only show Index, Time ago, Outcome and maybe Icons if fits

Run

• Remove raw events and locations

Analyze Outcome of the game an categorize into Error, Discarded, Started, Nether and so on

Read and ingest the achievement files from a world.

Allow to delete rendering

Each run should have a unique attempt number. This can also be used as the id for the run instead of the worldname.