Downloads:

1,600

Downloads of v 10.6.0:

143

Last Update:

08 Jun 2020

Package Maintainer(s):

Software Author(s):

  • POI Contributors

Tags:

foss cross-platform poi kancolle yuudachi

poi

10.6.0 | Updated: 08 Jun 2020

Downloads:

1,600

Downloads of v 10.6.0:

143

Software Author(s):

  • POI Contributors

poi 10.6.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install poi, run the following command from the command line or from PowerShell:

>

To upgrade poi, run the following command from the command line or from PowerShell:

>

To uninstall poi, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade poi -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade poi -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure poi installed
  win_chocolatey:
    name: poi
    state: present
    version: 10.6.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'poi' do
  action    :install
  version  '10.6.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: poi,
    Version: 10.6.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller poi
{
   Name     = 'poi'
   Ensure   = 'Present'
   Version  = '10.6.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'poi':
  provider => 'chocolatey',
  ensure   => '10.6.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install poi version="10.6.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 08 Jun 2020.

Description

poi is an open source Kancolle browser based on Electron. poi provides basic functionalities to enhance the gaming experience and is complemented by a variety of plugins. poi behaves the same as Chrome and does not modify game data, packets or implement bots/macros.

More information could be obtained here.

Features

  • Easily view fleet information from the main panel (level, hp, morale, fighter power, equipment, etc.)
  • One-click screenshot / mute
  • Configurable notifications on expedition, docking, construction, morale recovery related events
  • Quest progress tracking
  • Configurable game screen size
  • Configurable layout and themes
  • Cross-platform: available on Mac OS X, Linux and Windows
  • Supports HTTP, Socks5 and Shadowsocks proxy
  • More functionalities are availale through plugins, with some listed below:
    • Full list of ship girls and equipments with queries
    • Foreseeing the battle result
    • Expedition condition helper
    • Data collector and reporter
    • Daily equipment improvement list for Akashi's Arsenal
    • Multiple panels for other DMM games

legal\LICENSE.txt
The MIT License (MIT)

Copyright (c) 2015-2018 poi contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer have been downloaded from the github release page on <https://github.com/poooi/poi/releases>
and can be verified like this:

1. Go to <https://github.com/poooi/poi/releases/download/v10.6.0/poi-setup-10.6.0.exe>
   to download the installer
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum: E13D77B7C3434F22621602541324E407E4E9C97DF45C996789646C0EF7BEA42F

File 'LICENSE.txt' is obtained from <https://github.com/poooi/poi/blob/master/LICENSE>
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  fileType      = 'exe'
  file          = "$toolsDir\poi-setup-10.6.0.exe"

  softwareName  = 'poi*'

  silentArgs    = '/S /allusers'
  validExitCodes= @(0)
}

Install-ChocolateyInstallPackage @packageArgs

# Lets remove the installer as there is no more need for it
Get-ChildItem $toolsDir\*.exe | ForEach-Object { Remove-Item $_ -ea 0; if (Test-Path $_) { Set-Content "$_.ignore" '' } }
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'poi*'
  fileType      = 'exe'
  silentArgs    = '/S'
  validExitCodes= @(0)
}

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | ForEach-Object { 
    $packageArgs['file'] = "$($_.UninstallString)"

    $fileStringSplit = $packageArgs['file'] -split '\s+(?=(?:[^"]|"[^"]*")*$)'

    if($fileStringSplit.Count -gt 1) {
      $packageArgs['file'] = $fileStringSplit[0]
      $packageArgs['silentArgs'] += " $($fileStringSplit[1..($fileStringSplit.Count-1)])"
    }

    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | ForEach-Object {Write-Warning "- $($_.DisplayName)"}
}
tools\poi-setup-10.6.0.exe
 

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
poi 10.6.0-beta3 28 Sunday, May 24, 2020 Approved
poi 10.6.0-beta2 28 Wednesday, May 13, 2020 Approved
poi 10.6.0-beta1 27 Wednesday, May 6, 2020 Approved
poi 10.6.0-beta0 26 Tuesday, May 5, 2020 Approved
poi 10.5.1 220 Monday, January 13, 2020 Approved
poi 10.5.0-beta2 37 Monday, January 6, 2020 Approved
poi 10.5.0-beta1 54 Sunday, December 15, 2019 Approved
poi 10.5.0-beta0 33 Saturday, December 14, 2019 Approved
poi 10.4.0 83 Sunday, December 1, 2019 Approved

This package has no dependencies.

Discussion for the poi Package

Ground Rules:

  • This discussion is only about poi and the poi package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or poi, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus