Skip to content

Update package and module name to match the GitHub repository name#2

Merged
WoozyMasta merged 1 commit into
WoozyMasta:masterfrom
bogdannbv:master
Jun 4, 2026
Merged

Update package and module name to match the GitHub repository name#2
WoozyMasta merged 1 commit into
WoozyMasta:masterfrom
bogdannbv:master

Conversation

@bogdannbv

Copy link
Copy Markdown
Contributor

There is a mismatch between the module (.../pak1) name and the github repository (.../pac1) resulting in go get complaining that the names don't match.

$ go get github.com/woozymasta/pac1
go: github.com/woozymasta/pac1@upgrade (v0.1.0) requires github.com/woozymasta/pac1@v0.1.0: parsing go.mod:
        module declares its path as: github.com/woozymasta/pak1
                but was required as: github.com/woozymasta/pac1

@bogdannbv bogdannbv changed the title Update package and module name to match the GitHub repository's name Update package and module name to match the GitHub repository name Jun 3, 2026
@WoozyMasta

Copy link
Copy Markdown
Owner

Oh fuck, thanks for catching that. The format is literally pac1, and somehow I still managed to write pak1 in go.mod.

Good thing only you, me, and the Go toolchain saw this.
Merging it and pretending it was intentional 😂

@WoozyMasta WoozyMasta self-assigned this Jun 4, 2026
@WoozyMasta WoozyMasta merged commit d1caaaa into WoozyMasta:master Jun 4, 2026
1 check failed
@WoozyMasta

Copy link
Copy Markdown
Owner

@bogdannbv, thanks again.

The module should now install correctly:

$ go get github.com/woozymasta/pac1
go: downloading github.com/woozymasta/pac1 v0.2.0
go: added github.com/woozymasta/pac1 v0.2.0
go: added github.com/woozymasta/pathrules v0.1.2

You can try using it now, but as you have already seen, this thing is not exactly production-ready yet if bugs this dumb are still sitting on the surface.

I tested it against original game files and a few mods, so no strong compatibility guarantees for now.

Also, if resourceDatabase.rdb support is ever needed, there is a prototype in #1. It can read/write FORM/RDBC, supports the observed node types (2/4/5/6/7/22), and should roundtrip safely for the layouts covered so far.

It is not a complete format implementation yet. Key64, FieldA, FieldB, reserved header fields, and mod-heavy type 2 records still need more research.

@bogdannbv

Copy link
Copy Markdown
Contributor Author

First of all, awesome work! So far I haven't encountered any noticeable issues.

Good thing I decided to dig a bit deeper for existing implementations before starting to write my own 🫩 (a bit tired of writing random parsers lol)

I'm working on an external mod manager/syncer because lately, at least on Linux, the game keeps failing download them so I've ran it against hundreds of popular mods and everything worked as expected 😁.

Atm I don't think I really need RDB support, but I'll deffo give it a try if it ever comes to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants