Oh, no enforced monospace on card display? Will be fixed in a moment.
I've noticed this issue with the Pearls board as well.
It's possible one of the devs will see your post and fix it, as they did with Skye's, but you shouldn't rely on it.
To be fair, the exact same thing can be said about the bug system.
If you bug something, it will get fixed. It might not get fixed straight away since we have internal prioritisation, but it will get handled.
It might get fixed, sometimes requiring resubmitting the same bug, either because it was deleted without being resolved, or it was dismissed without a resolution after initially being acknowledged that it was a bug and assigned priority. Both have frequently been my experience since the new bug system went in. So I'm not surprised that number dropped so quickly.
That being said, when things do get fixed it's always a wonderful feeling, and very much appreciated.
A bug being assigned a category or priority doesn't mean it is necessarily a bug, that just prioritises when the coders will look at it to determine if it is a bug or not and fix if need be.
Categorisation is done by the entire team, so as to take some of the organisational labour off the small group of coders we have.
As an example: high priority means this looks really really bad, the coders will look at it as fast as they can. Typo means this is someone reporting a typo, we'll look at it when we next clear typos. Coder typo means this is someone reporting a typo in something that will require a coder to investigate and fix (system messages, combat messages, and the like). Categorisation has nothing to do with the legitimacy of a report.
It's great to have such insight into how that works, and allows for more understanding and patience. In particular I speak towards instances such as this where it appears that whomever is verifying whether or not something warrants a fix, is maybe being a little too hasty to dismiss things:
Sent By: Achaea on 28 Apr 2019, 02:58
Your bug report #3911 (detail: The Hunger seaspell is not listed on SEASPELLS LIST.) - has been assigned to low priority.
Sent By: Achaea on 04 May 2019, 10:15
Your bug report (detail: The Hunger seaspell is not listed on SEASPELLS LIST.) - has been removed because it is not a bug (usually meaning that this is the way things are intended to be). Please accept our apologies for any inconvenience or misunderstanding that may be involved.
Sent By: Achaea on 04 May 2019, 11:52
Your bug report (detail: The Seaspell HUNGER is not listed on the SEASPELLS LIST. For no explained reason, when I submitted this recently it was classified to Low Priority, and then a few days later dismissed as 'not being a bug', with no explanation. Please correct this.) - has been fixed.
I was just mentioning it as it seems to be happening with increased frequency, so thought it might be worth review and consideration.
Oh, no enforced monospace on card display? Will be fixed in a moment.
I've noticed this issue with the Pearls board as well.
It's possible one of the devs will see your post and fix it, as they did with Skye's, but you shouldn't rely on it.
To be fair, the exact same thing can be said about the bug system.
If you bug something, it will get fixed. It might not get fixed straight away since we have internal prioritisation, but it will get handled.
It might get fixed, sometimes requiring resubmitting the same bug, either because it was deleted without being resolved, or it was dismissed without a resolution after initially being acknowledged that it was a bug and assigned priority. Both have frequently been my experience since the new bug system went in. So I'm not surprised that number dropped so quickly.
That being said, when things do get fixed it's always a wonderful feeling, and very much appreciated.
Oh, those were fixed bugs. Auto deleted ones don't show up in that counter. I could probably get that number, but will require some digging since its not readily available.
@Makarios I know that significant changes are sometimes announced via the Announce and Classleads newsboards. Would it be worth consideration towards having a running changelog accessible from the site so that people could stay apprised of all the work and fixes being done? Even if a lot of them are minor, I'm sure a lot of people wouldn't mind knowing, and would offer a better understanding of just how much work goes on behind the curtain.
I see a lot of common trees in the realm, such as oak, maple, and elm. There are some trees I haven't seen yet, such as tamarack and jack pine. Would I be risking insanity if I mentioned tree types I haven't seen yet? Or does the tree biodiversity of Achaea approximately match Earth's?
I always viewed it as a generality so you knew what was around, with different climates naturally having different tree types as they adapted to the environment.
That said, you would probably catch a rash of hell from people for using Earth trees you don't see in-game. Maybe if you couched it in "my father once told me of a tree like this but with...yadda yadda". But expect some people to still complain. But stay tuned. You will see a new tree in game soon(tm).
Swear to glob we've become the City of Evil Puns, lately.
And I love too Be still, my indelible friend That love soon might end You are unbreaking And be known in its aching Though quaking Shown in this shaking Though crazy Lately of my wasteland, baby That's just wasteland, baby
I saw in the classleads posts that sword and shield denizen damage got increased - is it comparable to 2h for hunting now?
Would the extra tankiness granted by a SoA be worth the decrease in damage over 2h with the increase?
I'm pretty sure that even with the buff sword and shield still lags behind the other specialisations. You can get the main benefit of the SoA - the ability to absorb attacks - as the other specs, even if it is slightly more expensive, so it's not really worth it. Knight is generally tanky enough as it is between fullplate, weathering to boost health, resistance for magical damage, and class-specific resistances.
So I now have two skills called Pierce, the Battlerage one and the Jewellery one. I have my Nexus buttons set to default (so pierce @tar), but now when I hit the button it tells me I need a piecing needle. If I type it manually, like "pierce ogre", it uses the Battlerage ability appropriately. If I type the ID number, like "pierce 55555", it wants the needle again.
Is there a way I can have the button refer to the Battlerage Pierce specifically? Or otherwise have an alias or reflex that doesn't depend on me typing the name each time?
So I now have two skills called Pierce, the Battlerage one and the Jewellery one. I have my Nexus buttons set to default (so pierce @tar), but now when I hit the button it tells me I need a piecing needle. If I type it manually, like "pierce ogre", it uses the Battlerage ability appropriately. If I type the ID number, like "pierce 55555", it wants the needle again.
Is there a way I can have the button refer to the Battlerage Pierce specifically? Or otherwise have an alias or reflex that doesn't depend on me typing the name each time?
Not sure if this will work, but try 'battlerage pierce @tar". Either way, sounds like might be a bug.
The website fades out/gets darker and "locks" (can't click links or highlight text, etc) when I scroll down. Is that just me? Suggestions for fixing? On Firefox 67.0.4
Comments
Coder wise this is partially the case - I'm paid, we have two other coders that are volunteers (they are awesome).
Categorisation is done by the entire team, so as to take some of the organisational labour off the small group of coders we have.
As an example: high priority means this looks really really bad, the coders will look at it as fast as they can. Typo means this is someone reporting a typo, we'll look at it when we next clear typos. Coder typo means this is someone reporting a typo in something that will require a coder to investigate and fix (system messages, combat messages, and the like). Categorisation has nothing to do with the legitimacy of a report.
Your bug report #3911 (detail: The Hunger seaspell is not listed on SEASPELLS LIST.) - has been assigned to low priority.
Sent By: Achaea on 04 May 2019, 10:15
Your bug report (detail: The Hunger seaspell is not listed on SEASPELLS LIST.) - has been removed because it is not a bug (usually meaning that this is the way things are intended to be). Please accept our apologies for any inconvenience or misunderstanding that may be involved.
Sent By: Achaea on 04 May 2019, 11:52
Your bug report (detail: The Seaspell HUNGER is not listed on the SEASPELLS LIST. For no explained reason, when I submitted this recently it was classified to Low Priority, and then a few days later dismissed as 'not being a bug', with no explanation. Please correct this.) - has been fixed.
Oh, those were fixed bugs. Auto deleted ones don't show up in that counter. I could probably get that number, but will require some digging since its not readily available.
Soon (tm).
That said, you would probably catch a rash of hell from people for using Earth trees you don't see in-game. Maybe if you couched it in "my father once told me of a tree like this but with...yadda yadda". But expect some people to still complain. But stay tuned. You will see a new tree in game soon(tm).
Results of disembowel testing | Knight limb counter | GMCP AB files
That love soon might end You are unbreaking
And be known in its aching Though quaking
Shown in this shaking Though crazy
Lately of my wasteland, baby That's just wasteland, baby
Would the extra tankiness granted by a SoA be worth the decrease in damage over 2h with the increase?
Results of disembowel testing | Knight limb counter | GMCP AB files