I agree with @Ash and the sentiment echoed by a lot of people both here and on the questions/answers themselves. However I feel I should give my understanding of the topic as it runs slightly tangential than this single self-answered question:
1. Self-answering is scrutinised closely
Self answers can attract a bit more attention than normal, because they are a bit of a showcase of you, the problem you faced and the solution you took to overcome it.
Being able to share something profound so that it might help others is one of the great things about this site (in my opinion). And when done right it doesn't go unrewarded, you can effectively earn ~1.5x the rep of a regular answer if people vote on both the question (+5) and the answer (+10).
Having said that, there has to be a real need for your self-answered question. Does it:
- Provide expertise or insight to solve a problem (that might not be found elsewhere)? (E.g. 1, 2, 3) and/or,
- Consolidate multiple sources of information that would otherwise take a lot of sleuthing through? (E.g. 1, 2)
If a self-answer is simply listing information easily found in a wiki, it's likely people will think that is less useful, and vote accordingly.
2. 'Seeded' questions work great, when we have a problem to solve
I'd like to direct you to Minecraft crash question duplicates and SEO. In this case, we were getting a lot of Minecraft questions that gave little more than the not-very descriptive error message.
As it turns out there was a valid, easily identifiable cause of this error, but we were not able to share it easily with the masses as the error message could vary slightly from person to person. Thus, MrLemon created: Minecraft crashes on launch with EXCEPTION_ACCESS_VIOLATION, Problematic frame: ig4dev32.dll or ig4dev64.dll or ig4icd32.dll or ig4icd64.dll
This question gives readers a clear and concise description of the issue along with a path towards fixing it, as well as giving us a valid duplication target should we recognise this issue being posted again. I'd like to stress, we're not talking 2 or 3 questions here, but 23/26 linked questions, and probably a bunch more that were closed for other reasons and/or since deleted.
In other words, seeding questions can be beneficial, but there needs to be a reason, a gap in knowledge that our expertise* and knowledge can fill.
* Including the ability to sleuth - don't undervalue skill with a search bar!
The current situation
Now this is why I'm a little confused as to why some users are creating a bunch of seed questions of late as a means to consolidate questions. Ok, maybe from a purely content perspective this may seem like a good idea, but the thing is, Arqade is built on the premise of providing answers to questions, and solving problems as they arise, not creating wiki-style, exhaustive documentation of a topic. From the Tour:
Focus on questions about an actual problem you have faced. Include details about what you have tried and exactly what you are trying to do.
Using today's example, if someone asks how to unlock Captain Falcon, let's provide an answer which covers that. We don't broaden the scope of a question to encompass all relevant information on a topic, why would we create a broad "duplicate" just to dupe the earlier question to it?
I certainly don't think this is what LessPop_MoreFizz was talking about when he wrote On ending Chronological Oppression with respect to the matter of Question Duplication. That was about 'accidentally better duplicates' not 'creation of Umbrella-topics to force duplicates to'.
For me personally, I also think we can do better than to simply parrot a game wiki. In fact, if I may call upon LessPop one more time:
Stack Exchange isn't GameFAQs.
...what we do well isn't Big Lists of Stuff.
I'm a busy person. I'd like to imagine that most other users here are busy people. If somebody else has already created a [searchable database], by god, I'm going to use that to answer questions, and point out to people when their answers come from there. If someone has already made a list of [every weapon], we shouldn't be trying to make our own list - but if someone asks where to find all of the unique shotguns, that's something we can answer.
Wikis are great for general reference, and sure, there will always be questions that can be answered with a quote and a link, but we should be primarily focusing on building the answers for questions that wikis do not or cannot handle.
Self-answering is great when it addresses an actual problem you've faced with a substantial answer that makes the the site (and the internet) that much better for having it. Self-answered 'List' questions that simply transcribe/quote the wiki aren't helpful and isn't something we as a site should focus on, especially not if the primary reason is to duplicate other specific questions to it.
'Seeding' questions is OK, if there is a problem/gap in knowledge to address, but if you're substantially quoting, transposing or collating other people's answers, consider marking the combined answer 'Community Wiki' so that you aren't earning reputation points for other's work.
But to directly answer your question:
Is there a bias against self-answered questions?
No. The bias 'against' the current self-answered question comes from the points above and the points covered by Ash, Frank and other commenters that have been involved, but not against 'self answered questions' as a whole.