Bug discussion before report (on Github)

Status
Not open for further replies.

Anarcomu

King
Joined
Oct 4, 2022
Messages
640
Hello everyone !

Following an(other) bug comment on the New Version thread, I think it would be useful to have a dedicated thread for discussing bugs.

  • If you notice a bug and want to report it, read the Bug Reports thread and post on Github
  • If you notice a bug that might be caused by mods, please add a list of mods you are using, it will help determine if it is base VP or a modmod
  • If you notice a bug and you are not using any mod, discussion can help pinpoint the origin, and provide a reproducible save-game before reporting, which is encouraged.
 
The way I see it, Recursive is the current master of the mod, and has made their intentions pretty clear. They want bugs reported in git, not on CFC.

The current version that people are reporting on....is a beta. Bug hunting is part of the game. With all of the work people put into this thing for free, all they are asking is that when people find bugs, they report them using the proper method. That's really not a big ask here.
 
The way I see it, Recursive is the current master of the mod, and has made their intentions pretty clear. They want bugs reported in git, not on CFC.

The current version that people are reporting on....is a beta. Bug hunting is part of the game. With all of the work people put into this thing for free, all they are asking is that when people find bugs, they report them using the proper method. That's really not a big ask here.
Both can be done. A discussion might improve the report of a bug, so what's the harm?
 
Both can be done. A discussion might improve the report of a bug, so what's the harm?
The harm is when people use that as "well I've reported the bug on CFC, my work is done"

Its fine for people to ask "I'm seeing this behavior, is that intentional or a bug?" But then once they get the confirmation they should report it.

But most of the time its simply "hey this thing is broken" with no followup
 
The harm is when people use that as "well I've reported the bug on CFC, my work is done"

Its fine for people to ask "I'm seeing this behavior, is that intentional or a bug?" But then once they get the confirmation they should report it.

But most of the time its simply "hey this thing is broken" with no followup
So what if somebody comments "hey this thing is broken" with no followup? If you think that's insufficient, ignore it and move on. If you think that it may be of relevance, ask for a bug report or look into the issue yourself.

It's illusional to think that in an open, voluntary project you can somehow discipline the public. I would be grateful that, at least, someone gave me a hint that something's not right.

Edit: Sorry, I used the word "delusional" because of bad language skills. I meant to use "illusional".
 
Last edited:
I guess the intent here is that some people may just want confirmation that they are in fact looking at a bug. Well I guess that's OK. But understand that we won't make the submission to Github for you. I think that's the least thing somebody could do that has enjoyed this mod for many years. Yes, it may take a few minutes to figure out for a novice PC user. But if you have successfully installed the VP mod.. I have faith in you that you can figure out how to submit the bug to Github.

Some people might just not want to waste the devs time or embarrass themselves. Heck I did it. I thought I was playing the most recent stable and they did in fact release a newer version. My problem was already fixed. Oops.
 
I dont see a problem with a thread like this to discuss potential bugs, as long as the OP makes it clear that they should be reported on Github if something is to be done about it. As Abros mentioned, if 5 people report a weird behavior without a report and those persons would otherwise not have made a bug report anyway, that is still better. There is a vast difference in how much effort people want to put into this, and you cant expect to change that for everyone.
 
Moderator Action: No. This will inevitably lead to people posting bugs here and not on GitHub.
Issue Count.png

There is a very good reason why we keep track of bugs on GitHub.

We can easily close an issue if it's intentional, is already fixed, doesn't have enough information, is local, etc.

Thread closed.
 
Status
Not open for further replies.
Top Bottom