Civ+: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
m (Link to civcraft, devoted, and sovasc in the intro paragraph) |
m (remove duplicated in addition) |
||
Line 6:
Another major change is to the exp economy. Doing tasks such as mining, farming, fishing, and killing mobs has a chance to yield treasure maps. Treasure maps can be followed in order 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 aims to tie the exp grind and combat gear progression to exploration, something that a custom painted map like the one on Civ+ benefits greatly from.
Unlike many civservers, which aim to be on the latest version, Civ+ uses 1.8.9. Being on such an old version has many advantages. While modern civservers are forced (and often fail) to remain on a constant treadmill of version upgrades and mod updates, Civ+ can use the same mods and plugins it always has without any time wasted porting features. In addition, this stable platform allows Civ+ to use deep NMS techniques that reach deep into minecraft's code to modify vanilla mechanics. For example, the horse breeding mechanics introduced by Ivy would be impossible, or at least significantly more difficult without using NMS.
One of the major goals when designing plugins for Civ+ was for every new plugin to be fully self-documenting, or at least self-evident. Mechanics should explain themselves when you attempt to use them, and known mechanics should point to unknown mechanics. While this goal hasn't been fully reached with the existing plugins like Citadel and Namelayer, many of Civ+'s existing plugins are semi-self-documenting.
| |||