Civ+: Difference between revisions
Jump to navigation
Jump to search
Introduction: Remove statement of incompleteness in paragraph explaining self-documenting plugins, replace with mention of TutorTales
m (→Mechanics: Update meteor frequency and partly update sanctuaries) |
(Introduction: Remove statement of incompleteness in paragraph explaining self-documenting plugins, replace with mention of TutorTales) |
||
Line 19:
Another major change is to the exp economy. Doing tasks like mining, farming, fishing, and killing mobs has a chance to yield treasure maps. These maps can be followed to obtain a random relic - an item required for crafting exp, as well as the replacement for enchanted books and enchanting with an enchantment table. This ties the exp grind and combat gear progression to exploration, something that the custom painted map in Civ+ benefits greatly from.
One of the major goals in designing plugins for Civ+ was for them to be fully self-documenting, or at least self-evident. Mechanics should explain themselves when used, and known mechanics should point to unknown mechanics.
Civ+ was influenced by [[CivCraft|CivCraft 2.0]], [[Devoted|Devoted 2.0]], and [[Sovereignty Ascending]]. Obvious features like Citadel and Namelayer came from CivCraft 2.0, but less obvious features include the idea that a civserver should be permanent, without significant decay or fear of eventual reset. From Devoted 2.0 came the influence in Civ+'s WorldPainter map, designed from the start to be playable and pleasant from a first-person perspective. Finally, from Sovereignty Ascending came the idea of Sanctuaries, with several changes made to balance potential exploits. The prospective that civserver plugins should be rewritten also partially came from SovAsc.
| |||