Gathering detailed insights and metrics for bc-minecraft-project
Gathering detailed insights and metrics for bc-minecraft-project
Gathering detailed insights and metrics for bc-minecraft-project
Gathering detailed insights and metrics for bc-minecraft-project
A Typescript library for dealing with minecraft bedrock project data
npm install bc-minecraft-project
Typescript
Module System
Node Version
NPM Version
TypeScript (97.07%)
JavaScript (1.76%)
PowerShell (1.17%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
BSD-3-Clause License
1 Stars
492 Commits
1 Forks
3 Watchers
4 Branches
7 Contributors
Updated on Jul 14, 2025
Latest Version
1.21.73-4
Package Id
bc-minecraft-project@1.21.73-4
Unpacked Size
40.69 kB
Size
7.74 kB
File Count
15
NPM Version
10.8.2
Node Version
20.19.2
Published on
Jul 05, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
A Typescript library for dealing with minecraft bedrock project data
1let project = MCProject.loadSync("some folder");
2
3//First way of getting data
4let tags = project.definitions.tag;
5if (tags && tags.defined.includes('target')) {
6 ...
7}
8
9//Second way of getting data
10let tag = MCDefinition.getOrAdd(project.definitions, "tag");
11if (tag.defined.includes("target")) {
12 ...
13}
14
15//First way of getting project attribute
16if (project.attributes.diagnose === "true") {
17 ...
18}
19
20//Second way of gettin project attribute
21if (MCAttributes.getOrAdd(project.attributes, "diagnose", "false") === "true") {
22 ...
23}
24
This standard will introduce 3 new file that will help with project definition, attributes, excluded/includes of folders/files and settings that deal
with project for minecraft bedrock.
The file can be found in the root of the project. The following files will be added:
The file with the name: .mcattributes
. This file stores any of the settings or attribtues related to the project. Which uses universal determined
keys along each project. Each tool/program may also introduce each own set of keys, aslong as they are unique to the tool/program. Other
programs/tools simply ignore these keys. But when overwriting the file, must keep the old keys from other tools or programs.
A wider specification can be found in McAttributes
Example
1diagnose=true 2diagnose.objectives=true 3diagnose.tags=true 4diagnose.mcfunctions=true 5 6world.area_used=0 0 0 1000 256 1000
This file specifies anything that is included in the project, but cannot be found in the project files itself, or not easly. At the same time the user can also blacklist definition through this same project.
A wider specification can be found in McDefinitions
Example
1## I am a comment 2 3## Tags used in the map 4tag=initialized 5tag=calculating 6tag=enemy 7tag=monster 8 9## Tags to be black listed 10tag=!Monster 11 12## Objectives used in the map 13objective=var 14objective=coin 15objective=foo 16 17## Objectives blacklisted 18objective=!Var 19objective=!Coin 20 21## Families 22family=npc 23 24## Families Blacklisted 25family=!Npc 26 27## Entity names 28name=Steve 29 30## Entity names blacklisted 31name=!steve
Based upon .gitignore
. This file specifies through glob-patterns what files, folder to included/excluded from the project.
A wider specification can be found in McIgnore
Example
1## This is a comment 2## this will ignore the folders/file called Template 3Template 4 5## This will included file/folders that are in a folder called template and have the name and extension: settings.json 6!Template/settings.json
First, read the contributing guide. fork the project, clone it and run the following commands:
Installation
1 npm ci 2 npm update
No vulnerabilities found.
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
2 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 5
Details
Reason
Found 0/7 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-14
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More