"New Core"?

[1joneselliot]

In the community scripts website there is a notice in the news section, "New Script PRs Temporarily Paused", which talks about a migration to a "new core". I'm curious what this means and what we might expect feature-wise. I looked around and didn't find anything that stood out to answer my question. Just curious, appreciate any help!

[1joneselliot]

Some of this is discussed in this PR: #16749, which helps. If there's any user-facing announcement of what the "new core" is and why it's better than the "old core", I'm curious to read for my own knowledge!

[MickLesk]

Short version: the engine moved out of the script repo into its own one, community-scripts/core.

Before, every ct/*.sh pulled misc/build.func from this repo — engine and scripts shipped together. Now a script loads the engine from core and carries only its own declarations.

What that changes for you:
Fixes land once. A bug in the update logic, the APT handling or the GPU setup is fixed in one place and every script picks it up on the next run — instead of a 600-file PR that ages badly.

Incus: The host backend is chosen at runtime, so the same scripts run on Incus too. That repo mirrors ct/ and install/ automatically; only the bootstrap line differs.

Killer Feature:
You can test a fork of the engine. COMMUNITY_SCRIPTS_CORE_URL points at any branch or fork, so engine changes can be tried without touching the script repo. The old layout made that effectively impossible, which is the main reason for the split. (Like our bot in the current PR's f.e.: #17279 (comment)

Scripts stay readable. What's left in a ct/ script is the application, not the plumbing — 35 engine files live in core now. The Old "misc" Folder in ProxmoxVE will be removed in next days.

Nothing changes in how you use them: same one-liner, same update inside the container.