Home Trending Latest threads New posts Developer diaries

so will there be a bug reporting subforum?

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Status
Not open for further replies.
Show only dev responses
Very well, but....

Supposing the 'bug' is something triggered by specific hardware (yes, I know: why should it? But looking back at the HOI1 bugforum, it's clear that such things seem to happen), there's little point in attatching a save game (ia. won't work in the case of displayproblems, obviously).

Also, despite the mess of seing a bugreporting forum cluttered by all kinds of false alarms and mistakes, it may cut down on duplicate bugreports if previous reports can be looked up. An effect that I assume you guys would much appreciate?

And finally, players will be very pushy - as always - to inquire if this or that 'bug' will be fixed. It will be easier to say ya or nay once than have to respond to (or ignore) bunches of e-mail.

Just my 2 cavalryunits, but I think there would still be advantages in an open bugforum...?
 
Ditto. I'd like to see a bug forum if only so Paradox can say "we know about it; it's being fixed in the next patch" rather than have hundreds of us mailing save games through the ether.
 
Its because it takes time to maintain two lists, and its a more convenient filing system to get them in emails, and the process it into bug-databases.
 
Johan - could Paradox still do something like post a locked sticky listing all of the acknowledged bugs and whether they're fixed, unfixed, or WAD? If that's easy to do, that seems like the best of both worlds.

Thanks.
 
dmshewchuk said:
Johan - could Paradox still do something like post a locked sticky listing all of the acknowledged bugs and whether they're fixed, unfixed, or WAD? If that's easy to do, that seems like the best of both worlds.
Click to expand...

That would be the method used previously and as Johan said it's pretty tedious.

Especially since no matter how good a list you have you'll still have people reporting lots of stuff multiple times. Stickies are invisible to most posters for some reason.
 
Grosshaus said:
That would be the method used previously and as Johan said it's pretty tedious.

Especially since no matter how good a list you have you'll still have people reporting lots of stuff multiple times. Stickies are invisible to most posters for some reason.
Click to expand...

If you have a bug database it should be fairly easy to run a query on it from time to time and update bug status on a sticky. Could be automated even ... that way you just update your main database, and not worry about keeping 2 separate lists. It would be very useful for us, and shouldn't be much of a problem to maintain - apart from a little time required to set it up.
 
Status
Not open for further replies.
Top Bottom
Back