Mirage Editor Backlog

21/12/2019 done:

* add save/publish options to the navbar (under the Project menu)

to do:

* implement auto-save -> each 15 minutes, save a separate copy of the project; write a script to remove saves older than a week (?)

* update the guide

there won't be any window to browse all those automatic saves just yet. The priority is to implement auto-save, so that no work is lost (e.g. in case where an editor update screws something up). If somebody reports his work is gone, I'll retrieve the previous auto-save manually.

23/12/2019 done:

* rewrote the entire project management code, it's much simpler now and I'm no longer ashamed of it.

* added server side project-integrity checks

* implemented auto-save -> each 15 minutes, save a separate copy of the project

24/12/2019 done:

* spent some time on the guide

27/12/2019 done:

* optimized saved db size -> it now contains only data that was directly modified

* added all item details to the backend -> it can be now served to the editor, but we still have to prepare all the fancy windows, layout and stuff

(except for armors and weapons, those will come last)

28/12/2019 done:

* added interface for editing potions, damage and defense charms, mounts, flyers, and basic quest items

02/02/2020 done:

* added interface for editing all items except for weapons and armors (those will come much later)

* display item description (those are located in client files, somewhere...)

note: currently we have those tokens like "^00ffff" in item description which should translate to some color. It can be read as "till the end of the line, use some color". They will be parsed in the editor at some point, but I also need to make GUI to set it and I don't want to spend time on that now - we've got other priorities.

4/01/2020 to do:

* try to integrate a project into the actual game

I did some bugfixing today.

12/01/2020 done:

* projects will only auto-save if there were some changes done (the revision counter in the project list won't go up by itself anymore)

* editing read-only projects will constantly give you a warning notification (not intrusive, but noticeable - it says your changes won't be saved anywhere)

* added version number to the bottom left corner of the screen

* loading a project from a pwmirage.com/map/?db=* url will now remove the ?db=* part from the url, hence showing you the actual project you loaded, not the one in URL

* cleaned up the map code

25/01/2020 done:

* implemented the new db format -> New database format in the editor and its possible benefits

* auto-save interval lowered from 15 mins to 5 mins

All changes in the editor are now saved incrementally, which means there will no longer be a case where your data is somehow lost -> if you remove all your work from a project and press save, the server will still keep your previous data. Basically speaking, a project is now just a log of your actions. One log entry could be adding an NPC, then another entry - removing the very same NPC.

There's no longer a need to "load" a project. Each project has a unique URL for editing, which also means you can modify multiple projects at once with multiple browser tabs.

26/01/2020 done:

* added server side validation for published projects

* published projects are now automatically approved on the forum. This also applies to any comments. Projects still need to be reviewed ofc, but the content is visible to everyone immediately

13/02/2020 done:

* merged content is now visible to everyone in the editor, even without creating a project

08/03/2020 done:

* exported all quest data (it's available at https://github.com/pwmirage/editor/tree/master/data/quests )

* setup local test environment

9-10/03/2020 done:

* design the quest editor

11/03/2020 done:

* initial mockup of the quest editor

12/03/2020 done:

* Fixed syntax in the quest files on github -> https://github.com/pwmirage/ed…3cb6d33eb7721e70bbe6e935b

* Loaded actual quest in the editor -> The boxes are no longer hardcoded

* Added lines connecting the boxes (eventually they'll come from the connecting dots, not the top-left corner of the box itself)

13/03/2020 done:

* connect dots instead of top-left corners of the boxes

* connect answers with their subsequent dialogues (requires parsing some additional data)

to do:

* allow adding/removing additional dialogues and answers (probably with a right click menu)

14/03/2020 done:

* allow switching between "accept", "cant-accept", "cant-finish", and "finish" dialogues (top menu)

* parse sub-quests and allow switching between them (bottom menu)

15/3/2020 done:

* migrate database of all original PW items/npcs/recipes/etc to github -> This greatly reduces traffic on pwmirage.com https://github.com/pwmirage/editor/tree/master/data/base

* remove the server-side service for obtaining detailed item data. All static information is now stored on github

to do:

* serialize changes in the editor to usable data

* start implementing left panel with quest details (briefing text, basic requirements - lvl range, rep, culti, class)

16/03/2020 done:

* add project cache to the editor -> instead of applying all merged patches 1-by-1 on project load, use a single predefined blob of all merged patches: https://github.com/pwmirage/version/tree/master/cache

17/03/2020 done:

* automate creating cache blobs. They're now generated automatically on project publish, then pushed to github when project is merged.