Path Archives

[Odin]

Were the Archives and all the early threads of POV lost or is the error, when trying to access them, something that can be fixed?

[Tierney]

If I remember correctly, this happened the last time that the server migration happened and that was fixed previously.

Both David and Josh have been busy with bringing both of the games together, so it's very likely that it's on their list of things to do and they haven't gotten to it, but they will. I looked at the bug thread for this particular issue and it's been marked as a , which is a minor bug and fixable.

[Alexandrea]

Well actually, I marked it B. As per these guidelines;

SPECIAL LABELS
Special labels are usually placed on thread topics by us (developers and bug mods), but you can do it yourself if you have a good understanding of the bug fixing process.

"[a]" -- Urgent bug. Interruption to gameplay, or something which makes it harder to play the game for one or more characters.

"" -- Not urgent. Something which might be annoying, but doesn't interrupt or ruin gameplay for anyone.

"[c]" -- Minor. Probably something to be added to the list of known minor bugs. Superficial bugs or bugs which are easy to avoid are given this category.

"[x]" -- Not a bug. Soon to be archived.

"[f]" -- Fixed. Soon to be archived, allowing time though for testing.

"[?]" -- This label is given when the developers or bug mods have looked at the bug and require more people to give feedback or information. Can be used with other labels.

"" -- This means that the bug is unconfirmed. Some bugs are reported due to various mistakes, and we don't usually go digging through the code looking for a bug until either multiple people have confirmed it, or it's easy to identify as a bug.

"[h]" -- This means that the bug is either hard to fix, or we can't work out what's causing it, despite our best efforts. These bugs will usually take longer to get fixed.

So although it doesn't interfere with gameplay... at least on the grid, it isn't as minor as say a C which would be a display issue.

And since I'm who marked it B, we can't even know for a 100% sure that it was seen by The Dev Dudes. And while the last time they were restored without any issue, it seems like (imo) it was resolved quite a bit more quickly.... which is why I've been bumping the bug thread for the issue.

[Amalea]

Might be better off PM'ing the guys and asking if they've seen it.