ProbeJS Legacy 3.10.0 -> 4.0.0

A huge update, see ProbeJS 7 release note and another ProbeJS 7 release note for more details.

But of course PJS Legacy 4 will not be a one to one copy of PJS 7, exact implementations vary a lot, and there can also be differences in features.

Full Changelog: https://github.com/ZZZank/ProbeJS-Legacy/compare/3.10.0...4.0.0

ProbeJS Legacy 2.6.1 -> 3.0.0

Rich display info dumping

What's new?

• ProbeJS Legacy will now dump rich display informations about items, fluids, blocks, tags, and lang keys, providing rich display in VSCode when ProbeJS(VSCode Extension) is installed.
  

• for items, it can display:

• item id,

• localized name(or lang key if no localization is avaliable),

• whether it's block or item or crop, max stack size, and

• special infomations for tools and foods and etc.

• If you have icons exported via Icon Exporter, icons for such item can also be displayed.

• for fluids, it can display

• id,

• localized name(or lang key if no localization is avaliable),

• whether it has a fluid block, and

• whether it has a fluid bucket item.

• for lang kays, it can display:

• all valid localization under similar locale, and en_us

• it's really hard to name them all, please try it by yourself.

• config "disabled" is now replaced by "enabled", to make ProbeJS VSCode extension happy.

• Old config will be automatically upgraded.

• .vscode now will be generated at .minecraft/ folder, aka game folder, making workspace more useful.

• Snippets of registries now support all avaliable registry types, e.g. potion and enchantment

• ProbeJS now fetch registries and tags from Minecraft internals, instead of relying on an external json file.

• This change prevents reloading and exporting data when /probejs dump is triggered, which makes dumping much much FASTER, especially on a large modded instance.

• Also, autoExport config is removed because of this.

• Use different method filtering approaches for classes and interfaces, so we should be able to filter out duplicated methods more completely.

• Set default values for configs, so that first-time users will not get a all-disabled config

• ProbeJS Legacy now dump registries into special.d.ts instead of registries.d.ts

• More datas, including tags and platform data, will be dumped into special.d.ts

• dumping messages are improved now, roughly showing stages of dumping.

• class DamageSource will now show accepted assginments in its type. E.g. 

type DamageSource_ = "inFire"|"lightningBolt"|"onFire"|"lava"|"hotFloor"|"inWall"|"cramming"|"drown"|"starve"|"cactus"|"fall"|"flyIntoWall"|"outOfWorld"|"generic"|"magic"|"wither"|"anvil"|"fallingBlock"|"dragonBreath"|"dryout"|"sweetBerryBush"|DamageSource;

Commit history

ProbeJS Legacy 1.6.0 -> 2.0.0

A huge update, adding support for Document, Forge event listening, full config with autosave, and much much more

What's new?

• Collected class/methods/... will now be dumped to `kubejs/probe/` folder, instead of `kubejs/kubetypings/` folder.

• ProbeJS can now dump more classes/methods into `global.d.ts`

•     On a slightly modded 1.16.5 Forge instance, ProbeJS can now dump about 164000 lines, 4.4 times of previously 37700 lines.

• ProbeJS can now dump java access related data better.

•     On a slightly modded 1.16.5 Forge instance, ProbeJS can now recognize and dump about 2000 method presets, 33% more than previously 1500.

• An actual config file will be generated at `kubejs/config/probe.json`, and will be automatically saved on change(through command).

• Event dumping now supports `onForgeEvent()`

• Correctly resolves types used by List/Map

• Types will have `_` appended to prevent conflict

• better support for RecipeSerializer

• Remove `dump.js` generation, because it seems completely useless

• Support getters

• and many small changes, for a better experience

ProbeJS Legacy 1.?.? -> 1.6.0

The first release of ProbeJS 1.16.5 unofficial continuation.

What's new?

• ProbeJS now mixins into event listening, so you no longer need captureEvent to capture fired events.

• Fix command arguments. /probejs previously will do what /probejs dump does, that's fixed now.

• Add semi-comma in dump.json to handle malformed tag key, like per-viam-invenire:replace_vanilla_navigator, whose `-` will causes troubles

• Respect kubeJS annotations.

• Ported from https://github.com/Prunoideae/ProbeJS-Forge/commit/549118a44d07b5e7a10f0ff71ac8ce5338a7066e

• You can use `/probejs config xxxx` to access configs. Currently you can use `/probejs config dump_export` to toggle dump.json generating on or off