mirror of
				https://github.com/PlaceholderAPI/PlaceholderAPI
				synced 2025-10-31 06:12:28 +01:00 
			
		
		
		
	Move to MkDocs Wiki setup
This commit is contained in:
		
							
								
								
									
										72
									
								
								docs/faq.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										72
									
								
								docs/faq.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,72 @@ | ||||
| # FAQ | ||||
|  | ||||
| Here are frequently asked questions about stuff related to PlaceholderAPI. | ||||
|  | ||||
| ## What is an Expansion? | ||||
|  | ||||
| An expansion (aka PlaceholderExpansion) usualy refers to a separate jar file that is added to PlaceholderAPI's `expansion` folder to add extra placeholders to use in other plugins.   | ||||
| External PlaceholderExpansions are downloaded from PlaceholderAPI's eCloud through the [`/papi ecloud download <expansion>`](commands.md#papi-ecloud-download) command. | ||||
|  | ||||
| Plugins may provide their own PlaceholderExpansion directly without any external jar file being used. | ||||
|  | ||||
| ## It only shows `%placeholder%` and not the variable | ||||
|  | ||||
| When a plugin or [`/papi parse me %placeholder%`](commands.md#papi-parse) only returns the placeholder itself and no value should you check for the following things: | ||||
|  | ||||
| - ### The expansion is actually installed. | ||||
|     In many cases is the cause that the expansion of the placeholder is missing.   | ||||
|     Just execute [`/papi ecloud download <expansion>`](commands.md#papi-ecloud-download) followed by `/papi reload` to activate it. You can find a list of Expansions and their Placeholders [on the placeholder list](users/placeholder-list.md). | ||||
|      | ||||
|     /// note | ||||
|     Not all placeholders come in their own expansion. Some plugins *hardcode* them in and load them on startup, when hooking into PlaceholderAPI.   | ||||
|     Such expansions may have `NO DOWNLOAD COMMAND` displayed on the Placeholder list. | ||||
|     /// | ||||
|    | ||||
| - ### Plugin actually supports PlaceholderAPI | ||||
|     It can happen that the plugin you use to display the placeholder in doesn't support PlaceholderAPI. In such a case check, if the parse command returns the actual value of a placeholder.   | ||||
|     If that is the case while the plugin is still displaying the placeholder, can this be an indicator of the plugin not supporting PlaceholderAPI. | ||||
|      | ||||
|     You can find a list of plugins supporting PlaceholderAPI [here](users/plugins-using-placeholderapi.md).   | ||||
|     Just make sure that "Supports placeholders" has a check mark in front of it. | ||||
|    | ||||
| - ### No typo in the placeholder | ||||
|     Double-check that the placeholder you set doesn't contain a typo. You can use [`/papi ecloud placeholders <expansion>`](commands.md#papi-ecloud-placeholders) (replace `<expansion>` with the name of the expansion) to get a list of all the placeholders the expansion may have.   | ||||
|     Keep in mind that this only works for separate expansions on the eCloud and not for those that are loaded by plugins. | ||||
|    | ||||
| - ### Plugin is enabled | ||||
|     If an expansion depends on a plugin, make sure you have the plugin installed and that it is enabled (Shows green in `/pl`). | ||||
|  | ||||
| ## I can't download the expansion | ||||
|  | ||||
| Make sure, that the connection to the cloud (https://api.extendedclip.com) isn't blocked by a firewall or similar.   | ||||
| Next step would be to check if the expansion actually exists on the cloud. Not all plugins provide their placeholders through a separate jar on the cloud. Some have them build in and register them on startup. | ||||
|  | ||||
| If both checks failed, go to the cloud-page and download the jar manually. Put it then in the `expansions` folder of PlaceholderAPI (`/plugins/PlaceholderAPI/expansions`).   | ||||
| Finally execute `/papi reload` to load the expansion. | ||||
|  | ||||
| ## How can other plugins use my placeholders with PlaceholderAPI? | ||||
|  | ||||
| See the [Using PlaceholderAPI](developers/using-placeholderapi.md) page. | ||||
|  | ||||
| ## Can I help on this wiki? | ||||
|  | ||||
| You sure can!   | ||||
| We welcome contributions to our wiki by everyone. If you found a typo or want to improve this wiki in another way, head over to the [Wiki's readme file][readme] to find out about how you can contribute towards this wiki. | ||||
|  | ||||
| ## PlaceholderAPI is posting an error about an outdated expansion? | ||||
|  | ||||
| ``` | ||||
| [00:00:01 ERROR]: [PlaceholderAPI] Failed to load Expansion class <expansion> (Is a dependency missing?) | ||||
| [00:00:01 ERROR]: [PlaceholderAPI] Cause: NoClassDefFoundError <path> | ||||
| ``` | ||||
|  | ||||
| If you receive the above error, try to do the following steps: | ||||
|  | ||||
| - Make sure any required dependency of the mentioned expansion (e.g. a plugin) is installed. | ||||
| - Make sure you use the latest version supported for the server version you use. | ||||
| - If you downloaded the jar from the ecloud, make sure it isn't malformed/corrupted. | ||||
|  | ||||
| If the issue persists after you've done those checks, report it to the author of the expansion.   | ||||
| In most cases is the issue that either a dependency is missing or that the expansion tries to use outdated methods from PlaceholderAPI. | ||||
|  | ||||
| [readme]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/wiki/README.md | ||||
		Reference in New Issue
	
	Block a user