Closed corylulu closed 4 years ago
Side note: I do like how Kotlin is able to automagically cast a variable type if it's inside an
if(val is someType)
rather than still haven't to explicitly cast it afterwards. It's even simpler than theif(val is someType val2)
that C# has... Pretty cool.
Yup, I really like the whole type handling of Kotlin. Just awesome!
Yeah. It's not bad.
The next thing that I figured out was an issue is the fact that the senders/receivers aren't linked to a player, which can result in two players making sender items one after another, then each make a receiver items and it results in both the receivers going to the second sender.
I was having weird issues like that. Perhaps it could also be solved by creating a receiver automatically after a sender hoe is used on a chest to ensure it correctly pairs. Would also allow for a bunch of them to be made by an OP, then people can just grab one and start using it without having to know any commands.
Yeah. It's not bad.
The next thing that I figured out was an issue is the fact that the senders/receivers aren't linked to a player, which can result in two players making sender items one after another, then each make a receiver items and it results in both the receivers going to the second sender.
I was having weird issues like that. Perhaps it could also be solved by creating a receiver automatically after a sender hoe is used on a chest to ensure it correctly pairs. Would also allow for a bunch of them to be made by an OP, then people can just grab one and start using it without having to know any commands.
Yaeh you are right about this. Pleas open an issue for that. I already have a solution in mind.
From my initial testing, this seems to work.
Side note: I do like how Kotlin is able to automagically cast a variable type if it's inside an
if(val is someType)
rather than still haven't to explicitly cast it afterwards. It's even simpler than theif(val is someType val2)
that C# has... Pretty cool.