Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add comments into config.yml #31

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ShadedJon
Copy link

Added comments for most of the config options. I am unsure what EnderPearl's scaleFac does.

Added comments for most of the config options. I am unsure what EnderPearl's scaleFac does.
@Maxopoly
Copy link

Thanks for adding this, the documentation of Bastion is kinda sketchy

Ender pearl scale fac is how much damage a pearl deals to the bastion. Also could you sign the CLA, it can't be merged before that.

@spaceFountain
Copy link

As compared to how much it would do if someone placed a block.

On Fri, Oct 16, 2015 at 7:10 AM Max Baumstark [email protected]
wrote:

Thanks for adding this, the documentation of Bastion is kinda sketchy

Ender pearl scale fac is how much damage a pearl deals to the bastion.
Also could you sign the CLA, it can't be merged before that.


Reply to this email directly or view it on GitHub
#31 (comment).

@ShadedJon
Copy link
Author

Signed.

@ShadedJon ShadedJon closed this Oct 17, 2015
@ShadedJon ShadedJon reopened this Oct 17, 2015
@Maxopoly
Copy link

Could you add a line for enderpearl scaleFac?

blocksToErode: 1
# how many bastions break when a field is breached. set to 0 to destroy all overlapping bastions.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to set this to a negative number if you want all the overlapping bastions to lose durability. Setting this to 0 will cause bastions to be unbreakable. Please fix.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It also refers to the number of blocks damage gets applied to when someone places a block (or maybe also tries to teleport though I think there can only be one blocking field for that in the code), not how many get destroyed when the field is broken.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah your explanation of the setting is much better.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blocks to erode shoudl be negative? I need to check that in the live
config, had some complaints earlier this week.

On Sun, Oct 18, 2015 at 2:58 PM, BlackXnt [email protected] wrote:

In Bastion/config.yml
#31 (comment):

blocksToErode: 1
+# how many bastions break when a field is breached. set to 0 to destroy all overlapping bastions.

Yeah this is a much better way of explaining it^


Reply to this email directly or view it on GitHub
https://github.com/Civcraft/Bastion/pull/31/files#r42327089.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ttk2 I think it was changed back to a negative number after we moved to 1.8: #17 The repo was never updated tho so it will be nice if you can upload the current config we are running.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, should I just pull and then push or do you suggest a different method?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you don't want to pull the repo you can edit the file through the browser(by clicking on the edit button in the page of the file) and copy-paste what you have on the server, just make sure you keep the yml format right. the outcome will be the same.

@idoash4
Copy link

idoash4 commented Oct 18, 2015

You should be placing comments in the top part of the file, before any uncommented text. Otherwise the comments will be deleted if the plugin edits the file (e.g a command that changes the value of one of the settings and requires the plugin to edit the file and save it).

@ShadedJon
Copy link
Author

@BlackXnt can you explain more what you mean by your last comment?

@CivcraftBot
Copy link

Can one of the admins verify this patch? Type 'ok to test' to test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants