Describe the feature

The Problem

Currently, I believe KubeJS lacks something in the reusability/distribution department. Let's say I've made a custom block and want to share that with someone. From the files I've sent, they'll need to put the startup script (which adds the block) in startup_scripts, the server script (which adds a recipe for the block) in server_scripts, and the texture in assets/kubejs/textures/block. To install multiple "packs" of scripts and textures like this sounds like a real pain.

The Solution

KubeJS packs: add a new folder: .minecraft/kubejs/packs, or maybe .minecraft/kubejs_packs. This folder could then contain folders and/or zip archives, structured similarly to data/resource packs:

pack_name/
├─ pack.mcmeta
├─ startup_scripts/
├─ server_scripts/
├─ client_scripts/
├─ assets/
└─ data/

The pack.mcmeta file would be a JSON containing a "description" and a "pack_version": 1 in case the format changes. Every pack in the folder would automatically get loaded, with startup_scripts run at startup, data and server_scripts loaded/ran on server load, and assets and client_scripts loaded/ran on client load.

Additional info

No response