Open-source project
owlboy/greatpug-public avatar
owlboy/greatpug-public

Great Pug public repo: the change log is the product documentation

A Bar in the Metaverse (VRChat)

60 stars6 forksShellLicense varies

At a glance

What is it?
greatpug-public is the public sister repository of a VRChat bar, and almost everything a visitor can learn lives in its dated change log: audio levels, pool table geometry, late joiner networking, VRChat SDK bumps and a security-driven removal of third party assets.
Who is it for?
This repository suits a visitor who wants to know what actually changed in a VRChat world between two dates, and a patron who wants to follow development without reading a wiki, because the change log entries are detailed and dated. It does not suit someone looking for the world assets themselves, since the public repository is the sister of a private one, and no licence is stated here.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Shell, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on October 22, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • owlboy/greatpug-public60 ★ · +0
Star history
Repository2026-08-212026-10-22
owlboy/greatpug-public6060

0 Stars in the last 62 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A public repository with a private twin

The Great Pug is described in one line as a bar in the metaverse in VRChat, and the README notes it now has a smaller sister bar, The Great Pug - West. This repository is stated to be the public sister repository to the private repository for the world, which sets the expectation correctly: you get announcements, not the build. The public surface is thin by design. The top level holds .github/, README.md and four directories, calendar/, data/, scripts/, tapsters/ and version/, and GitHub reports Shell as the primary language, which lines up with a scripts/ directory rather than with a Unity project. Bugs and feature requests are meant to go through the issues feature of this repository and to cover both bars. No licence is declared, the default branch is master, and the last push is dated 2026-09-29.

Dated entries are the whole documentation

There is no manual here, so the change log carries the weight. The most recent entries show the granularity. The 2026.08.28 entry updated patron flyers, turned the lights back up in Night View and put the Night View gate away. The 2026.08.14 entry turned the volume up on various audio sources, updated patron flyers and dimmed the Night View Hall. The 2026.08.08 entry reduced logging noise during scene join, improved logging across the scene, fixed help text on the Pool Table rendering in the wrong spot, and added Trust and Safety improvements. Read together, they describe a world that is tuned continuously rather than launched occasionally, and they make it possible to tell which of two builds a screenshot came from. The releases track the same cadence, with tags dated 2026.08.28, 2026.08.14 and 2026.08.08.

Third party assets were pulled for security reasons

One entry stands out from the rest, dated 2026.08.23: various third party assets were removed due to security concerns, with a note that they will return. That single line is the only security disclosure in the public record, and it is worth reading next to the dependency list rather than in isolation. The world is built on VRChat's own packages, com.vrchat.base and com.vrchat.worlds, both moved to v3.10.4 in the 2026.06.19 entry, alongside tip.udonutils at v14.0.4, tip.udonvoiceutils at v5.1.4, dev.onevr.vrworldtoolkit at v3.4.1 and com.acchosen.vr-stage-lighting at v2.8.4, plus Filamented updated to a named upstream commit. The 2026.05.02 entry shows the same set at earlier versions, which means the pins move deliberately and are visible in the log.

Late joiners and networking get the most lines

A large share of the entries is about state arriving correctly for people who were not in the room when it changed. The 2026.05.28 entry improves networking and sync logic for the Liquid System and for the pickup management systems, improves toggles for late joiners, and updates scripts to carry correct networking mode flags. The same entry fixed potential memory leaks in image loaders and in material swaps, added null checks, optimised distance checks and removed dead code. The 2026.08.07 entry improved the initialisation of the Room Tracker so lighting and state are correct right away, and fixed a bell that might not ring for some people when they entered. Sliding door logic was reworked in 2026.05.02 to improve sync behaviour and handles for desktop users, and again in March. This is the least visible and most expensive half of the work.

The Pool Table received more attention than anything else

