This message was deleted.

Depends on the details. If you for example set a value in that extension at execution time, that would not be a good idea. But it really depends on the exact details of the situation.

I have a task, that computes values, then sets them in the extension I then have another task from another plugin that requires that value I can make sure they run after each other

Easiest would be the wiring via task inputs / outputs I guess if the data need to be produced somehow (what I would guess).

the two tasks are otherwise independant, they are just running one after the other

But for that you have to write the value to a file / files. But depending on what it does, you could then also have the task up-to-date, and / or cached. To only share the values without files, a shared build service usually is the way to go. Maybe it would even just do the logic and not some task. Still depends on the gory details

Just wanted to follow-up here, i've implemented a BuildService which again uses ValueSources, own calculations etc. The BuildService can be shared between tasks and even plugins and has member variables containing the state. Works like a charm. So thanks for the suggestion 👍