# allianceauth-pve
[](https://pypi.python.org/pypi/allianceauth_pve)
[](https://codecov.io/gh/Maestro-Zacht/allianceauth-pve)
PvE tool for AllianceAuth
Free software: GNU General Public License v3
Features
========
This package aims at helping groups of people manage PvE sessions, centralized loot management and loot taxes.
Create a rotation
-----------------
Rotations are a sort of containers for entries. When created, they have some options to customize the behavior of the tool with the entries, such as tax rate, count of setups of the system before ratting etc.
They can be created by the people with the right permission (see [below](#permissions)). For them, a button will be avaiable in the main page. It'll lead to a form for creating a rotation.
| Field | Description |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | |
| Priority | The priority for the rotation in the list of active rotations. Rotations are displayed in descending order of priority. |
| Tax rate | Tax rate in percentage. 0 for disabling taxes. |
| Max daily setups | The maximum number of helped setups a user can get per day. This option is thought for wormholes where you should setup a system before ratting in it. Set to 0 for disabling tracking setups. Defaults to 1. |
| Min people share setup | The minimum number of users in an entry for considering the setups valid. Defaults to 3 |
| Entry buttons | [Custom buttons](#buttons-and-roles-setups) to be shown in the Entry forms. You can select them by holding Ctrl and left-clicking. The package comes with buttons for the main C5 and C6 wormhole. sites. |
| Roles setups | [Roles presets](#buttons-and-roles-setups) for Entry forms. You can select them by holding Ctrl and left-clicking. |
Add Entries
-----------
Entries are the corrisponding of an actual PvE fleet. They consist in an estimated total loot value and a set of shares.
When an Entry is submitted to a rotation, all the rules of tax rate and setups are applied and the loot value is split between the participants according to their share weight.
To add an entry to a rotation, click on the plus button on the bottom left of the screen.
Every entry has a list of shares. To add a share, search for the character you want to add in the panel on the right and click the add button.
A share will be added with the first role in the list, 1 site count and no setup. Setups are helpful in wormholes when you want to track who helped setting up a system before ratting. Roles defines how loot will be split between the shares: for example, if someone has 1 site count and a role with a value of 1 and someone else has 1 site count and a role with a value of 2, this last person will receive double the amount of money of the first one.
In order to add a role, you can click on the `New Role` button and create one from scratch or load a roles setup, if you chose at least one in the rotation form, by clicking on the `Load Roles Setup` button.
When you have a role loaded, you can choose it from the dropdown select on the shares.
On the center of the right panel there is the Estimated total section. There is a numeric field and a list of buttons if you selected at least one in the rotation form. you can either input the estimated total by hand or click on the buttons while you are running the sites.
On the right of the Estimated total field there are 4 buttons for incrementing the site count of the shares. If you hover each of them there'll be a tooltip telling what each button does.
The ones that change selected chars only edit the shares with the green arrow. This is helpful if you are doing the form while you are running the sites: if a person leaves, you can click on the arrow and it'll be unselected.
Once you have submitted the entry, you'll see updating the summary and the entry list on the rotation page. You can edit an entry by clicking the arrow on the right of the row in the entry list and then click on the edit button.
When the loot is sold, a person with the right permission (see [below](#permissions)) can close the rotation and insert the sales value in the form. Then the closed rotation page will be shown with the right amount of money to send to each person, calculated on the sales value.
You can see all the closed rotations from the dashboard.
Funding Projects
----------------
In the dashboard, there is a section for funding projects. People with the appropriate permission (see [below](#permissions)) can create projects and add them to the list. When adding entries, an active funding project can be selected with a percentage of the entry to be added to the project. The money will be added to the project total once the rotation is closed.
In each project page, there is a list of the people who have contributed to the project and the total amount of money they have contributed and the current completion percentage of the project.
Projects need to be closed manually by people with the appropriate permission and they will not appear during entry creation.
Closed Rotation
---------------
In a closed rotation summary, you can click on a character name and on an actual total to copy their value. Once you do so, the corresponding row in the table will be of a different color to help tracking down who is already being copied. To reset a row color, click on the `X` button on the right of the row.
Buttons and Roles Setups
------------------------
Buttons and roles setups can be created in the admin page by people who have access.
Settings
--------
| Setting | Default | Description |
| ---------------- | ------- | ---------------------------------------------------------------- |
| `PVE_ONLY_MAINS` | `False` | When set to `True`, only main characters are shown in search bar |
Help wanted
===========
This modeling is based on how whormoles fleets and loot are managed. If you have some feature requests for other types of environment, pls join [AllianceAuth discord](https://discord.gg/fjnHAmk) and give me a shout in the #pve-tool channel. I don't have any experience in anything except whormholes so any help is appriciated.
Installation
============
The following is assuming you have a functioning AllianceAuth installation.
1. `pip install allianceauth-pve`
2. Add `allianceauth_pve` (note the underscore) to your `INSTALLED_APPS`
3. Run migrations
4. Run collectstatic
5. Restart AllianceAuth
Updating
========
1. `pip install -U allianceauth-pve`
2. Run migrations
3. Run collectstatic
4. Restart AllianceAuth
Permissions
===========
The following permissions are provided:
1. `access_pve`: only users with this permission can see the tool and be added in entries.
2. `manage_entries`: only users with this permissions can create entries.
3. `manage_rotations`: only users with this permissions can create and close rotations.
4. `manage_funding_projects`: only users with this permissions can create and close funding projects.
You'll have to assign this permissions to desired groups/states to make the tool work.
Credits
=======
From an original idea of iRBlue.
This package was created with [Cookiecutter](https://github.com/audreyr/cookiecutter) and the [audreyr/cookiecutter-pypackage](https://github.com/audreyr/cookiecutter-pypackage) project template.
Raw data
{
"_id": null,
"home_page": null,
"name": "allianceauth-pve",
"maintainer": null,
"docs_url": null,
"requires_python": "~=3.8",
"maintainer_email": null,
"keywords": "allianceauth, eveonline, allianceauth_pve",
"author": null,
"author_email": "Matteo Ghia <matteo.ghia@yahoo.it>",
"download_url": "https://files.pythonhosted.org/packages/70/48/bdc35b79706191d0f8fdd8ad254a9ad242b3c5ab85c29b2b48da6e1fe9ee/allianceauth_pve-1.14.3.tar.gz",
"platform": null,
"description": "# allianceauth-pve\n\n[](https://pypi.python.org/pypi/allianceauth_pve)\n[](https://codecov.io/gh/Maestro-Zacht/allianceauth-pve)\n\n\nPvE tool for AllianceAuth\n\n\nFree software: GNU General Public License v3\n\nFeatures\n========\n\nThis package aims at helping groups of people manage PvE sessions, centralized loot management and loot taxes.\n\nCreate a rotation\n-----------------\n\nRotations are a sort of containers for entries. When created, they have some options to customize the behavior of the tool with the entries, such as tax rate, count of setups of the system before ratting etc. \n\nThey can be created by the people with the right permission (see [below](#permissions)). For them, a button will be avaiable in the main page. It'll lead to a form for creating a rotation.\n\n\n\n\n\n| Field | Description |\n| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Name | |\n| Priority | The priority for the rotation in the list of active rotations. Rotations are displayed in descending order of priority. |\n| Tax rate | Tax rate in percentage. 0 for disabling taxes. |\n| Max daily setups | The maximum number of helped setups a user can get per day. This option is thought for wormholes where you should setup a system before ratting in it. Set to 0 for disabling tracking setups. Defaults to 1. |\n| Min people share setup | The minimum number of users in an entry for considering the setups valid. Defaults to 3 |\n| Entry buttons | [Custom buttons](#buttons-and-roles-setups) to be shown in the Entry forms. You can select them by holding Ctrl and left-clicking. The package comes with buttons for the main C5 and C6 wormhole. sites. |\n| Roles setups | [Roles presets](#buttons-and-roles-setups) for Entry forms. You can select them by holding Ctrl and left-clicking. |\n\nAdd Entries\n-----------\n\nEntries are the corrisponding of an actual PvE fleet. They consist in an estimated total loot value and a set of shares.\nWhen an Entry is submitted to a rotation, all the rules of tax rate and setups are applied and the loot value is split between the participants according to their share weight.\nTo add an entry to a rotation, click on the plus button on the bottom left of the screen.\n\n\n\nEvery entry has a list of shares. To add a share, search for the character you want to add in the panel on the right and click the add button.\n\nA share will be added with the first role in the list, 1 site count and no setup. Setups are helpful in wormholes when you want to track who helped setting up a system before ratting. Roles defines how loot will be split between the shares: for example, if someone has 1 site count and a role with a value of 1 and someone else has 1 site count and a role with a value of 2, this last person will receive double the amount of money of the first one.\n\nIn order to add a role, you can click on the `New Role` button and create one from scratch or load a roles setup, if you chose at least one in the rotation form, by clicking on the `Load Roles Setup` button.\n\nWhen you have a role loaded, you can choose it from the dropdown select on the shares.\n\nOn the center of the right panel there is the Estimated total section. There is a numeric field and a list of buttons if you selected at least one in the rotation form. you can either input the estimated total by hand or click on the buttons while you are running the sites.\n\nOn the right of the Estimated total field there are 4 buttons for incrementing the site count of the shares. If you hover each of them there'll be a tooltip telling what each button does.\nThe ones that change selected chars only edit the shares with the green arrow. This is helpful if you are doing the form while you are running the sites: if a person leaves, you can click on the arrow and it'll be unselected.\n\n\n\nOnce you have submitted the entry, you'll see updating the summary and the entry list on the rotation page. You can edit an entry by clicking the arrow on the right of the row in the entry list and then click on the edit button.\n\nWhen the loot is sold, a person with the right permission (see [below](#permissions)) can close the rotation and insert the sales value in the form. Then the closed rotation page will be shown with the right amount of money to send to each person, calculated on the sales value.\n\n\n\nYou can see all the closed rotations from the dashboard.\n\nFunding Projects\n----------------\n\nIn the dashboard, there is a section for funding projects. People with the appropriate permission (see [below](#permissions)) can create projects and add them to the list. When adding entries, an active funding project can be selected with a percentage of the entry to be added to the project. The money will be added to the project total once the rotation is closed.\n\nIn each project page, there is a list of the people who have contributed to the project and the total amount of money they have contributed and the current completion percentage of the project.\n\nProjects need to be closed manually by people with the appropriate permission and they will not appear during entry creation.\n\nClosed Rotation\n---------------\n\nIn a closed rotation summary, you can click on a character name and on an actual total to copy their value. Once you do so, the corresponding row in the table will be of a different color to help tracking down who is already being copied. To reset a row color, click on the `X` button on the right of the row.\n\nButtons and Roles Setups\n------------------------\n\nButtons and roles setups can be created in the admin page by people who have access.\n\nSettings\n--------\n\n| Setting | Default | Description |\n| ---------------- | ------- | ---------------------------------------------------------------- |\n| `PVE_ONLY_MAINS` | `False` | When set to `True`, only main characters are shown in search bar |\n\nHelp wanted\n===========\n\nThis modeling is based on how whormoles fleets and loot are managed. If you have some feature requests for other types of environment, pls join [AllianceAuth discord](https://discord.gg/fjnHAmk) and give me a shout in the #pve-tool channel. I don't have any experience in anything except whormholes so any help is appriciated.\n\nInstallation\n============\n\nThe following is assuming you have a functioning AllianceAuth installation.\n\n1. `pip install allianceauth-pve`\n2. Add `allianceauth_pve` (note the underscore) to your `INSTALLED_APPS`\n3. Run migrations\n4. Run collectstatic\n5. Restart AllianceAuth\n\n\nUpdating\n========\n\n1. `pip install -U allianceauth-pve`\n2. Run migrations\n3. Run collectstatic\n4. Restart AllianceAuth\n\nPermissions\n===========\n\nThe following permissions are provided:\n1. `access_pve`: only users with this permission can see the tool and be added in entries.\n2. `manage_entries`: only users with this permissions can create entries.\n3. `manage_rotations`: only users with this permissions can create and close rotations.\n4. `manage_funding_projects`: only users with this permissions can create and close funding projects.\n\nYou'll have to assign this permissions to desired groups/states to make the tool work.\n\nCredits\n=======\n\nFrom an original idea of iRBlue.\n\nThis package was created with [Cookiecutter](https://github.com/audreyr/cookiecutter) and the [audreyr/cookiecutter-pypackage](https://github.com/audreyr/cookiecutter-pypackage) project template.\n\n\n",
"bugtrack_url": null,
"license": null,
"summary": "PvE tool for AllianceAuth",
"version": "1.14.3",
"project_urls": {
"Changelog": "https://github.com/Maestro-Zacht/allianceauth-pve/releases",
"Homepage": "https://github.com/Maestro-Zacht/allianceauth-pve",
"Source": "https://github.com/Maestro-Zacht/allianceauth-pve",
"Tracker": "https://github.com/Maestro-Zacht/allianceauth-pve/issues"
},
"split_keywords": [
"allianceauth",
" eveonline",
" allianceauth_pve"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "07301882654acfd68d3dd263d944e4f147f5544a857197fc0c81a4ba988dff15",
"md5": "be759216e654e47c48d2b1b784d89c32",
"sha256": "5fb2bda61a2c61e24b484a3e9fc0b46f4b81639f262db90b35084fe757d21ce2"
},
"downloads": -1,
"filename": "allianceauth_pve-1.14.3-py3-none-any.whl",
"has_sig": false,
"md5_digest": "be759216e654e47c48d2b1b784d89c32",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "~=3.8",
"size": 70398,
"upload_time": "2024-04-16T15:59:34",
"upload_time_iso_8601": "2024-04-16T15:59:34.141610Z",
"url": "https://files.pythonhosted.org/packages/07/30/1882654acfd68d3dd263d944e4f147f5544a857197fc0c81a4ba988dff15/allianceauth_pve-1.14.3-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "7048bdc35b79706191d0f8fdd8ad254a9ad242b3c5ab85c29b2b48da6e1fe9ee",
"md5": "7378680f9a69b7f6230dd1672f7d4154",
"sha256": "def9852190624ef12a824511637809910c1074c4f7a8912dbff4d83de08f8613"
},
"downloads": -1,
"filename": "allianceauth_pve-1.14.3.tar.gz",
"has_sig": false,
"md5_digest": "7378680f9a69b7f6230dd1672f7d4154",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "~=3.8",
"size": 46744,
"upload_time": "2024-04-16T15:59:35",
"upload_time_iso_8601": "2024-04-16T15:59:35.598027Z",
"url": "https://files.pythonhosted.org/packages/70/48/bdc35b79706191d0f8fdd8ad254a9ad242b3c5ab85c29b2b48da6e1fe9ee/allianceauth_pve-1.14.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-16 15:59:35",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "Maestro-Zacht",
"github_project": "allianceauth-pve",
"travis_ci": false,
"coveralls": true,
"github_actions": true,
"tox": true,
"lcname": "allianceauth-pve"
}
JSON
