A wikiup is a system for authoring content, much as a wiki is.

The key distinction is that while a wiki typically stores qualitative content, a wikiup primarily stores values. That is, values which can drive a system. A wikiup is not itself a game system or a game: it is a library of game data, completely separated from any specific game implementation. The quantitative information in the library is available to client applications through the Wikiup API.

Why is this useful?

Consider this scene. A group of game developers meet in a smoky room over stale pizza and innumerable cans of Red Bull, arduously deciding whether a broadsword does more damage than a scimitar and what kind of armor a dwarf should wear. They move onto pikes, cutlasses, short swords, daggers, long bows, crossbows and lances. Shields, helmets must be considered alongside armor, terrain types, wall types, spells, potions, foodstuffs and precious metals. All this (and so very many cans of Red Bull) before they even get to characters and creatures. Now, how much of this work is really unique? Have not other games been written in which much of this data has already been explored and quantified? Wouldn’t it be faster and cheaper to prototype or even release by using a library of existing data?

This is where the wikiup comes in. Instead of sweating interminably over these same concepts and values, wikiup provides just such a data library, already vetted by an interested community, ready to plug into your new game. Is the data deficient in some way? No problem, simply add to the library to accommodate your needs. If you believe in “the wisdom of crowds” the data can be plugged into your game via a live web service. If you’re a little less trusting, the data can be downloaded and edited to your satisfaction. You can even tag versions of data that you like and accept “approved” content. Even if you still feel distrustful of the data, it can be readily employed for rapid prototyping, after which the stale pizza and Red Bull will still be waiting.