Requesting the addition of a second config file that would assist in the maintenance of custom field types.

Right now upgrading rewrites the config.yml and changes are lost. Otherwise you have to determine if anything in the configuration formatting has changed and if it is safe to not upgrade the config.yml, thereby keeping custom changes.

It would be great if the default config.yml loaded a custom_fields.yml or custom_fields.txt file after the default one is done processing.

This would allow for the over-ride of the default block types without having to edit the config.yml that comes with each release.

It would also be nice if you added the ability to turn on or off the default block types from within the custom_fields.txt.

So, if I didn't want to use the Proximity Mine or the Shocker and I wanted to over-ride the Iron Block that is used in the Sky Canon, my custom _fields.txt may look like the following.

disabled-defaults:

• title: Proximity Mine
• title: The Shocker

custom-fields:

• title: Iron Deed
  block: 42
  radius: 7
  prevent-use:
• 58
• 61
  prevent-destory: true
  prevent-place: true

Now that you are making such great frequent updates, this feature would really help us upgrade to with the latest release as soon as its out.

Thank you for all your efforts and your kind consideration of the request!

A further thought on this would be to allow reassign of the default block type.

So maybe reworking my suggestion a bit to:

default_changes:

• title: Proximity Mine
  enabled: false
• title: The Shocker
  enabled: false
• title: Grief Revert
  block: 14

This would of course, disable Proximity Mine and Shocker and it would keep everything the same with the Grief Revert, but simply change the block type from a gold block to gold ore.

Again, the overarching theme is to allow easy changes that are commonly made to the default settings in a manner that does not require edits to the config.yml that comes with the release.

Defaults come with PS as examples of what can be done but they can be deleted if you don't want them, many people delete all of them and create their own or modify the defaults extensively. You can modify them however you wish. Default types that come in the config aren't anything special or better than those created by players. If you don't want to have some, then delete them, or copy/paste them somewhere for safe-keeping, no need for me to create settings for you to disable them.

There is also no need for you to overwrite your config on each new version. The config file is automatically rewritten adding any new config settings that were added on new versions every time you load PS. So you will always have all the new settings on your config file without needing to add them manually or to overwrite the file every time you upgrade. Just run the new version of PS on your old config file once, then open it and you will see all the new settings there.

Phaed420,

That write new changes to the config file on updating is full of win. I wish everybody did that.

I had no idea about the config thing! That is awesome! :) Thank you!