why not just add it to the dependancy plugin? 

StackModifier is plenty big enough and there would be no point in merging the 2.

Why would you make another plugin more complex just so you don't have to run 2 plugins?

You'd just be overly complicating a whole plugin that no maintainer would want to take over/touch at that point.  

Also, you could have @me in discord or pm'd me to talk about this instead of needlessly creating a help thread on the plugin page. 

If you want this plugin to actually work as a stand-alone plugin then make a request.

yet it is required in the new version to have the other installed to make it work.
For me being the first to ask is not needed to react in this fashion btw.

As a serverowner i love both plugins

Yes, there are good reasons for that. One is it allows more plugin compatibility support ( when running both ) another being it relies on the other to stop abuse/exploits that arise while using this plugin. ( like stack abuse/manipulation ) many other problems. I refuse to merge the 2 because of the below issues.

When the server boots with StackModifier I have to backup all vending machine /vendor orders then apply all the stack modifications and then restore all the vending machine/vendor orders back to defaults. 

And once that is all done I have to make sure this plugin does its modifications only after StackModifier finished loading ^ otherwise if your stackmodifier plugin like ( stacksizecontroller ) etc loads after this plugin guess what happens?

This plugin won't work cuss the other stack modifier plugin overrides it.

So unless you want to mark and support all the other Stack-related modifier plugins with a thousand if checks to know which plugin they run on a server just to run each x / y / z  scenario code fixes for each different scenario. It's not worth it.