I have the perfect addition/suggestion. Please read this carefully!

A long time ago, when this standalone plugin did not exist I did a very similar thing by removing the other MorePhysics features and leaving the Piston features standalone.

There was one thing I did at the time, which made the plugin 100x better. Every player on my server loved it and we all had a blast!

What I had done, was in the PistonListener.java I added a few lines of code right before it calculated velocity added to the entity. I will give a simple, brief summarized explanation below.

double signVelocity = 0;
int signplacement = Settings.Pistons.SignPlacement.toInteger(); //<this would need the SignPlacement option added into the config under Piston category>
if (sign exists (signplacement) blocks above the piston OR sign exists (signplacement) blocks below piston ) {  
    sign WoodSign //<here I defined the location of sign and declared the sign itself>
    string lineOne   =   read WoodSign line 1;
    if (lineOne = "[Piston]"){
        string lineTwo = get WoodSign line 2;
        signVelocity = StringtoDouble(lineTwo);
        set WoodSign line 4 = color.limegreen + "Activated"; 
    }
}

Then right before it set the entity velocity I added a line of code something like this

	diff.multiply(Settings.Pistons.EntitiesLaunchPower.toDouble());
        v.add(diff);
        v.multiply(signVelocity); //<this is what I added>
        entity.setVelocity(v);

(Obviously thee above is not my legitimate coding.)

Then on my server, for complete individual piston control - in the config I set the piston power to 1. I also disabled the whole weight aspect within the config. I also set the signplacement for 3 blocks.. (above / below - Making it 3 allowed a decent amount of room for redstone wiring to the piston) By applying these options in the config this then caused pistons to act like normal when a sign didn't exist above or below it. However when a sign did exist it multiplied the final entity velocity 1x the number given on the sign.. So we could put numbers on the sign giving us 1 x the velocity number given, allowing specific velocity control for each piston. This was great as it allowed configuring each piston for different types of TNT launchers, item launchers, player launchers etc.

Also when I modified the plugin it I did go as far as adding a listener for when a sign was placed and if the first line of the sign equaled [Piston] it would check if the player had the permission node, if not it would change the first line to blank. as well as, if they did have permission, check if the second line can be converted into the double, if it cannot change the first line to "[-Piston-]" and then the second line to color.red + "Invalid"

I'm sure other small modifications could be made to this concept like, example to disable looking for signs at all within the config.

Let me know if you will add this and when. I would like to use these features again and would be interested in allowing you to add this feature to this for others to use. (maybe even adding this to the MorePhysics plugin as well?) If so, and need assistance I can help with that too.

If you do not plan on adding this anytime soon. I would be interested in be allowed to update my version and posting it as a different plugin for all to use.

Thanks for the plugin! AND Thanks for reading this long message - Hope you take this into consideration!

Can we get this updated to 1.5.1?

Very cool!

Sorry i have see it so late xD... but BIG THX :D