💰 TradingView Scripts 📜

TradingView offers a wide range of functionalities like back-testing, custom indicators, etc., which are written in Pine Script. This directory lists all the indicators, strategies, etc., which are either already published or scripted for general users.

📜 Getting Started

The indicators, strategies, etc., are published in TradingView/ZenithClown. To add the custom indicator or strategies, use the indicators dropdown to add them to your chart. Unpublished scripts can be directly added/edited from the PineScript editor as follows:

1. Click on "Pine Editor" at the bottom/right panel of the chart,
2. For indicator - directly paste the code and click on "Add to Chart", and for strategies, click "Create New > Strategy" and then past the code and click on "Add to Chart".
3. You can also save the indicator (optional) to your own library.

For more information, check custom indicator documentation.

👁 Privacy Settings

TradingView offers two distinct types of privacy settings for its published indicators, strategies - (I) 👥 Public Visibility - where the script can be found from the indicators menu, and the (II) 🔒 Private Visibility - people with the link can only view the script. Check the code documentation for code visibility settings.

👩‍💻 Code Visibility

In terms of the code, there are three distinct levels of settings - (I) 🌐 Open Source, (II) 🔑 Protected Script, and the (III) 🤝 Invite Only script. Check the code documentation for code visibility settings.

⚖ Project Licensing

All the indicators, strategies, etc. (files with a .pine extension) follow MPL 2.0 License, which is the default for the PineScript (check publishing guidelines for more details). The project itself follows GPLv3 license as per the organization's rules.

⚖ Project Disclaimer

This service is intended solely to provide a data structure that enables efficient management of databases containing various data points for <content> analysis. Certain non-sensitive data that is available in the public domain may be distributed with the project. Other data may not be shared, and the organization is under no obligation to make such data available to the general public. For details, please refer to the disclaimer statement.