The pool table is the clearest thread through the log, and it reads like an object being rebuilt in public. The 2026.08.07-B entry calls itself further refinements, adds new extra fancy pool cues, restores the light bars and changes how they work, improves the pool table UV mapping and texture quality, and adjusts the internal table geometry a little. The 2026.08.07 entry improves how the pool table works across many different dimensions. Smaller fixes follow: help text rendering in the wrong spot on 2026.08.08, occlusion issues with the pool cues on 2026.03.21, and pool ball shadow flickering on 2026.04.01. Volume was raised on some of the sounds along the way, and an air filter was added in The Roost to cut down on dust, which tells you the object sits in a room that people spend time in.

Rendering work shows up as leaks, culling and rebakes

Performance entries are written in engineering terms rather than marketing ones. In May 2026 there were fixes for potential memory leaks in image loaders and material swaps, a reduction in dead code, removal of unused objects and scripts from the scene, and better use of reflection probes. The April 2026 entries cover improved LOD transitions and culling, reduced overdraw in some areas, fixed collision on round side tables, couch legs and shelf objects, and fixed Light Volumes that were not active when they should have been in the first floor hallway. Rendering itself got its own pass: improved fog rendering credited to a contributor through issue 288, rebaked lighting to address errant shadows, rebaked occlusion, fixed exterior geometry holes and updated glass materials. The June entry adds improved texture VRAM usage and an improved overall download size.

The bar is funded by patrons and a seasonal event

The support section names three routes. Patreon covers ongoing maintenance, events and expansion, and Ko-fi is the direct donation link. The third is inside VRChat itself, through the Creator Economy store, where subscribing or tipping earns two perks: having your name displayed on the wall, and a minor jump increase for everyone in the instance that stacks with contributions from others. The 2026.05.02 entry shows that jump increase being rebalanced so the first few subscribers contribute a noticeably bigger boost, which is a small piece of design work spent on the reward itself. Events follow a yearly rhythm, with the tenth annual St. Patrick's at The Pug held on Saturday March 21st at 7pm Pacific, extra event photos hung afterwards, and the decorations and music removed on 2026.03.29. Presence outside the world is on Mastodon, Bluesky and Twitter, and the site is thegreatpug.com.

Editorial conclusion

This repository suits a visitor who wants to know what actually changed in a VRChat world between two dates, and a patron who wants to follow development without reading a wiki, because the change log entries are detailed and dated. It does not suit someone looking for the world assets themselves, since the public repository is the sister of a private one, and no licence is stated here. Before filing anything, use the issues tracker rather than the private repository, and if you depend on the world, note the August entry that removed third party assets for security reasons, since dependencies such as com.vrchat.base and com.vrchat.worlds move between releases.

Frequently asked questions

What is The Great Pug?

It is a bar in the metaverse in VRChat, and it now has a smaller sister bar called The Great Pug - West. The site linked from the repository is thegreatpug.com, and the world also appears on Mastodon, Bluesky and Twitter.

How do I report a bug in The Great Pug?

Use the issues feature of the greatpug-public repository, which is where both The Great Pug and The Great Pug - West bugs and feature requests are meant to be filed. This repository is the public sister of the private one, so the issues tracker is the intended contact point.

Which VRChat packages does The Great Pug depend on?

The change log shows com.vrchat.base and com.vrchat.worlds at v3.10.4, tip.udonutils at v14.0.4, tip.udonvoiceutils at v5.1.4, dev.onevr.vrworldtoolkit at v3.4.1 and com.acchosen.vr-stage-lighting at v2.8.4, with Filamented updated to a named upstream commit. Earlier entries record the same packages at lower versions.

How can I support The Great Pug?

Through Patreon for ongoing maintenance, events and expansion, through Ko-fi, or through the VRChat Creator Economy store. The store route adds two perks: your name displayed on the wall, and a minor jump increase for everyone in the instance that stacks with other subscribers' contributions.

How often is The Great Pug updated?

Frequently, and the record is dated. Recent releases are tagged 2026.08.28, 2026.08.14 and 2026.08.08, with change log entries under the same dates covering audio, lighting, the pool table, logging, collisions and Trust and Safety work, and the last push to the default branch master is dated 2026-09-29.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/owlboy-greatpug-public.svg)](https://hysenlabs.com/projects/owlboy-greatpug-public)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/owlboy-greatpug-public.svg)](https://hysenlabs.com/projects/owlboy-greatpug-public)