We'll send Avellone angry emails and letters of hate until he gets off his ass and starts writing. And if he messes something up.... grrr *shakes fist*

We need to send really cheesy emails and letters to Bethesda begging them to let him do it as well....

Not at all interested in knowing what's going on in the rest of the world?



svck up time.

Well it would be cool to see what things like elephants or kangaroos mutated to and how other societies became after complete anarchy but Fallout is mainly about the americana feel so I could do without it.

But I would like to see a RTS game for Resource Wars.

I'm not talking about a full fledged game though; I'm talking about parts of a new Fallout Bible being dedicated to what's going on in other places of the world. I just think it would be nice to get a sense that there's more going on in the Fallout world than the events of the games.

Ah, the whole "Bethesda owns the Fallout franchise" thing. I forgot about that.... and that's where Bethesda comes in and says "we can't allow it, it would turn future titles into that of which isn't spoken of.", even if the bible focuses on areas that Bethesda will probably never touch again. they would probably want to keep as many options open as they can for future titles and DLC, so I doubt they would allow it. if they did, they would have to go over everything Avellone put in, and most likely edit the [censored] out of it....one can always hope though...

Yeah I know but still, Resource Wars are an important part and was suppose (IIRC) to be it's own game and an RTS no less so that's why I want it.

Which is presicely my point. Lets say some writer decides to write a piece in the bible about Fort Knox being looted whilst the bombs were falling by the troops guarding it. Never mentioned in a game or anything so far, but its presence in the document locks it in.

Three years later, someones designing a DLC and thinks "You know what would be cool? Raiding Fort Knox?" - Despite the fact its never been in a game, the avenue is closed. No matter how cools the surrounding details are, and ignoring the fact that its never appeared in game, Fort Knox is off the table, unless you want to come back to the boards filled with "Broke Canon" flames.

Leave the Canon to just whats in the games, so the creativitity of the folks creating future games isn't limited.

If there is something that is written in the bible and needs to be re-written or tweaked to fit in with something then it can be done.
I see no reason why the bible "should" canonize something that hasn't even been mentioned in any game. (At least I think so... Has Fort Knox been mentioned?)
The Bible should serve to flesh out things that have been mentioned but weren't flesh out enough in the main game/DLC's among other things.
So just writing about Fort Knox for no reason seems... Unnecessary.
While fleshing out Talon Company would be a bit more necessary.
And it's all about how much they decide to write about the things as well.
Maybe they want to flesh out Ronto a bit more, nothing too big, just giving around 50 to 100 words about Ronto and it's military power while still leaving lots of creative possibility open for future games/DLC's/expansions.

Okay then. Lets make it a bit more direct. We write in the Bible today that Talon company is decended from a group like Blackwater. Ex Military officers operating as civilian contractors, those that exist today are the decendants from those helping establish military law in Toronto.

Lets say then in Fallout 6, we've got a great idea that talon company could slide right into. Problem is, is that the Civilian Military contractors idea isn't going to work, neither is the Canadian Connection - they're now decended from an active military unit guarding fort knox.

Whilst we can say that "The bible can be changed", the result would be accusations of breaking the established canon here on this very forum, NMA, and well everywhere else. It would also invalidate the point of the bible - its not really a bible if its just a few unused ideas that can be contradicted at a moments notice.

I agree that "Behind the scenes" stuff is good, and if devs want to publish a dissued concept for a location or quest like we saw with van buren, great, publish away. But it should be clearly understood to be non-canon until confirmed (and the Bible name not used).

Well for the sake of not just a Bible but the whole deal lets hope it doesn't go back to http://removed, I think that wouldn't be good for the franchise.

bigcrazewolf

Then the bible should be respected and followed, if the new idea don't fit then they can work with what they have instead.
Only way to allow complete artistic freedom is to set a game far away from the others and only have new stuff.
So long as there is old stuff there are old rules that need to be followed.
Might limit them somewhat but this isn't some kind of personal playground, the devs better damn well follow the lore.
Whether it's from a game, a comic or an online bible.
And hell, I consider it better writing if a writer can take previous work and while still following it put his/her own spin on it.

Gonna stop nagging about it now though, opinions differ.

Nobody said they would use TES approach in Fallout as well. Hell, one wonders if they would use another "Warp in the West" approach in future TES games either so being angry for that is a bit silly.

:shrug:


:thumbsup:

I really lliked the original bibles and read the hell out of them, the only thing I didn't like is how they handled the Talking Deathclaws... I mean wtf, the only reason why they died 100% of the time is because of a bug and it was "confirmed" canon.

I dislike that, it's in the same strain of "yep this is suddenly canon" by those dudes at the Vault Wiki that just because of an offhand vague comment the Chosen One IS AND ALWAYS WILL BE a male despite every direct mention of him/her lacking any and all gender pronouns.

Eventually I'm going to make an account and revert those changes and say something on the talk page because I think they were too sudden and too strong.

A lot more necessary.