Downloads:

145

Downloads of v 1.5.0:

145

Last Update:

25 Aug 2019

Package Maintainer(s):

Software Author(s):

  • Nevander

Tags:

doom-d64rtr doom games d64 retribution

doom-d64rtr (Install)

1.5.0 | Updated: 25 Aug 2019

Downloads:

145

Downloads of v 1.5.0:

145

Maintainer(s):

Software Author(s):

  • Nevander

doom-d64rtr (Install) 1.5.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install doom-d64rtr (Install), run the following command from the command line or from PowerShell:

>

To upgrade doom-d64rtr (Install), run the following command from the command line or from PowerShell:

>

To uninstall doom-d64rtr (Install), 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 doom-d64rtr -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 doom-d64rtr -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 doom-d64rtr installed
  win_chocolatey:
    name: doom-d64rtr
    state: present
    version: 1.5.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 'doom-d64rtr' do
  action    :install
  version  '1.5.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: doom-d64rtr,
    Version: 1.5.0,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller doom-d64rtr
{
   Name     = 'doom-d64rtr'
   Ensure   = 'Present'
   Version  = '1.5.0'
   Source   = 'STEP 3 URL'
}

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


package { 'doom-d64rtr':
  provider => 'chocolatey',
  ensure   => '1.5.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install doom-d64rtr version="1.5.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 by moderator gep13 on 27 Aug 2019.

Description

FEATURES

  • All original maps ported directly from Doom 64 with accurate texturing in UDMF format
  • Remade Doom 64 MAP33 titlemap to be used as the actual TITLEMAP
  • Custom intermission text screens recreating the originals with text lines that fade instead of type on
  • New introduction text screen which tells the story so far from the game manual (can be skipped at any time to get right into the game)
  • Fixing obvious bugs and mismatched or unaligned textures present on the original levels
  • Only minor fixes made to maps (small things that improve the original maps visually or otherwise, but the maps will not deviate from the originals)
  • Map order is matched to Doom 64's original order exactly
  • Bonus "fun" maps are accessible from a hub style selection map
  • Reward for completing Hectic is a Megasphere (what you would get from the death traps) and some early cells
  • Titlemap has been made into a playable level also accessible from the fun map hub
  • Testing map included where you can see every monster, weapon, item, and prop and pit monsters against each other in a 12v12 arena
  • "Fake sky-hack 3D geometry" recreated by using actual 3D floors
  • Doom 64 style "split doors" recreated using scripts and sound sequences
  • MAP20 Breakdown's "sliding door" effect converted to Polyobjects
  • Scrolling cloud skies made using hires cloud textures, skyboxes and translucent 3D floors
  • All original cloud skies match up to the color and map slot they belong in from the original game
  • Colored sector lighting as close to Doom 64 as possible in GZDoom, will be improved in the future!
  • Freshly written scripts for every map, which accurately recreate original game events and puzzles
  • Toggle option to choose between a fully revamped arsenal with smoother firing animations from Cage and Almonds or the original animations
  • Toggle option to make bullet and shell casings drop from either animation set
  • Original push-back and recoil (purely visual) effects added to most weapons
  • Unmaker has been recreated to function identical to the original and uses cells for ammo
  • Three Demon Keys and upgrades to the Unmaker function as in Doom 64
  • Doom 64 HUD has been remade and incorporated replacing the normal Status Bar
  • G/ZDoom's alternative HUD is left unchanged, and thus still available for use if you prefer the alt hud
  • You can see which Demon Keys you have by checking the Automap
  • Player viewheight and size adjusted to match with Doom 64's larger map and sprite scale
  • Player speed and gravity adjusted to match Doom 64's properties
  • All Doom 64 monsters are remade and adjusted to match Doom 64's original behavior
  • All items, powerups, pickups, keys, weapons, ammo, and props are recreated
  • No additional enemies, gore effects or crazy map effects are added
  • Simple usage of dynamic lights to enhance atmosphere, but don't worry they aren't overbearing

tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$(Join-Path $toolsDir commonEnv.ps1)"
. "$(Join-Path $toolsDir dependenciesEnv.ps1)"

$url = Get-ModdbDlUrl 'https://www.moddb.com/downloads/start/170502'
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $installLocation
  url           = $url
  softwareName  = 'doom-d64rtr*'
  checksum      = '014F5B6667CC12DB1DAADA1D191653D0DEDDCB1A729878BE7CA160E0F891F559'
  checksumType  = 'sha256'
}
Install-ChocolateyZipPackage @packageArgs

