GunCAD Wiki - User contributions [en]

GunCAD Index

2026-02-01T18:52:02Z

Mission:

[[File:Guncad-index-256-round.png|alt=GunCAD Index|thumb|The GunCAD Index logo]]
The '''GunCAD Index''' is a search engine for [[3D Printing|3D-printable]] gun designs ({{Glossary|GunCAD|guncad}}) on [[Odysee]]/[[LBRY]]. It is {{Glossary|Open-Source|[[open-source software]].}}

It can be found at https://guncadindex.com

== Background ==
The GunCAD Index was created in early 2025 by [[The Shittinator]] in response to personal frustrations with searching for designs on Odysee. It was released on March 8th, 2025 and has been in continuous development ever since.

== Features ==

=== Searching ===
Arguably the most important feature of the Index, users can perform full-text searches against its database for 3D gun designs. Searches match against several fields of each release via a custom search algorithm.

=== Channel Auto-Discovery ===
The Index automatically discovers new gun designers based on a number of criteria:

* Channels for which any one single release has the "guncad" tag; and
* Channels for which:
** They have a release; and
** That release is identified by an automatic tagging rule (see below); and
** They are picked up by a search, which requires:
*** One of several dozen known-relevant tags on the channel (such as "guncad"); or
*** For any one release from that channel to be reposted by a channel already known by the Index
Between these discovery methods, the Index proves effective at discovering new creators, either by digging for them itself, voluntarily by the channel in question, or by other channels reposting content they find interesting.

As the process of channel auto-discovery can be problematic when bootstrapping new instances, a list of known channels is shipped with the software.

=== Tagging ===
The Index contains a mostly-hardcoded list of "tags" that can be applied to releases that correspond to various important features of it, such as what it is, what caliber of gun it is (if applicable), which if any OEMs are relevant when discussing it (such as Glock), and more.

Tags can wind up on releases via several mechanisms:

* They can be added via an automatic tagging rule, which looks at properties of the release (name, description, etc.) and performs regex matches against keywords. If a match is found, the tag is applied
* They can be added if an associated AI is configured and decides that a tag should be added
* Users can submit edits against releases suggesting the addition/removal of any tag. These suggestions are reviewed by an admin for legitimacy and either affirmed or discarded

=== API Access ===
Available via a link in the footer, the Index offers almost all of its data via a machine-readable REST API provided by the Django REST Framework.

=== Opt-Out ===
Channels with the "noindex" tag are excluded from all discovery and indexing. For a finer-grained approach, releases with the "noindex" tag are excluded from indexing without excluding the channel.

== Known Instances ==
As the GunCAD Index is open-source, it can be hosted by anyone with the requisite knowledge. The following is a list of all known public instances of the software:

* https://guncadindex.com

== Technical Details ==
The GunCAD Index is built on the Django framework and serves requests via Gunicorn. It uses PostgreSQL for its backing database and Redis (or Valkey) for caching. Requests must be served via a reverse proxy which also serves the role of managing static content.

It requires close contact with LBRY, and as such mandates the use of a [[lbrynet]] node. It periodically spiders LBRY in search of new channels it infers to be related to GunCAD ("authors") and the designs they produce ("releases") via a number of heuristics.

[[ Category:GunCAD Index ]]

Finding Tested Gun Designs

2026-02-01T18:46:31Z

Mission: /* Release Groups */

{{NeedsWork}}Downloading random files off the internet carries some risk, especially with regard to DIY firearms. For any given model, there might be no indication of how much testing is done, what the results of those tests were, what ammunition is acceptable, what safe handling looks like, how to clear the firearm, etc.

This guide will discuss best practices, how to avoid common pitfalls, and how to find reputable firearm designs.

== Best Practices ==

=== Release Groups ===
Many popular designs are published by [[Release Group|release groups]] who have ensured those designs underwent a minimum of beta testing before release. This does not discount the work of reputable independent designers like Timothy Hoffman or UnseenKiller.

