We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.bpk
What these files are....
BPKs are files that store within a package. A file inside the BPK named info.wif defines this pack. For example:
info.wif
"WaspInfo" { "ID" "WASP_TDB_PACK" "Name" "WASP - TheDarkBomber Pack" "Desc" "WASP items." "Icon" "pack.ico" "LargeIcon" "pack.jpg" } "BeeInfo" { "ID" "WASP_TDB_PACK" "Name" "WASP - TheDarkBomber Pack" "Desc" "Items created with WASP." "Pack" { "Package" { "Path" "example_package/info.txt" } } } `
"WaspInfo"
{
"ID" "WASP_TDB_PACK"
"Name" "WASP - TheDarkBomber Pack"
"Desc" "WASP items."
"Icon" "pack.ico"
"LargeIcon" "pack.jpg"
}
"BeeInfo"
"Desc" "Items created with WASP."
"Pack"
"Package"
"Path" "example_package/info.txt"
The text was updated successfully, but these errors were encountered:
I don't know how many times you have to bee told that BEE2.4 isn't geting BPK support!
Sorry, something went wrong.
Also, why are you just a collaborator? Shouldn't you be the owner?
I don't understand why you need to use these weird file extensions, like .bpk and .wif.
.wif
No branches or pull requests
.bpk
compatibility for BEE2.4What these files are....
BPKs are files that store within a package. A file inside the BPK named
info.wif
defines this pack. For example:"WaspInfo"
{
"ID" "WASP_TDB_PACK"
"Name" "WASP - TheDarkBomber Pack"
"Desc" "WASP items."
"Icon" "pack.ico"
"LargeIcon" "pack.jpg"
}
"BeeInfo"
{
"ID" "WASP_TDB_PACK"
"Name" "WASP - TheDarkBomber Pack"
"Desc" "Items created with WASP."
"Pack"
{
"Package"
{
"Path" "example_package/info.txt"
}
}
}
`
The text was updated successfully, but these errors were encountered: