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

brutaldoom (Install)

Package test results are passing.

This package was rejected on 5/22/2019. The reviewer n3rd4i has listed the following reason(s):

n3rd4i (maintainer) on 12 May 2019 17:20:18 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 12 May 2019 17:54:55 +00:00:

brutaldoom has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:

    • docsUrl - points to the location of the wiki or docs of the software

    • mailingListUrl - points to the forum or email list group for the software

    • bugTrackerUrl - points to the location where issues and tickets can be accessed

    • projectSourceUrl - points to the location of the underlying software source

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 12 May 2019 19:39:59 +00:00:

brutaldoom has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/3f05ff9060afaf0722ee84525bda5715 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

n3rd4i (maintainer) on 13 May 2019 14:04:27 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 13 May 2019 14:37:35 +00:00:

brutaldoom has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:

    • docsUrl - points to the location of the wiki or docs of the software

    • mailingListUrl - points to the forum or email list group for the software

    • bugTrackerUrl - points to the location where issues and tickets can be accessed

    • projectSourceUrl - points to the location of the underlying software source

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 13 May 2019 15:40:19 +00:00:

brutaldoom has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/fb35da1e01f75b4aaf7986d04eef18a5 for details.
This is an FYI only. There is no action you need to take.

n3rd4i (maintainer) on 13 May 2019 17:08:57 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 13 May 2019 17:43:10 +00:00:

brutaldoom has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:

    • docsUrl - points to the location of the wiki or docs of the software

    • mailingListUrl - points to the forum or email list group for the software

    • bugTrackerUrl - points to the location where issues and tickets can be accessed

    • projectSourceUrl - points to the location of the underlying software source

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 13 May 2019 18:30:52 +00:00:

brutaldoom has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/90c1fb9a1c8cceb25572a9f870fdb80d for details.
This is an FYI only. There is no action you need to take.

n3rd4i (maintainer) on 13 May 2019 20:55:27 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 13 May 2019 21:28:32 +00:00:

brutaldoom has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 13 May 2019 22:19:38 +00:00:

brutaldoom has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/d1e237b9adddadf69cbc5e82850ab1c6 for details.
This is an FYI only. There is no action you need to take.

n3rd4i (maintainer) on 16 May 2019 20:23:58 +00:00:

User 'n3rd4i' (maintainer) submitted package.

n3rd4i (maintainer) on 16 May 2019 20:30:24 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 16 May 2019 21:05:03 +00:00:

brutaldoom has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 16 May 2019 21:48:04 +00:00:

brutaldoom has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/7cda71ca2c1282ec63182ae839392b71 for details.
This is an FYI only. There is no action you need to take.

n3rd4i (maintainer) on 17 May 2019 17:42:53 +00:00:

User 'n3rd4i' (maintainer) submitted package.

n3rd4i (maintainer) on 17 May 2019 17:45:45 +00:00:

User 'n3rd4i' (maintainer) submitted package.

n3rd4i (maintainer) on 17 May 2019 17:51:20 +00:00:

User 'n3rd4i' (maintainer) submitted package.

n3rd4i (maintainer) on 17 May 2019 17:54:43 +00:00:

User 'n3rd4i' (maintainer) submitted package.

n3rd4i (maintainer) on 17 May 2019 17:58:39 +00:00:

User 'n3rd4i' (maintainer) submitted package.

n3rd4i (maintainer) on 17 May 2019 18:01:13 +00:00:

User 'n3rd4i' (maintainer) submitted package.

n3rd4i (maintainer) on 17 May 2019 18:04:24 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 17 May 2019 18:38:01 +00:00:

brutaldoom has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 17 May 2019 19:29:03 +00:00:

brutaldoom has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/61cd8e7f0f617e57785e56dce9967288 for details.
This is an FYI only. There is no action you need to take.

n3rd4i (maintainer) on 21 May 2019 17:21:58 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 21 May 2019 17:53:25 +00:00:

brutaldoom has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • Binary files (.exe, .msi, .zip, etc) have been included without including a LICENSE.txt file. This file is required when including binaries More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

n3rd4i (maintainer) on 21 May 2019 18:01:23 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 21 May 2019 18:22:26 +00:00:

brutaldoom has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/188a287dfa1083c2800439ef969a5768 for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 21 May 2019 18:33:31 +00:00:

