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

Piston Machine not entering other territories #1393

Open
Jacobpaul22 opened this issue Jul 10, 2020 · 1 comment
Open

Piston Machine not entering other territories #1393

Jacobpaul22 opened this issue Jul 10, 2020 · 1 comment

Comments

@Jacobpaul22
Copy link

Debug info

Run /f debug mini and paste or screenshot all four lines here.
10.07 10:06:19 [Server] INFO Paper version: git-Paper-291 (MC: 1.15.2)
10.07 10:06:19 [Server] INFO Server ID: 99f27f70-c2a7-4fac-afac-0032000edfb9
10.07 10:06:19 [Server] INFO Plugin version: 1.6.9.5-U0.5.15-b234
10.07 10:06:19 [Server] INFO Java version: 11.0.7

Logs

Give us your logs by going to logs/latest.log.
https://gist.github.com/Jacobpaul22/1ecfbbb1f17218cc3a57df42dead9b5e

Details

I'm trying to allow the use of a "flying piston machine" (specifically a machine called a slime drill) to move into Faction claimed territory and be able to move blocks that a slime block and piston can normally move. To see the exact same machine that I'm using, I referenced this video: https://www.youtube.com/watch?v=k6R45TCKXTE&t=265s

When I build this machine on my server and test it out in the wilderness, it works perfectly fine. However, whenever the machine approaches a different territory (e.g. wilderness entering into faction claimed territory OR even warzone entering into wilderness), it stops right at the border of the two territories, and returns to its original spot, as if it came into contact with an immovable wall.

In the main.conf, I have disablePistonsInTerritory=false and I made sure to ask in the Discord before posting here. This is my first time using the Issue Tracker, so if I did anything wrong or didn't include enough information, I sincerely apologize! Please let me know if you need any other information from me on my end, and I'll reply ASAP.

@CmdrKittens
Copy link
Collaborator

Having looked closer at the code, the disable configuration option prevents all movement ever in a territory, while enabling it still requires build permission between territories. As in, you could move your machine between connected allied territory if allies were granted build permissions.

I'm open to the idea of adding an additional control over pistons being allowed separate from build perms, but this does open up quite a lot of damage possibilities by enemy factions.

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

No branches or pull requests

2 participants