Bug Reports - Version 7.1 closed?

[Unseelie]

Where should we be posting new bugs? The current bug thread is closed and has already moved to the second page.

Bug: Tactician (Fighter Archetype, UC) gives the text from the Cavalier Tactician ability instead of the modified text from the archetype. It otherwise appears to be implemented correctly.

Text Reads: "At 1st level, a cavalier receives a teamwork feat as a bonus feat. He must meet the prerequisites for this feat. As a standard action, the cavalier can grant this feat to all allies within 30 feet who can see and hear him. Allies retain the use of this bonus feat for 3 rounds plus 1 round for every two levels the cavalier possesses. The cavalier can use this ability once per day at 1st level, plus one additional time per day at 5th level and for every 5 levels thereafter."

Text Should Read: "At 5th level, a tactician gains this ability as the cavalier class feature (Advanced Player’s Guide 33). He may use this ability once per day at 5th level, plus one additional time for every five levels after 5th (to a maximum of four times at 20th level). If the tactician also has cavalier levels, these levels stack for determining the number of uses per day, and he can take the better progression. This ability replaces weapon training 1."

 

[Mathias]

There's a stickied post at the very top of this forum that tells you how to report bugs.

 

[Unseelie]

Sorry, thought that was an older sticky post so I didn't check it out. Might as well close this then.

 

[Enforcer84]

Closing time...one last call for Bug Reports so finish your message of errors...

 

[CorzatTheGray]

Is there a way to find what bugs have been reported to the new reporting management system and what the status is, whether it be in progress or complete?

I know that I may not find the bugs but I did follow the old thread to be aware of what others had found and if/how they had been resolved.

There at the tail-end of it when Aaron was reporting on what had been fixed was excellent IMO to just keep the general populace informed on what had been reported and tackled by you guys. Just a quick blurb to say "X problem is this... Check!... Fixed for next release!... Next..."

Just wondering...

 

[Mathias]

I want to, but before then, we need to edit our bug list. For example, if you saw a project in the list labeled "History Tracking", would you know what that meant?

I know what it means - history tracking is what we call the mechanism that the Shadowrun, CoC, Cortex, etc. files use to not only apply the changes they want to make, but record what made them. Implementing that would mean that if you moved your mouse over a skill's bonus, you'd get a report like this:

6 ranks: +6, class skill: +3, armor check penalty: -3 (studded leather armor: -1, medium encumbrance: -3), morale bonus: +2 (something: +1, something else: +2), trait bonus: +1 (some trait: +1)

(That's of course a huge project - everything in the entire Pathfinder system needs to have its script altered so that it records where the change came from as it applies its changes to other things).

(d20 & Pathfinder were written before that mechanism existed, so unlike the other game systems, where everything was created with history tracking in mind, in d20/Pathfinder, it requires a retrofit).

So, before we can publicize the bug tracker, I need to change the name and description of that project, and lots of others like it, in order to make it something our users can understand, not just something that uses so much jargon that only we can understand it (or something that only I can understand, because I wrote down a three word reminder of something I wanted to accomplish at some point).

I don't think that there will be enough time for that in the near future, but I would like to be able to find the time to do so at some point.

 

[CorzatTheGray]

I want to, but before then, we need to edit our bug list. For example, if you saw a project in the list labeled "History Tracking", would you know what that meant?

Let me start by saying that I understand what you're saying here.

I think you went out a few more steps in the process than what I was intending.

I was thinking along the lines of this from one of the last posts that Aaron made in the old closed thread.

The Race Vishkanyas from the Advanced Race Guide is not calculating DC for the Toxic ability correctly. It is adding the Con modifier, but not the 1/2 HD for the race.

Toxic: A number of times per day equal to his Constitution modifier (minimum 1/day), a vishkanya can envenom a weapon that he wields with his toxic saliva or blood (using blood requires the vishkanya to be injured when he uses this ability). Applying venom in this way is a swift action.

Vishkanya Venom: Injury; save Fort DC 10 + 1/2 the vishkanya's Hit Dice + the vishkanya's Constitution modifier; frequency 1/round for 6 rounds; effect 1d2 Dex; cure 1 save

Fixed, it was using automatic calculation that normally only considers racial Hit Dice for the DC.

This is what I was thinking of more for what users have submitted so that we could see what you geniuses had already had submitted to you and fixed.

I think what you're telling me is that you'd have to change a "header" or category name that a bug submitted is being filed under. That makes sense. I'm not sure that we'd have to see that at all though, just the end result.
What I was intending to ask about is more of a notice on what has been tackled by you guys that I should be watching out for as a bug before the next release.

I get that by having an actual bug submission process that it makes it easier on your end to track and manage the bugs as they are submitted and kudos for that! It means that it only makes Hero Lab better quicker for all of the users.

I'm not trying to jump your case at all on this. I don't intend the tone of this post to convey that at all but I can see how it could be read that way.

Keep up the great work on this excellent product!

 

[Mathias]

Exposing the bug system to users is an all-or-none proposition, and we've been using it internally for a year or so already to record the issues and project ideas we see, so we've got a lot of things in there beyond what was reported in the last few weeks.

The change list for each update, including the bugs addressed, is always available through the Help menu...Pathfinder FAQ within the program, and when each update is published, I copy this update's FAQ entry, and post it in the announcement thread - so, when the next release comes out, you'll be able to see what was changed.

 

[risner]

when the next release comes out, you'll be able to see what was changed.

I think that is sufficient for most user (like me), the only negative to not exposing it is on you. You will likely get more duplicate bugs of the same issue. I assume the bug tracking system has an easy way to tag a bug as a "dup of another bug id" and make your like a little easier.

Thanks!

 

[CorzatTheGray]

I think that is sufficient for most user (like me), ...

It is sufficient, I agree. I do check the changelog as well after each update because there is always a little something you guys toss in there that wasn't on a more recent post of the old thread and/or I had forgotten about.

I blame twitter and facebook for my need for constant updates... now that I mention it, I guess that's more of what I was envisioning. Something more along the lines of a tweet about a bug that was conquered. A simple here's what the problem was, here's what we did to fix it. Thus the beauty of the old thread. It was great even after the thread was locked to us as Aaron continued to post to it just to have that tweet-like feel to it to know that work continues on.

I'll stop beating the dead horse now though I think I've ranted enough about this.

Thanks for all that you guys do! It is appreciated by all of us users. The open communication on these forums between developers and users is amazing and I'm not sure of anywhere else other than on the Paizo boards themselves where so much, and timely communication occurs between the company and the people.

Again, thanks!