$WAD = 'D64RTR[v1.5].WAD'
$BRIGHTMAPS = 'D64RTR_BRIGHTMAPS.PK3'
$d64rtrIco = "$(Join-Path $installLocation 'd64rtr.ico')"

## StartMenu
Install-ChocolateyShortcut -ShortcutFilePath "$(Join-Path $startMenuDir $ModName).lnk" `
  -TargetPath "$gzdoom" -Arguments "$BRIGHTMAPS -file $WAD -iwad $iWAD2" `
  -WorkingDirectory "$installLocation" `
  -IconLocation "$d64rtrIco"
Install-ChocolateyShortcut -ShortcutFilePath "$(Join-Path $startMenuDir `"$ModName Release Notes`").lnk" `
  -TargetPath "$installLocation\D64RTR_README.TXT" `

## StartMenu - Multiplayer
$SMMultiplayerDir = "$(Join-Path $startMenuDir Multiplayer)"
Install-ChocolateyShortcut -ShortcutFilePath "$(Join-Path $SMMultiplayerDir `"$ModName [MP] startServer [LAN]`").lnk" `
  -TargetPath "$gzdoom" -Arguments "$BRIGHTMAPS -file $WAD -iwad $iWAD2 -host -port 10666" `
  -WorkingDirectory "$installLocation"
Install-ChocolateyShortcut -ShortcutFilePath "$(Join-Path $SMMultiplayerDir `"$ModName [MP] joinServer [LAN]`").lnk" `
  -TargetPath "$gzdoom" -Arguments "$BRIGHTMAPS -file $WAD -iwad $iWAD2 -connect 127.0.0.1:10666" `
  -WorkingDirectory "$installLocation"

## Desktop
Install-ChocolateyShortcut -ShortcutFilePath "$lnkDesktop" `
  -TargetPath "$gzdoom" -Arguments "$BRIGHTMAPS -file $WAD -iwad $iWAD2" `
  -WorkingDirectory "$installLocation" `
  -IconLocation "$d64rtrIco"
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$(Join-Path $toolsDir commonEnv.ps1)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'doom-d64rtr*'
}
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
  $key | % {
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''
    } else {
    }
    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 | % {Write-Warning "- $($_.DisplayName)"}
}
Remove-Item "$lnkDesktop" -force
Remove-Item "$startMenuDir" -recurse -force
Remove-Item "$installLocation\*" -exclude *.ini, *.zds -recurse -force
tools\commonEnv.ps1
## Common between Install and Uninstall
$ModName = "D64RTR"

$installLocation = [IO.Path]::Combine($ENV:LocalAppData, 'Programs', "Doom $ModName")
$startMenuDir = [IO.Path]::Combine($ENV:AppData, 'Microsoft', 'Windows', 'Start Menu', 'Programs', "Doom $ModName")
$lnkDesktop = [IO.Path]::Combine($ENV:UserProfile, 'Desktop', "$ModName.lnk")
tools\dependenciesEnv.ps1
$gzdoomLocation = [IO.Path]::Combine($ENV:LocalAppData, 'Programs', 'gzdoom')
$freeDoomTools = [IO.Path]::Combine($ENV:ChocolateyInstall, 'lib', 'freedoom', 'tools')

$gzdoom = "$(Join-Path $gzdoomLocation 'gzdoom.exe')"
$iWAD2 = "freedoom2.wad" # located in $ENV:DOOMWADDIR

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

Discussion for the doom-d64rtr (Install) Package

Ground Rules:

  • This discussion is only about doom-d64rtr (Install) and the doom-d64rtr (Install) 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 doom-d64rtr (Install), 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