Skip to content
This repository was archived by the owner on Mar 14, 2018. It is now read-only.

Dependencies & Supported Plugins

Jump to bottom
Bootscreen edited this page May 7, 2012 · 10 revisions

###Navigation###

##Dependencies This Plugins are needed for templecraft to work:
###Vault: 1.2.15 This adds some mayor basics to templecraft so you will have to install this before using TC!
Vault supports many plugins and it should be a very good idea to have it running anyway.

##Supported Plugins This Plugins are supported by templecraft. TempleCraft interacts with they'r API. This means, you don't need it to run TempleCraft, but when you use one of them you need the listed Version or above.
###Multiverse: 2.4-b527+### Worlds are unloaded and loaded per Multiverse so that mayor bugs are prevented
###Catacombs: 2.2+ Temples can be loaded/unloaded in temples. You are able to build a catacomb in a Temple -> Dungeonception!
###Heroes: 1.4.7+ The features of Heroes are compatible with templecraft. (Player-Life, Skills added to command whitelist in TCconfig etc.)
##Incompatible Plugins Plugins that do NOT work in temples. If you find a plugin that has problems with templecraft don't hesitate to inform us!\ Running them alongside TempleCraft should never be a problem, just do not use the features of them in TempleCraft-Worlds.
Tipp: If you wan't to use plugins within your temples try the option "constant-worldnames" in the config!\ You will not be able to run more then 1 instances of the same temple at a time but some plugins might do theyr job this way. ###ShowcaseStandAlone Do not set up showcases in temples.
###Citizens Do not create NPC's in temples.
###Others Do not use features of plugins in temples, that are not capable of handling worlds being load/unload without server restart.

Clone this wiki locally