Downloads:
1,893
Downloads of v 0.1.3:
137
Last Update:
22 May 2019
Package Maintainer(s):
Software Author(s):
- All right reserved to: BrutalDoom
- FreeDoom and Zandronum authors
Tags:
brutaldoom doom freedoom zandronumbrutaldoom (Install)
Downloads:
1,893
Downloads of v 0.1.3:
137
Maintainer(s):
Software Author(s):
- All right reserved to: BrutalDoom
- FreeDoom and Zandronum authors
brutaldoom (Install)
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This package was rejected on 22 May 2019. The reviewer n3rd4i has listed the following reason(s):
=== 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)
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.
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)
$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
Log in or click on link to see number of positives.
- BrutalDoomModInstall.zip (a2775fee7a27) - ## / 58
- zandronum3.0-win32-base.zip (c261ecbc6931) - ## / 61
- freedoom-0.11.3.zip (28a5eafbb128) - ## / 60
- brutaldoom.0.1.3.nupkg (b8a610f31933) - ## / 60
- BrutalDoomModInstall.zip (088c35d934b0) - ## / 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 |
---|---|---|---|---|
brutaldoom (Install) 21.0.0 | 1730 | Thursday, June 6, 2019 | Approved |
2019 Moddb
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:
-
- freedoom (≥ 0.11.3)
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.
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.
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...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.
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.
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.
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.
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...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.
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.
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.
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...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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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'.