[dwh]

Originally Posted by MarcoH64

You can see a Plugin as an externally definable include.

What you are talking about has nothing to fo with Plugins, but with standard functions offered, and maybe with approaching this as OOP classes.

Thanks for explaining it.

To tell the truth, I'm pretty disappointed by this. It sounds like adding a ton of complexity to something as simple as inserting a bit of code in a file. This might actually make upgrades worse. Includes need to happen at the right place. I'd rather look at the code on one page when upgraded to see if the placement has to change. Now if there are 3 mods working on a similar piece of code, it will be much harder to get a feel of the flow of the code. As it is, with regular code, to follow the logic you need to look at all the included files. I've found that to be quite a pain several times, but there it's understandable. I dunno. Maybe it will all work out, but I'm wondering if this is such a good thing...

What's the big benefit? Just to make mods easier to install for newbies?

(Just in case this comes off wrong, I'm not trying to say this in a negative manner or just to nag...I also want to check if I'm understanding this properly and give feedback about it. As always, I want it clear that I love vb!)