Guild Wars 2

Topic says it all. Thank you.

Mark Katzbach.9084:

This feature already exists. See the up and down arrows next to my name? When there is another staff post in a thread, the arrow will not be grayed out and will be clickable. You can use the arrows to navigate to the next and previous staff posts within a thread.

That’s true, but you still have to seek a dev post first by scanning through all the postings. There are numerous topics with multiple pages, and finding any dev post at all can be quite cumbersome from time to time.

Hence, I ‘d say the OP’s suggestion has its merit.

Also, when viewing a topic, there is no visible indication whether this topic contains a dev post at all. I kind of remember that there was such an indicator when the game was in beta stage, and I wish it was still around.

~MRA

Mark Katzbach.9084:

This feature already exists. See the up and down arrows next to my name? When there is another staff post in a thread, the arrow will not be grayed out and will be clickable. You can use the arrows to navigate to the next and previous staff posts within a thread.

Like the previous poster said, you have to find a red post first. Perhaps there should be something on the first page (or top of the by thread name) that goes to the first red/dev post. Especially when you click on the post in the dev tracker, and it goes to the first unread post instead (if you’ve already looked in that thread before).

Mark Katzbach.9084:

This feature already exists. See the up and down arrows next to my name? When there is another staff post in a thread, the arrow will not be grayed out and will be clickable. You can use the arrows to navigate to the next and previous staff posts within a thread.

Pity is doesn’t work because direct linking to posts is bugged. As I’ve said about this before:

That is only a consequence of the real problem: The forum doesn’t know what page of a thread a post is actually on. Go to any thread that has a second parge. Go to the last post on the first page. Open the direct link to that post in a new tab/window. It will go for page 2.

The longer the thread, the worse the problem. The most extreme is the Ascended items threadnaught, where posts on page 222 try to open page page 243.

I suspect that the function which determines which page a post is on thinks there are less posts per page than there actually are. A simple typo, or maybe a case where the number was changed but the coder forgot to update both variables.
But also a hint of bad coding practices. It shows that the posts per page number is stored in two separate variables. Since it’s always going to be the same for all code that needs it, it should be stored in a single variable that all the relevant code can access.

I’m still waiting for someone from ANET to acknowledge that this problem exists.