Ansible
PS DSC
Downloads:
1,618
Downloads of v 0.2.0.20160511:
1,115
Last Update:
12 May 2016
Package Maintainer(s):
Software Author(s):
- vlad001 Ispohr
Tags:
games dark-souls map- Software Specific:
- Software Site
- Software Docs
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Dark Souls Map Viewer
- 1
- 2
- 3
0.2.0.20160511 | Updated: 12 May 2016
- Software Specific:
- Software Site
- Software Docs
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,618
Downloads of v 0.2.0.20160511:
1,115
Maintainer(s):
Software Author(s):
- vlad001 Ispohr
Dark Souls Map Viewer 0.2.0.20160511
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by vlad001 Ispohr. The inclusion of vlad001 Ispohr trademark(s), if any, upon this webpage is solely to identify vlad001 Ispohr goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Dark Souls Map Viewer, run the following command from the command line or from PowerShell:
To upgrade Dark Souls Map Viewer, run the following command from the command line or from PowerShell:
To uninstall Dark Souls Map Viewer, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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://community.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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download darksoulsmapviewer --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade darksoulsmapviewer -y --source="'INTERNAL REPO 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 darksoulsmapviewer -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install darksoulsmapviewer
win_chocolatey:
name: darksoulsmapviewer
version: '0.2.0.20160511'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'darksoulsmapviewer' do
action :install
source 'INTERNAL REPO URL'
version '0.2.0.20160511'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller darksoulsmapviewer
{
Name = "darksoulsmapviewer"
Version = "0.2.0.20160511"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'darksoulsmapviewer':
ensure => '0.2.0.20160511',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved by moderator dtgm on 12 May 2016.
Dark Souls Map Viewer is a program made by vlad001 on the xentax forums, who released the program open sourced. Ispohr on the Dark Souls Reddit re-released the map viewer, with the DLC content and a online map analytics too, but for whatever reason his website is now down (likely got hacked). Because of this, the Oolacile data file was kinda ‘lost’. A nice person over on Reddit posted it and I decided to package it up and host it. Now it’ll have a place to exist other than random rapidshare links. This is Vlad001’s with the map files from Ispohr’s release. Vlad001 has also been kind enough to endorse this mirror.
The maps themselves are not the -actual- maps of Dark Souls but instead the collision maps. The game’s collision maps are surprisingly complete, even when it comes to objects you should never be able to reach, but keep this in mind if something seems missing.
<#
.SYNOPSIS
Create a .ignore file for a package binary.
.DESCRIPTION
Chocolatey automatically creates a "shim" in a special folder, on your
machine's PATH, for any executables found in the package's installation
directory. This is helpful when installing ZIP packages or any kind of
command line tools.
Chocolatey can be instructed to ignore a particular binary by creating a file
at the same path with the same name as the binary to ignore, except ending
with the file extension ".ignore".
This function creates that file, given the binary's path.
.PARAMETER Path
The path of the binary to ignore.
This parameter also accepts multiple paths or pipeline input.
.EXAMPLE
Install-IgnoreBin -Path "foo.exe"
.EXAMPLE
Install-IgnoreBin -Path $foo, $bar
.EXAMPLE
Get-ChildItem "$content\foo\*.exe" | Install-IgnoreBin
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function Install-IgnoreBin {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true, ValueFromPipeline = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string[]] $Path
)
PROCESS {
foreach($item in $Path) {
New-Item "$(Resolve-Path $item).ignore" -Type "File" -Force | Out-Null
}
}
}
<#
.SYNOPSIS
Create a .gui file for a package binary.
.DESCRIPTION
Chocolatey automatically creates a "shim" in a special folder, on your
machine's PATH, for any executables found in the package's installation
directory. This is helpful when installing ZIP packages or any kind of
command line tools.
Chocolatey can be instructed to treat a particular binary as a GUI application,
meaning it will START the binary in a separate process and not block the
console, by creating a file at the same path with the same name as the binary,
except ending with the file extension ".gui".
This function creates that file, given the binary's path.
.PARAMETER Path
The path of the binary to treat as a GUI application.
This parameter also accepts multiple paths or pipeline input.
.EXAMPLE
Install-GuiBin -Path "foo.exe"
.EXAMPLE
Install-GuiBin -Path $foo, $bar
.EXAMPLE
Get-ChildItem "$content\foo\*.exe" | Install-GuiBin
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function Install-GuiBin {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true, ValueFromPipeline = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string[]] $Path
)
PROCESS {
foreach($item in $Path) {
New-Item "$(Resolve-Path $item).gui" -Type "File" -Force | Out-Null
}
}
}
$tools = Split-Path $MyInvocation.MyCommand.Definition
. $tools\shortcut.ps1
Uninstall-Shortcut `
-Link 'Dark Souls Map Viewer' `
-SpecialFolder 'CommonPrograms'
<#
.SYNOPSIS
Install-Shortcut creates a new shortcut to a file or program.
.DESCRIPTION
Install-Shortcut wraps the COM Object, Wscript.Shell, and its arguments to create
a shortcut to a file or program. It requires some very specific input, please
review the notes on each parameter.
.PARAMETER Link
The shortcut to create.
The underlying COM Object requires an absolute path. This function will
attempt to properly expand that path, especially if you provide a
SpecialFolder as a root directory.
The underlying COM Object also requires that the link's path/name end in
either .lnk or .url. This function will attempt to add that file extension if
it is not provided.
The underlying COM Object will fail silently in many cases, especially due to
improperly formatted link paths. This function will test the existence of the
expected link using this parameter and fail if it is not found.
.PARAMETER Target
The target of the shortcut.
This path must exist. This function will attempt to expand the path to its
absolute value.
.PARAMETER SpecialFolder
The Windows special folder to contain this shortcut.
If you want to create a shortcut at one of the system managed paths, such as
the Desktop or the Start Menu, you should use the special tokens provided.
The most commonly used are
* CommonDesktop
* CommonStartup
* CommonPrograms
If you provide a special folder, the Link parameter may contain a simple
"name" and not a file path.
The full list of special folders can be found here:
https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx
.PARAMETER Icon
The icon of the shortcut.
This can take several forms and, due to this, is not validated carefully. You
can provide an absolute file path (this is your responsibility), like
"C:\Windows\notepad.exe"
Or, you can provide an absolute file path and an index into the resources of
that program, like
"C:\Windows\notepad.exe, 1"
.PARAMETER Description
The tooltip to display on the shortcut.
.PARAMETER Launch
Whether to launch this link immediately after creating it. Useful for links
created in the CommonStartup special folder.
.EXAMPLE
Install-Shortcut -Link "foo" -Target "foo.exe" -SpecialFolder "CommonPrograms" -Description "Foo Bar"
.EXAMPLE
Uninstall-Shortcut -Link "foo" -SpecialFolder "CommonDesktop"
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/shortcut.ps1
#>
function Install-Shortcut {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string] $Link,
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string] $Target,
[string] $SpecialFolder,
[string] $Icon,
[string] $Description,
[switch] $Launch
)
$Link = Resolve-ShortcutLink -Link $Link -SpecialFolder $SpecialFolder
$shell = New-Object -ComObject 'Wscript.Shell'
$shortcut = $shell.CreateShortcut($Link)
$shortcut.TargetPath = (Resolve-Path $Target).Path
$shortcut.WorkingDirectory = (Split-Path (Resolve-Path $Target).Path)
if($Icon) {
$shortcut.IconLocation = $Icon
}
if($Description) {
$shortcut.Description = $Description
}
$shortcut.Save()
if(-not(Test-Path $Link)) {
throw "Failed to create shortcut: $Link"
}
if($Launch) {
& $Link
}
}
function Uninstall-Shortcut {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string] $Link,
[string] $SpecialFolder
)
$Link = Resolve-ShortcutLink -Link $Link -SpecialFolder $SpecialFolder
Remove-Item $Link -Force | Out-Null
}
function Resolve-ShortcutLink {
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string] $Link,
[string] $SpecialFolder
)
if(-not($Link.ToLower().EndsWith('.lnk') -or $Link.ToLower().EndsWith('.url'))) {
$Link = "$Link.lnk"
}
if($SpecialFolder) {
$Link = Join-Path ([System.Environment]::GetFolderPath($SpecialFolder)) $Link
}
$ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($Link)
}
Log in or click on link to see number of positives.
- darksoulsmapviewer.zip (84999db3833d) - ## / 57
- darksoulsmapviewer.0.2.0.20160511.nupkg (b0e0178ab086) - ## / 57
- main.exe (0b971fefe432) - ## / 56
- ogl_clr.dll (29760d798580) - ## / 55
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.
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| Dark Souls Map Viewer 0.2.0.20160511 | 1115 | Thursday, May 12, 2016 | Approved | |
| Dark Souls Map Viewer 0.2 | 503 | Wednesday, March 25, 2015 | Approved |
This package has no dependencies.
Ground Rules:
- This discussion is only about Dark Souls Map Viewer and the Dark Souls Map Viewer 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 Dark Souls Map Viewer, 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.