#kulche's suggestion discussion
trail fossilBOT
real yew
(should probably have been 'dependent', not 'dependant') (cope harder)
civic saddle
Why is a moderator suggesting
real yew
.. why wouldn't i
real yew
lobby has been completely unresponsive for the past several months
civic saddle
Maybe he died
limber escarp
Can't you just tell lobby💀
Just because you are mods doesn't mean you got favour
Everyone is equal
civic saddle
Just because you are mods doesn't mean you got favour
Okay
neon mist
Introducing such a feature would create significant headaches:
- When approving a plugin, moderators would have to vet the contents of the plugin AND its dependencies, increasing workload.
- A bad actor could on purpose break a widely-used dependency, instantly breaking the dependent plugins.
- Dependency hell. If plugin A requires plugin C v1 and plugin B requires plugin C v2, the game cannot load both simultaneously. This conflict can cause unpredictable errors, crashes or other problems.
Instead, vendoring is suggested. Essentially, it means that the creator includes a copy of the necessary shared code directly within their plugin.
trail fossilBOT
:lock: einfach.irgendjemand closed this for the following reason:
Answered.
real yew
@neon mist can I encrypt my code into a plugin and then nest it in other plugins?
I assume "once": true is enough for a lua script to only load once
neon mist
No for the first one, yes for the second one. Use plugin channels for further questions.