Castle World : ~11/Davinskeep


Castle / Castle Organizations / Castle World / James Brown / Davinskeep

The Davinskeep Project

A co-operative effort to “evolve” a castle over time, with multiple builders.

Some Background:

		Request for collaberation. :)
I'm going to start a project in the next couple weeks. An ambitious project, that will span generations! (well, minifig generations, anyway) I want to make a big castle, but I don't want to do anything boring and ordinary like planning it, or just (...) (24 years ago, 2-Nov-00, to lugnet.castle.org.cw)

		Re: Request for collaberation. :)
(...) I wasn't planning on doing this as a .dat file, no. I'm not great at visualizing 2D-->3D, and my CAD attempts to date have mostly been lame. I was planning on this being a "real" project. Some more guidelines that I've been turning around in (...) (24 years ago, 2-Nov-00, to lugnet.castle.org.cw)

		The Davinskeep Project
King Gregor was not pleased. "What do you mean, you didn't know?" "I'm sorry Sire, it's that simple: I had no idea. Probably no one does." Malcolm, the castellan of Davinskeep, did his best to be calm in the face of his (somewhat paranoid) monarch's (...) (23 years ago, 21-Mar-01, to lugnet.castle.org.cw) !

Project Overview:
Most real castles weren’t built all at once, or even by the same people. Even the ones that were built with a single vision often underwent changes over the generations as the needs of the occupants changed. The Davinskeep Project is an attempt to duplicate something of that real process of evolution over time by giving creative control of the building process to different people as the project continues.

Project Guildlines:
These are the things each contributor should keep in mind as they work on their “generation” of Davinskeep

As with any Castle World effort, the “3 C’s” are paramount: Courtesy, Co-operation, and Creativity
Each contributor should keep the modifications to Davinskeep limited to what could be achieved in a generation. No great leaps from 32-square manor houses to 6-baseplate fortresses, please.
No contributor should immediately “erase” or cover over the work of the immediately prior contributor, out of respect for each other’s work.
The storyline will also be a cooperative effort, with each person contributing the story for their generation of Davinskeep. (also see “Story Arc”, below)
I (James Brown) get a veto over project contributions, mostly because, well... it’s my idea, and I’m doing the groundwork.

Story Arc:
Each contributor gets a “generation” to play with - roughly 20-50 years where they get to decide what happened and why. The only stipulation is that Davinskeep passes in a direct line from Sir Davin, rightful heir to rightful heir. You’re welcome to have wars or rebellions or what-have-you, so long as by the end of your generation of story, Davinskeep is again firmly in the hands of the rightful heir. (and you can even fudge a bit on the “firmly” part...)

Logistics:
The logistics of a project like this, involving multiple people across (potentially) several countries, are tricky to say the least. In the early stages, while Davinskeep is still fairly small, people will likely duplicate it with their own collection, and make their modifications. Later on, as the keep grows, this will be less feasable, and copies of Davinskeep will be maintained by only a few people (possibly only me), and they will modify it under the direction of whoever has creative control for that generation.

It is also possible that some ambitious (and more CAD-savvy) person will undertake the maintenance of Davinskeep in a virtual form. This would be very cool, and possibly let more people participate - but is not a challenge I feel up to.

Historians Chapters Project notes and progress

Primary content in this document is © James Brown. All other text, images, or trademarks in this document are the intellectual property of their respective owners.