Bukkit

@leagris Enhanced ownership...I dunno, that's going to be rather tricky. How exactly would you imagine it being used? (note that owners are per minecart/train)

I dislike adding 'special' tools though, it results in conflicts most of the time. Let's keep it obvious shall we? :)

Right (?) click with rail on rail A connection (normal rail) is made facing the direction you look. Facing towards an up-slope? A slope is made. Block place event is fired (can place), no item is subtracted.

Right click with minecart onto minecart / place minecart Based on the sneaking position, alternates between TC and default minecarts. Entering/interacting with the minecart is only cancelled when minecart type is changed. This entire feature will probably be a configuration option, by default false.

The command I can add.

I'm not sure how many people are interested in the right-click sneak/nosneak system, so yeah, should I really implement this knowing that only one person will ever use it? Kinda the issue.

The track switching suggestion is a good idea, and a very useful one, too. I will also add the command to change between the two.

@Etsija @DJTomek Changes for TrainCarts build #92: - Sorted item transfer is now implemented, with width and height radius. Use negative radius value to transfer from/to outer to inner - SpawnItemDrops property for minecarts, can be set using property signs and using command /train or /cart spawnitemdrops true/false. spawnitemdrops is the property name.

Do note that servers previously using the default spawnitemdrops false in the config.yml will have to edit defaulttrainproperties (after restart) so they are set false there. Existing trains are probably left unaffected, and you will have to manually set those to false, or edit trainproperties.yml and put 'spawnitemdrops: false' after each displayed cart.

That is all.

@DJTomek Yup, I can add that, and I will add it. It's a simple matter of moving the 'spawnItemDrops' property from config.yml to train props. I will make it a cart property, but it can be set for entire trains.

@DJTomek Hmn no, there are no permissions set for who can pick up what items, and TC does not keep track of the destroyed minecart items. You can set permissions for who can destroy trains, however.

Do you need a train 'spawn drops' property? I can easily add it. :)

@Etsija I am now going to finish off the sign ordering system. Format will be a bit simple, like this, since I have a text length limitation:

• You can set two numbers: width and height
• Width 5: Will look for chests from the center to 5 blocks away
• Width -5: Will look for chests from 5 blocks away to center
• Height: Similar format as width
• Example: chest in 1:-3 ==> Looks from Y=-3 and 3 towards the center for chests. This will do?

@Trioxinz 1.) What version of TC is it that you are using? If not the latest found on the dev-build server, update first.

2.) See also 1. There is a train.place.traincart permission, only players with that permission can place a traincarts minecart. By default this is TRUE for everyone.

@ThePersonally Dev-build of TC (see above) and BKC 1.52 dev-build.

@Jacold I still need to decide on a good way to have the best of both worlds. Some people only want the default movement control that is in Minecraft, others, like you, want absolute control sort of like uCars can on rails.

My best option is to add a train property that sets whether 'full control' is enabled...would that do for you?

@XanvvdeR 1.) LINK 2.)

As requested, I added a 'jumper' sign. It's still in a very primitive form, as I want to expand it further, but for now, 'it works'.

[+cart/train]
jump
velx/vely/velz

What this does, is jump a single cart, or all carts of a train, at the given offset towards a certain direction. The offset is relative to the sign like eject offsets are, which means you can jump forwards using 0.0/0.6/1.0

Mind you: this feature required me to add several other changes so it properly works. In addition, I also fixed some issues with trains sometimes hanging 'stuck' in the air when jumping up vertically.

Please, if you use it, test everything carefully to see if all physics are behaving as they should. I did, but not very extensively. Keep a close eye on vertical rails especially.

I'm now going to look into some sort of way to do item transferring in an order fashion. I previously got stuck because of limited line space to put arguments, so I may decide to add aliases for the sign name to make room for more arguments.

@leagris Was a properties sign error, forgot that the / separator now also allows a 'true or false' setting based on sign power level. Had to add an exemption. Latest version fixes your problem.

Now looking into the ordering argument for transfer signs.