peliprint/README.md

## ![](https://i.imgur.com/SsOU6r8.png) teamblueprint/main
[Discord ➚](https://ptero.shop/community)\
[Documentation ➚](https://ptero.shop/docs)

[Installation](#installation)\
[Development](#development)\
[Extensions](#extensions)\
[Contributions](#contributions)

### Installation
**What you need:**
* The latest release of Blueprint. [Download ➚](https://github.com/teamblueprint/main/releases/latest)
* `unzip` [Download ➚](https://pkgs.org/download/unzip)
* Linux and Pterodactyl knowledge.
* Fingers and a brain.

**Installation:**
1. Navigate to your Pterodactyl folder. (most likely /var/www/pterodactyl)
2. Run the Blueprint installation script. This runs the commands required for Blueprint to function correctly. If your Pterodactyl folder is not `/var/www/pterodactyl`, put `OVERWRITE_FOLDER="/path/to/pterodactyl";` in front of `bash blueprint.sh`.
```sh
chmod +x blueprint.sh
bash blueprint.sh
```
3. After waiting for the installation script to finish, open up your Pterodactyl admin panel and click on the puzzle icon in the top right of the website.

### Development
We've made some guides for extension development over on [GitBook](https://ptero.shop/docs). We are adding more guides over time, don't hesitate to suggest a topic for future guides.

### Extensions
Open an issue on GitHub to get your extension listed here. To install an extension, upload your `something.blueprint` file to your Pterodactyl folder and run `blueprint -install something`.

**Announcements**: [PterodactylMarket](https://pterodactylmarket.com/resource/679), [sourceXchange](https://www.sourcexchange.net/products/announcements)\
**Redirect**: [PterodactylMarket](https://pterodactylmarket.com/resource/664), [GitHub](https://github.com/prplwtf/blueprint-redirect)\
**dbEdit**: [GitHub](https://github.com/prplwtf/blueprint-dbedit)

### Contributions
[prplwtf](https://github.com/prplwtf) - creator and maintainer\
[alipoyrazaydin](https://github.com/alipoyrazaydin) - contributor\
[sp11rum](https://github.com/sp11rum) - contributor
Blueprint has a brand new logo and errors are red now. Remember the Blueprint error screen? Instead of being blue, it's red now. Makes it a little bit easier to understand. Also, the new look is here, with a brand new website as well. Great stuff! 2023-06-05 12:20:01 -04:00			`## ![](https://i.imgur.com/SsOU6r8.png) teamblueprint/main`
Update Discord link to ptero.shop/community 2023-06-15 05:44:33 -04:00			`[Discord ➚](https://ptero.shop/community)\`
Fix Discord and Documentation links on README 2023-05-04 12:48:44 -04:00			`[Documentation ➚](https://ptero.shop/docs)`
Work in progress changes to the README mom i'm on the internet! 2023-05-04 08:38:35 -04:00
Add links to "Installation", "Development" and "Extensions" 2023-06-11 13:58:55 -04:00			`[Installation](#installation)\`
			`[Development](#development)\`
Add "contributions" to README.md 2023-07-04 05:36:20 -04:00			`[Extensions](#extensions)\`
			`[Contributions](#contributions)`
Add links to "Installation", "Development" and "Extensions" 2023-06-11 13:58:55 -04:00
Work in progress changes to the README mom i'm on the internet! 2023-05-04 08:38:35 -04:00			`### Installation`
			`What you need:`
			`* The latest release of Blueprint. [Download ➚](https://github.com/teamblueprint/main/releases/latest)`
			* `unzip` [Download ➚](https://pkgs.org/download/unzip)
			`* Linux and Pterodactyl knowledge.`
			`* Fingers and a brain.`

Simple README update 2023-05-07 06:55:12 -04:00			`Installation:`
Add better support for panels installed in other locations. 2023-07-25 16:42:32 -04:00			`1. Navigate to your Pterodactyl folder. (most likely /var/www/pterodactyl)`
			2. Run the Blueprint installation script. This runs the commands required for Blueprint to function correctly. If your Pterodactyl folder is not `/var/www/pterodactyl`, put `OVERWRITE_FOLDER="/path/to/pterodactyl";` in front of `bash blueprint.sh`.
Work in progress changes to the README mom i'm on the internet! 2023-05-04 08:38:35 -04:00			```sh
			`chmod +x blueprint.sh`
			`bash blueprint.sh`
			```
Finish the Installation instructions for README.md Off-topic note: Blueprint was meant to be a paid add-on in it's early days. This means some parts of the commits may talk about "obfuscation for the license system". The license system has been scrapped since and is not planned to come back, we are trying to keep our code open. Working on the project was messy back then, and you may see some outside people make commits and me question what others were doing before this became a solo-project. Have fun laughing at the previous commits of us trying to figure out if this project is even possible to do. 2023-05-04 09:09:13 -04:00			`3. After waiting for the installation script to finish, open up your Pterodactyl admin panel and click on the puzzle icon in the top right of the website.`
Update README.md 2023-05-21 07:51:08 -04:00
			`### Development`
Add extra information to README.md 2023-06-23 12:15:30 -04:00			`We've made some guides for extension development over on [GitBook](https://ptero.shop/docs). We are adding more guides over time, don't hesitate to suggest a topic for future guides.`
Extension list on README 2023-05-24 04:15:23 -04:00
			`### Extensions`
Add extra information to README.md 2023-06-23 12:15:30 -04:00			Open an issue on GitHub to get your extension listed here. To install an extension, upload your `something.blueprint` file to your Pterodactyl folder and run `blueprint -install something`.
Extension list on README 2023-05-24 04:15:23 -04:00
Update list of extensions 2023-07-24 11:06:49 -04:00			`Announcements: [PterodactylMarket](https://pterodactylmarket.com/resource/679), [sourceXchange](https://www.sourcexchange.net/products/announcements)\`
GitHub markdown frustrated me sometimes 2023-06-23 14:58:03 -04:00			`Redirect: [PterodactylMarket](https://pterodactylmarket.com/resource/664), [GitHub](https://github.com/prplwtf/blueprint-redirect)\`
Add "dbEdit" to list of extensions. 2023-06-23 14:55:19 -04:00			`dbEdit: [GitHub](https://github.com/prplwtf/blueprint-dbedit)`
Add "contributions" to README.md 2023-07-04 05:36:20 -04:00
			`### Contributions`
			`[prplwtf](https://github.com/prplwtf) - creator and maintainer\`
			`[alipoyrazaydin](https://github.com/alipoyrazaydin) - contributor\`
Fix mistake in README.md 2023-07-06 10:29:47 -04:00			`[sp11rum](https://github.com/sp11rum) - contributor`