Project settings
Table of contents
Description
Using the project settings, you can fine-tune the work of the project. Determines which options will be automatically applied when the template is run.
How to open the settings?
In order to open the project settings, you must click the corresponding button in the static blocks panel. If you do not see static blocks, then right-click on an empty space of the working window and set the “ Show static blocks ” checkbox in the context menu.
The project settings contain 3 sections - browser settings, proxychecker settings and HTTP settings.
Browser settings
Quick customize
Allows you to select 2 options for quick settings from templates - Quality or Speed . Depending on this choice, the general browser settings will be automatically set, which, if necessary, can be changed individually at your discretion.
Saving settings
If you often use the same combination of settings in your projects, you can save it using the appropriate button (1), after clicking on it you will be prompted to enter a name for the new configuration.
The settings from the “Browser” and “Proxychecker” tabs will be saved.
Settings from the “HTTP” tab are not saved.
To delete a configuration, use the corresponding button (2).
Browser type
In version 7.5.0.0, the Chromium engine was added.
Chrome engine is renamed in CEF (Chrome).
Which browser to use when working on the project. There are several options to choose from. Switching from one browser to another is also available directly at runtime using the Browser Settings action.
In the program settings, you can select a browser that will be used by default in all new projects.
Arguments
For the Chrome browser, you can add your own running arguments by listing them separated by a space. The complete list of arguments can be found at the links:
https://www.chromium.org/developers/how-tos/run-chromium-with-flags
https://peter.sh/experiments/chromium-command-line-switches/
After changing the arguments, you must restart your browser. This can be done by clicking the “Restart” button or by performing the Run instance action.
Input emulation
It allows you to emulate the actions of a real user when filling out fields on web pages, clicking on buttons and links, thereby bypassing protection on sites. Using the slider, you can select 4 options for preset values, thereby choosing between the speed of the project and its quality. When you select the maximum speed, all emulation options and protection bypass will be disabled, with maximum quality, all emulation and protection bypass will be enabled, but the execution speed will be lower.
DOM events emulation - Emulation of regular DOM events via JS (for example onfocus, etc.). These events are tracked by scripts that add new fields to the web page. Field filling checks and other primitive protection against bots.
Text insert emulation - Emulate data input and interact with a web page through keyboard and mouse events. As if a real person were pressing buttons and clicking a mouse. Bypasses advanced protections that monitor data entry without the use of peripherals.
Neural Network protection bypass - Advanced emulation based on human behavior. Allows you to bypass the vast majority of protection algorithms against bots, including neural network protection.
Full mouse emulation
This option enables mouse emulation at the project level.
This means that when the shooter "Setting values» (Set) and "Run action» (Rise) is automatically added to the mouse emulation from the current cursor to the HTML element that is specified in the action.
That is, to add mouse emulation to your template, just one click!
Nothing else is required.
Works only on maximum quality of input emulation.
Don't use a browser
Disables the browser part, while you cannot influence the page and its elements. If you work through POST / GET requests, with databases or batch files, the browser can be disabled to improve performance.
More information about working with requests can be found in the articles GET request , POST request and HTTP requests .
Browser without content view
Allows you to keep loading all elements on the page, but not display them. Allows you to save computer resources.
Dedicated process
If enabled, it uses one instance per base.exe base - in this case, tasks within the database will be performed faster, but resource consumption will increase.
The setting is only available for the Firefox engine
Use Proxifier
Allows you to use the program for proxying network traffic in the template.
Load pictures
For most sites, projects can work without pictures. Disabling them significantly saves traffic. You can also disable images using the Browser Settings action.
Load objects (Flash, Silverlight, Java)
If disabled, Flash, Silverlight, and Java objects will not load and run on the page. Allows you to increase productivity and save traffic. This setting can also be done using the Browser Settings action.
If Flash is enabled by this setting, but for some reason does not work in the Chrome browser, add the run arguments --enable-system-flash --disable-software-rasterizer --disable-smooth-scrolling to the launch. Read more: Flash does not work in the browser
Run JavaScript
If disabled, scripts on the page will not run. For most modern resources, this can affect the functionality of the site. This setting can also be done using the Browser Settings action.
Cache clearing
When starting the project, automatically clear the contents of the cache - storage of temporary information. Using the cache helps to save traffic consumption. This setting can also be done using the Browser Settings action.
Some of these settings are related to the rules for loading content and can be changed while working in a browser window .
You can also create your own version of the settings using the necessary modes of operation and save in a separate template.
Proxychecker settings
Allows you to set the rule according to which proxies will be taken from the proxychecker at the start of the project.
In the project itself, you can change the rule for the proxy checker using the “ Get proxy ” action. More details can be found in the article Using a proxy .
HTTP settings
The method for transmitting HTTP requests is set - Standard or Alternative . The " By default " option is specified in the program settings in the "Execution" tab.
By default ZennoPoster uses the Chillkat library to transfer HTTP requests.
We have added an alternative option - ZennoHttpClient , which allows you to solve problems with some sites (for example, Yandex).
Default - the method selected in the program settings.
Standard - Chillkat.
The alternative is ZennoHttpClient.
These settings are used to work with query actions. More information about working with requests can be found in the articles GET request , POST request and HTTP requests .