brutaldoom has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • Binary files (.exe, .msi, .zip, etc) have been included without including a LICENSE.txt file. This file is required when including binaries More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

n3rd4i (maintainer) on 22 May 2019 04:56:05 +00:00:

User 'n3rd4i' (maintainer) submitted package.

chocolatey-ops (reviewer) on 22 May 2019 05:30:30 +00:00:

brutaldoom has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • Binary files (.exe, .msi, .zip, etc) have been included without including a LICENSE.txt file. This file is required when including binaries More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 22 May 2019 06:22:43 +00:00:

brutaldoom has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/eb7f5f486f7a24691da9510ddedbbffe for details.
This is an FYI only. There is no action you need to take.

n3rd4i (maintainer) on 22 May 2019 17:36:51 +00:00:

will place correct version and reject this one
Status Change - Changed status of package from 'submitted' to 'rejected'.


=== Brutal Doom for Windows ===

Just packaged version of 3 components:
1. Zandronum Engine (https://bitbucket.org/Torr_Samaho/zandronum/src/default/)
2. FreeDoom Wads (https://github.com/freedoom/freedoom.github.io)
3. BrutalDoom Mod (https://www.moddb.com/mods/brutal-doom)

Files

Hide
  • tools\assets\brutalv21.rar
  • tools\assets\brutal_doom.ico
  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop'; # stop on all errors
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $zandronumLocation = "$ENV:LocalAppData\Programs\Zandronum"
    $freedoomLocation = "$ENV:LocalAppData\Programs\FreeDoom"
    $installLocation = "$ENV:LocalAppData\Programs\BrutalDoom"
    $startMenuLocation = "$ENV:AppData\Microsoft\Windows\Start Menu\Programs\BrutalDoom"
    New-Item -ItemType Directory -Force -Path $installLocation
    
    ## Brutal Doom section
    $BDModName = 'brutalv21'
    $BDModPack = "$BDModName.pk3"
    $brutalDoomArgs = @{
      packageName   = 'BrutalDoomMod'
      file           = "$toolsDir\assets\$BDModName.rar"
      unzipLocation = $installLocation
      # specificFolder = $BDModPack
      softwareName  = 'brutal*'
      checksum      = 'A42F7A1F4FBEC5B19591ECE7F9811034'
      checksumType  = 'md5'
    }
    Install-ChocolateyZipPackage @brutalDoomArgs
    
    Install-ChocolateyShortcut `
      -ShortcutFilePath "$startMenuLocation\BrutalDoom Manual.lnk" `
      -TargetPath "$installLocation\BRUTAL DOOM MANUAL.rtf" `
      -Description "Brutal Doom Manual for v21 GOLD Release"
    
    Install-ChocolateyShortcut `
      -ShortcutFilePath "$startMenuLocation\BD Start LAN Server.lnk" `
      -TargetPath "$zandronumLocation\zandronum.exe" `
      -Arguments "-iwad %localappdata%\Programs\FreeDoom\freedoom1.wad -file %localappdata%\Programs\BrutalDoom\brutalv21.pk3 -port 10666 +map E2M1 +sv_maxlives 0 -host +alwaysapplydmflags 1 -skill 3 +cooperative 1 +sv_hostemail "" +sv_maprotation 0 +sv_randommaprotation 0 +sv_motd "" +sv_hostname BDHome1 +sv_website "" +sv_password "" +sv_forcepassword 0 +sv_joinpassword "" +sv_forcejoinpassword 0 +sv_rconpassword "" +sv_broadcast 1 +sv_updatemaster 0 +sv_maxclients 8 +sv_maxplayers 8 -upnp +dmflags 0 +dmflags2 0 +zadmflags 0 +compatflags 0 +zacompatflags 0 +lmsallowedweapons 0 +lmsspectatorsettings 0 +sv_afk2spec 0 +sv_coop_damagefactor 1 +sv_defaultdmflags 0" `
      -Description "BrutalDoom Start LAN server" `
      -WorkingDirectory "$installLocation"
    
    Install-ChocolateyShortcut `
      -ShortcutFilePath "$startMenuLocation\BD Join Local LAN Server.lnk" `
      -TargetPath "$zandronumLocation\zandronum.exe" `
      -Arguments "-file %localappdata%\Programs\BrutalDoom\brutalv21.pk3 -iwad freedoom1.wad -connect 127.0.0.1:10666" `
      -Description "BrutalDoom Join Local LAN server" `
      -WorkingDirectory "$installLocation"
    
    Install-ChocolateyShortcut `
      -ShortcutFilePath "$startMenuLocation\BrutalDoom.lnk" `
      -TargetPath "$zandronumLocation\zandronum.exe" `
      -Arguments "$installLocation\$BDModPack" `
      -IconLocation "$toolsDir\assets\brutal_doom.ico" `
      -Description "Brutal Doom v21 GOLD Release" `
      -WorkingDirectory "$installLocation"
    
    Install-ChocolateyShortcut `
      -ShortcutFilePath "$ENV:UserProfile\Desktop\BrutalDoom.lnk" `
      -TargetPath "$zandronumLocation\zandronum.exe" `
      -Arguments "$installLocation\$BDModPack" `
      -IconLocation "$toolsDir\assets\brutal_doom.ico" `
      -Description "Brutal Doom v21 GOLD Release" `
      -WorkingDirectory "$installLocation"
    
  • tools\chocolateyuninstall.ps1 Show
    $ErrorActionPreference = 'Stop'; # stop on all errors
    $installLocation = "$ENV:LOCALAPPDATA\Programs\BrutalDoom\*"
    $iconPath = "$ENV:UserProfile\Desktop\BrutalDoom.lnk"
    
    $packageArgs = @{
      packageName   = $env:ChocolateyPackageName
      softwareName  = 'brutaldoom*'  #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
    }
    
    $uninstalled = $false
    [array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
    if ($key.Count -eq 1) {
      $key | % { 
        $packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below
        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 $installLocation -exclude *.ini, *.zds -recurse -force
    Remove-Item $iconPath -force
    
  • tools\LICENCE.txt Show
    From: https://www.moddb.com/mods/brutal-doom
    
    LICENSE
    
    All right reserved to:
    
    CREDITS
    Brutal Doom by Sergeant_Mark_IV
    
    
    Sprites:
    Mike12, Captain Toenail, David G, Revilution, Eriance, Perkristian, Dr. Doctor, DoomNukem, Joey_TD, Das_M, Rafael GoldenWarrior72, Samuel 'Mryayayify' Shank, Brandon (Keeper), Pa1nki113r, CrucuxDuo, Minigunner, Jekyll Grim Payne, Scuba Steeve, Ghastly, Vader, Lynn Forest, EletricPulse, Mr. Enchanter, Doom_Jedi, Kamijou, Kars van Kouwen, scalliano, Tomtefars, Azona, A James, BretArts, 3D Realms, Raven Software.
    
    Extra Code:
    TerminusEst13, Solarsnowfall, Nash, Jekyll Grim Payne
    
    Voice Acting:
    Zero X. Diamond (Doomguy)
    Black Metal Chainsaw (Female Player)
    Tiberium Soul (Marines)
    
  • tools\VERIFICATION.txt Show
    VERIFICATION
    
    Verification is intended to assist the Chocolatey moderators and community
    in verifying that this package's contents are trustworthy.
    
    Brutal Doom download Website (checksum visibile in this link):
    Link: https://www.moddb.com/mods/brutal-doom/downloads/brutal-doom-v21-beta
    MD5 Hash: a42f7a1f4fbec5b19591ece7f9811034
    
    This is the same checksum used in the install.
    

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

Package Maintainer(s)

Software Author(s)

  • All right reserved to: BrutalDoom
  • FreeDoom and Zandronum authors

Copyright

2019 Moddb

Tags

Release Notes

May 16 2019 Release Candidate 11
- Fixed a few more bugs.
- Further improved the gore system.
- All PSX Maps fully working.
- Flamecannon and Flamethrower now moved to Slot 9 as it was supposed to be.
- All armor types now saves 50%, to match classic Doom's Blue Armor, and solve issues with vehicles and the IDFA cheat.
- Revolver now allows to change ammo for rifle bullets as alt-fire.

Full changelog here:
- https://www.moddb.com/mods/brutal-doom/downloads/brutal-doom-v21-beta

Version History

Version Downloads Last updated Status

Discussion for the brutaldoom (Install) Package

Ground rules:

  • This discussion is only about brutaldoom (Install) and the brutaldoom (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 brutaldoom (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
Chocolatey.org uses cookies to enhance the user experience of the site.
Ok