• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

UE errata

The email from Paizo announcing the errata came out at 4:27PM PST yesterday, and this was posted at 8:35AM PST today - that means that just over an hour of an 8-5 workday has elapsed since the errata was announced before the first ETA post about that errata. We need time to read the errata and evaluate what needs to be changed before we can generate an ETA, and an hour is not a reasonable time span for that request.

Also, please remember that Paizo's releases are on the last Wednesday of the month, which is next week, and that there's a player companion, a high-crunch campaign setting book, and an adventure path to finish for this month, so your request that we divert time from the release came in during the final run up to that release.
 
Mathias said:
The email from Paizo announcing the errata came out at 4:27PM PST yesterday, and this was posted at 8:35AM PST today - that means that just over an hour of an 8-5 workday has elapsed since the errata was announced before the first ETA post about that errata. We need time to read the errata and evaluate what needs to be changed before we can generate an ETA, and an hour is not a reasonable time span for that request.

Also, please remember that Paizo's releases are on the last Wednesday of the month, which is next week, and that there's a player companion, a high-crunch campaign setting book, and an adventure path to finish for this month, so your request that we divert time from the release came in during the final run up to that release.
Click to expand...

Please don't take it that way, its not a request to divert. I was just trying to get a feel for the normal/average response time for the changes to be applied. I wasn't even looking for an official response, more of a it normally takes two weeks to apply an errata, or similar "normal". Since this is the first real errata that I have seen while using HL I was just wondering.
 
One of the perks of the job is the ability to pick our own hours. I tend to start around 10 and go to 7-8 depending on what I am working on. When we're under a big crunch time I can sometimes do a lot of overtime. I think one week I did something like, 90 hours of work (including working saturday and sunday). 16 hours coding will seriously fray your sanity. I don't recommend it at all.
 
But in response to the OP, we usually like to get any Errata included in the next monthly release, but Paizo doesn't give us any forewarning for this stuff and this one happened to fall in a pretty busy month and close to the release day. May not make it into next week's release, but we'll see.
 
Aaron said:
One of the perks of the job is the ability to pick our own hours. I tend to start around 10 and go to 7-8 depending on what I am working on. When we're under a big crunch time I can sometimes do a lot of overtime. I think one week I did something like, 90 hours of work (including working saturday and sunday). 16 hours coding will seriously fray your sanity. I don't recommend it at all.
Click to expand...
That is really nice in many ways if you can pick your hours. I would love to start later in the day as I am NOT a morning person.

I couldn't even pull 16hr coding days anymore. Getting too old! Damn youngsters. :p
 
You must log in or register to reply here.
Back
Top