Notices: This section not yet converted to new layout. Download stats are rolling back out.

Dark Souls Map Viewer

0.2.0.20160511

Package test results are passing.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator dtgm on 5/12/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.

To install Dark Souls Map Viewer, run the following command from the command line or from PowerShell:

C:\> choco install darksoulsmapviewer

To upgrade Dark Souls Map Viewer, run the following command from the command line or from PowerShell:

C:\> choco upgrade darksoulsmapviewer

Files

Hide
  • tools\bins.ps1 Show
    <#
      .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\chocolateyInstall.ps1 Show
    $tools = Split-Path $MyInvocation.MyCommand.Definition
    $content = Join-Path (Split-Path $tools) 'content'
    $main = Join-Path $content 'dksmv-0.2\main.exe'
    
    . $tools\bins.ps1
    . $tools\shortcut.ps1
    
    Install-ChocolateyZipPackage `
        -PackageName 'darksoulsmapviewer' `
        -Url 'http://kayin.pyoko.org/darksoulsmapviewer.zip' `
        -Checksum '2004205a4bd94f190a62d7e01c3bea7c' `
        -UnzipLocation $content
    
    Install-IgnoreBin `
        -Path $main
    
    Install-Shortcut `
        -Link 'Dark Souls Map Viewer' `
        -Target $main `
        -SpecialFolder 'CommonPrograms'
    
  • tools\chocolateyUninstall.ps1 Show
    $tools   = Split-Path $MyInvocation.MyCommand.Definition
    
    . $tools\shortcut.ps1
    
    Uninstall-Shortcut `
        -Link 'Dark Souls Map Viewer' `
        -SpecialFolder 'CommonPrograms'
    
  • tools\shortcut.ps1 Show
    <#
      .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)
    }
    

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Maintainer(s)

Software Author(s)

  • vlad001 Ispohr

Tags

Version History

Version Downloads Last updated Status
Dark Souls Map Viewer 0.2 152 Wednesday, March 25, 2015 approved

Discussion for the Dark Souls Map Viewer Package

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.

comments powered by Disqus