Downloads:

3,298

Downloads of v 3.4.3:

472

Last Update:

09 Mar 2015

Package Maintainer(s):

Software Author(s):

  • NetHack Development Team

Tags:

roguelike

NetHack

This is not the latest version of NetHack available.

  • 1
  • 2
  • 3

3.4.3 | Updated: 09 Mar 2015

Downloads:

3,298

Downloads of v 3.4.3:

472

Maintainer(s):

Software Author(s):

  • NetHack Development Team

Tags:

roguelike

  • 1
  • 2
  • 3
NetHack 3.4.3

This is not the latest version of NetHack available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Unknown


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

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

>

Deployment Method:

📝 NOTE: 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

  • 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

3. Copy Your Script

choco upgrade nethack -y --source="'INTERNAL REPO URL'" --version="'3.4.3'" [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 nethack -y --source="'INTERNAL REPO URL'" --version="'3.4.3'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install nethack
  win_chocolatey:
    name: nethack
    version: '3.4.3'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'nethack' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.4.3'
end

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


cChocoPackageInstaller nethack
{
    Name     = "nethack"
    Version  = "3.4.3"
    Source   = "INTERNAL REPO URL"
}

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


package { 'nethack':
  ensure   => '3.4.3',
  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.

This package was approved by moderator ferventcoder on 19 Mar 2015.

Description

NetHack is a single player dungeon exploration game that runs on a wide variety of computer systems, with a variety of graphical and text interfaces all using the same game engine. Unlike many other Dungeons & Dragons-inspired games, the emphasis in NetHack is on discovering the detail of the dungeon and not simply killing everything in sight - in fact, killing everything in sight is a good way to die quickly. Each game presents a different landscape - the random number generator provides an essentially unlimited number of variations of the dungeon and its denizens to be discovered by the player in one of a number of characters: you can pick your race, your role, and your gender.


tools\bins.ps1
function New-IgnoreBin {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory = $true)]
    [ValidateNotNullOrEmpty()]
    [ValidateScript({ Test-Path $_ })]
    [string] $Name
  )

  $Name = Resolve-Path $Name

  New-Item "$Name.ignore" -Type "File" -Force | Out-Null
}

function New-GuiBin {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory = $true)]
    [ValidateNotNullOrEmpty()]
    [ValidateScript({ Test-Path $_ })]
    [string] $Name
  )

  $Name = Resolve-Path $Name

  New-Item "$Name.gui" -Type "File" -Force | Out-Null
}
tools\chocolateyInstall.ps1
$id = "nethack"
$name = "NetHack for Windows"
$url = "http://sourceforge.net/projects/nethack/files/nethack/3.4.3/nethack-343-win.zip/download"

$tools = Split-Path $MyInvocation.MyCommand.Definition
$content = Join-Path (Split-Path $tools) "content"
$classic = Join-Path $content "NetHack.exe"
$tiles = Join-Path $content "NetHackW.exe"

. $tools\bins.ps1
. $tools\shortcut.ps1

Install-ChocolateyZipPackage $id $url $content

try {
  New-GuiBin $tiles

  New-Shortcut -Link "$name (Tiles)" -Target $tiles -SpecialFolder "CommonPrograms"
  New-Shortcut -Link "$name (Classic)" -Target $classic -SpecialFolder "CommonPrograms"

  Write-ChocolateySuccess $id
} catch {
  Write-ChocolateyFailure $id $_.Exception.Message
  throw
}
tools\chocolateyUninstall.ps1
$id = "nethack"
$name = "NetHack for Windows"

$tools = Split-Path $MyInvocation.MyCommand.Definition

. $tools\shortcut.ps1

Remove-Shortcut -Link "$name (Tiles)" -SpecialFolder "CommonPrograms"
Remove-Shortcut -Link "$name (Classic)" -SpecialFolder "CommonPrograms"
tools\shortcut.ps1
<#
  .SYNOPSIS

  New-Shortcut creates a new shortcut to a file or program.

  .DESCRIPTION

  New-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.

  .EXAMPLE

  PS> New-Shortcut -Link "foo" -Target "foo.exe" -SpecialFolder "CommonDesktop" -Description "The Foo program"

  .LINK

  https://github.com/AnthonyMastrean/chocolateypackages/blob/1b8671c6a7ca2f068524e663afd372db98bff844/helpers/shortcut.ps1
#>
function New-Shortcut {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory = $true)]
    [ValidateNotNullOrEmpty()]
    [string] $Link,

    [Parameter(Mandatory = $true)]
    [ValidateNotNullOrEmpty()]
    [ValidateScript({ Test-Path $_ })]
    [string] $Target,

    [string] $SpecialFolder,
    [string] $Icon,
    [string] $Description
  )

  $Link = Resolve-ShortcutLink -Link $Link -SpecialFolder $SpecialFolder

  $shell = New-Object -ComObject 'Wscript.Shell'

  $shortcut = $shell.CreateShortcut($Link)
  $shortcut.TargetPath = (Resolve-Path $Target)
  $shortcut.WorkingDirectory = (Split-Path (Resolve-Path $Target))

  if($Icon) {
    $shortcut.IconLocation = $Icon
  }

  if($Description) {
    $shortcut.Description = $Description
  }

  $shortcut.Save()

  if(-not(Test-Path $Link)) {
    throw "Failed to create shortcut: $Link"
  }
}

function Remove-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.

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
Nethack - Single Player Dungeon Exploration 3.6.6 21 Sunday, May 23, 2021 Approved
Nethack - Single Player Dungeon Exploration 3.6.5 18 Sunday, May 23, 2021 Approved
Nethack - Single Player Dungeon Exploration 3.6.4.20191221 15 Sunday, May 23, 2021 Approved
Nethack - Single Player Dungeon Exploration 3.6.4 24 Sunday, May 23, 2021 Approved
Nethack - Single Player Dungeon Exploration 3.6.3 24 Sunday, May 23, 2021 Approved
NetHack 3.6.2 775 Friday, June 7, 2019 Approved
NetHack 3.6.1 451 Monday, December 24, 2018 Approved
NetHack 3.6.0.1 747 Friday, February 3, 2017 Approved
NetHack 3.6.0 484 Monday, April 4, 2016 Approved

This package has no dependencies.

Discussion for the NetHack Package

Ground Rules:

  • This discussion is only about NetHack and the NetHack 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 NetHack, 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