Inital extra bed commit with back-compatibility

[ryantheleach]

I need some advice on how to continue, mainly what I should be worried about when it comes to permissions, whether to bother with the backwards compatibility checks and if theres any side-effects.

I've been running this code on my server for a few weeks now and havn't run into any problems (except permissions) but I'm not a heavy multiverse user.

Sorry about travis.yml and the gitattributes but github for windows was complaining and I wasn't sure how to fix the line numbering anyway, I'll pull request another fixed version at some stage.

[main--]

Your formatting is kinda ... fucked up. But I like the idea.

[ryantheleach]

what style guidelines does multiverse follow?

[fernferret]

We generally follow the same guidelines as bukkit, but that shouldn't matter a lot, we can just pull the request, run it through the autoformatter and be done with it. Summary: 4 spaces, spaces in places that make sense (see my comments on the message).

[ryantheleach]

Should I have added unit tests for this? What permissions should be set up for this?

mv.tp.self.b would default to own bed.
mv.tp.other.b would default to own bed.

does there need to be an additional permission for teleporting to someone elses bed?

[ammaraskar]

Any particular reason for keeping anything after the auto-lf normalization rule? I mean, the rest of it wont really matter to a java repository.

[ryantheleach]

honestly the only reason this is even in the commit is github for windows wouldn't stop nagging about it, so i just said, yes fix it, this is what it added.

[main--]

Never trust git GUIs. Things like this are exactly why I always commit and push from the command line.

[fernferret]

Never trust git GUIs.

👍

[main--]

Improved version: main--/Multiverse-Core@ce80fc1.

[ammaraskar]

Looks good to me, except maybe keep the auto lf change. Way too many people screw that up with PRs