Update package and module name to match the GitHub repository name#2
Conversation
|
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. |
|
@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.2You 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 It is not a complete format implementation yet. |
|
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 |
There is a mismatch between the module (
.../pak1) name and the github repository (.../pac1) resulting ingo getcomplaining 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