=== Avoiding Betas ===
If a design is advertised as "in [[beta]]," it may be presumed to be less tested (and therefore less safe) than validated and "released" designs.

=== Known Your Local Laws ===
In most parts of the world, building your own gun is of questionable legality. Many, if not most, 3D gun designs may also be illegal to possess where you live.

Even in the United States of America, there are many states and cities that have criminalized all or some part of the process designing or printing a 3D gun.

== When to Be Adventurous ==
TODO: Document when to eschew the previous suggestions, what skills you should have, what precautions you should take, and how doing so can contribute to guncad

== Finding Files ==
[[File:FGC-9 MkII Index Card.png|thumb|The FGC-9 MkII with a green stamp in the corner, indicating it meets the Index's quality standards.]]

=== GunCAD Index ===
The [[GunCAD Index]] ([https://guncadindex.com/ https://guncadindex.com]) is a guncad-specific search engine and a powerful tool for finding files. As its name implies, the GunCAD Index is an index of designs hosted elsewhere and '''does not itself host or serve any files.''' Instead, each listing at the Index provides links to where the file can be downloaded, such as [[Odysee]].

GunCAD Index has a feature that marks certain designs as "verified" via a stamp on the thumbnail. Verified releases meet a threshold for quality as defined on the Index's "About" page, which includes some amount of testing and good documentation.

Note that not all "unverified" releases are bad. Users are encouraged to investigate files that pique their interest even if they don't have a stamp, especially for low-risk things like furniture.

=== Odysee ===
[[Odysee]] ([https://odysee.com/ https://odysee.com]) is a file hosting website, and is where the vast majority of 3D2A files are actually hosted. In a pinch, it can be browsed directly, albeit without any of the Index's quality-of-life features.
[[Category:Guides]]

Finding Tested Gun Designs

2026-02-01T18:45:01Z

Mission: /* Best Practices */

{{NeedsWork}}Downloading random files off the internet carries some risk, especially with regard to DIY firearms. For any given model, there might be no indication of how much testing is done, what the results of those tests were, what ammunition is acceptable, what safe handling looks like, how to clear the firearm, etc.

This guide will discuss best practices, how to avoid common pitfalls, and how to find reputable firearm designs.

== Best Practices ==

=== Release Groups ===
Many popular designs are published by [[release groups]] who have ensured those designs underwent a minimum of beta testing before release. This does not discount the work of reputable independent designers like Timothy Hoffman or UnseenKiller.

=== Avoiding Betas ===
If a design is advertised as "in [[beta]]," it may be presumed to be less tested (and therefore less safe) than validated and "released" designs.

=== Known Your Local Laws ===
In most parts of the world, building your own gun is of questionable legality. Many, if not most, 3D gun designs may also be illegal to possess where you live.

Even in the United States of America, there are many states and cities that have criminalized all or some part of the process designing or printing a 3D gun.

== When to Be Adventurous ==
TODO: Document when to eschew the previous suggestions, what skills you should have, what precautions you should take, and how doing so can contribute to guncad

== Finding Files ==
[[File:FGC-9 MkII Index Card.png|thumb|The FGC-9 MkII with a green stamp in the corner, indicating it meets the Index's quality standards.]]

=== GunCAD Index ===
The [[GunCAD Index]] ([https://guncadindex.com/ https://guncadindex.com]) is a guncad-specific search engine and a powerful tool for finding files. As its name implies, the GunCAD Index is an index of designs hosted elsewhere and '''does not itself host or serve any files.''' Instead, each listing at the Index provides links to where the file can be downloaded, such as [[Odysee]].

GunCAD Index has a feature that marks certain designs as "verified" via a stamp on the thumbnail. Verified releases meet a threshold for quality as defined on the Index's "About" page, which includes some amount of testing and good documentation.

Note that not all "unverified" releases are bad. Users are encouraged to investigate files that pique their interest even if they don't have a stamp, especially for low-risk things like furniture.

=== Odysee ===
[[Odysee]] ([https://odysee.com/ https://odysee.com]) is a file hosting website, and is where the vast majority of 3D2A files are actually hosted. In a pinch, it can be browsed directly, albeit without any of the Index's quality-of-life features.
[[Category:Guides]]

Release Group

2026-02-01T18:37:21Z

Mission: /* Purpose */

{{Stub}}

A '''release group''' is a developer organization that coordinates the design, testing, documentation and/or publication of files. Release groups most often work with developers to provide them access to beta testers, and will also work with them to improve and standardize their build guides and documentation.

For a list of active release groups, see [[:Category:Release Groups]].

== History ==
Release standards among developers were in large part established by [[Deterrence Dispensed]] and [[AWCY?]] before 2020. Early 3D gun developers had a reputation for incomplete documentation and a disinterest in creating build guides or explaining their print settings and testing histories.

== Purpose ==
Release groups like [[The Gatalog]] are purposefully integrated to evaluate a developer's initial design, to oversee that design's beta testing, and to work with the developer to publish a final and "standard" release version of that design. The Gatalog is known for having a "[[beta manager]]" who works with developers, and administrators who review designs and their documents before publication.

=== Beta Testing ===
TODO: Document how groups tend to require releases undergo testing, how that's typically coordinated. [[Glossary:Beta]]?

=== Quality Control ===
TODO: Document how release groups act like a filter via beta managers blocking garbage from being released

Release Group

2026-02-01T18:36:55Z

Mission: /* History */

{{Stub}}

A '''release group''' is a developer organization that coordinates the design, testing, documentation and/or publication of files. Release groups most often work with developers to provide them access to beta testers, and will also work with them to improve and standardize their build guides and documentation.

For a list of active release groups, see [[:Category:Release Groups]].

== History ==
Release standards among developers were in large part established by [[Deterrence Dispensed]] and [[AWCY?]] before 2020. Early 3D gun developers had a reputation for incomplete documentation and a disinterest in creating build guides or explaining their print settings and testing histories.

== Purpose ==
Release groups like The Gatalog are purposefully integrated to evaluate a developer's initial design, to oversee that design's beta testing, and to work with the developer to publish a final and "standard" release version of that design. The Gatalog is known for having a "beta manager" who works with developers, and administrators who review designs and their documents before publication.

=== Beta Testing ===
TODO: Document how groups tend to require releases undergo testing, how that's typically coordinated. [[Glossary:Beta]]?

=== Quality Control ===
TODO: Document how release groups act like a filter via beta managers blocking garbage from being released

Release Group

2026-02-01T18:36:08Z

Mission: A good start

{{Stub}}

A '''release group''' is a developer organization that coordinates the design, testing, documentation and/or publication of files. Release groups most often work with developers to provide them access to beta testers, and will also work with them to improve and standardize their build guides and documentation.

For a list of active release groups, see [[:Category:Release Groups]].

== History ==
Release standards among developers were in large part established by Deterrence Dispensed and AWCY? before 2020. Early 3D gun developers had a reputation for incomplete documentation and a disinterest in creating build guides or explaining their print settings and testing histories.

== Purpose ==
Release groups like The Gatalog are purposefully integrated to evaluate a developer's initial design, to oversee that design's beta testing, and to work with the developer to publish a final and "standard" release version of that design. The Gatalog is known for having a "beta manager" who works with developers, and administrators who review designs and their documents before publication.

=== Beta Testing ===
TODO: Document how groups tend to require releases undergo testing, how that's typically coordinated. [[Glossary:Beta]]?

=== Quality Control ===
TODO: Document how release groups act like a filter via beta managers blocking garbage from being released

User:Mission

2026-02-01T18:24:31Z

Mission: Created page with "3D2A Absolutist."

3D2A Absolutist.