{"action":"opened","issue":{"url":"https://api.github.com/repos/SleepyTrousers/EnderIO/issues/2506","labels_url":"https://api.github.com/repos/SleepyTrousers/EnderIO/issues/2506/labels{/name}","comments_url":"https://api.github.com/repos/SleepyTrousers/EnderIO/issues/2506/comments","events_url":"https://api.github.com/repos/SleepyTrousers/EnderIO/issues/2506/events","html_url":"https://github.com/SleepyTrousers/EnderIO/issues/2506","id":80465609,"number":2506,"title":"ME Conduits do not connect to adjacent P2P Tunnels on server restart","user":{"login":"predakanga","id":830645,"avatar_url":"https://avatars.githubusercontent.com/u/830645?v=3","gravatar_id":"","url":"https://api.github.com/users/predakanga","html_url":"https://github.com/predakanga","followers_url":"https://api.github.com/users/predakanga/followers","following_url":"https://api.github.com/users/predakanga/following{/other_user}","gists_url":"https://api.github.com/users/predakanga/gists{/gist_id}","starred_url":"https://api.github.com/users/predakanga/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/predakanga/subscriptions","organizations_url":"https://api.github.com/users/predakanga/orgs","repos_url":"https://api.github.com/users/predakanga/repos","events_url":"https://api.github.com/users/predakanga/events{/privacy}","received_events_url":"https://api.github.com/users/predakanga/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-25T09:26:53Z","updated_at":"2015-05-25T09:26:53Z","closed_at":null,"body":"This is potentially a duplicate of #2028, but I think the issue experienced by @Mad-Virus (https://github.com/SleepyTrousers/EnderIO/issues/2028#issuecomment-86051965) and myself is different to the OP.\r\n\r\nIn short, if you have an ME Conduit connected to the tunnelled side of an AE2 P2P Tunnel (that is, the side that makes use of the tunnel, not the side that carries it), the conduit will be unable to reconnect after a server restart.\r\n\r\nThe issue can only be resolved by removing and re-placing the conduit or tunnel; using the wrench to adjust the conduit's inputs and outputs does not help, as the tunnel's direction is grayed out.\r\n\r\n@MatthiasMann suggests in #2028 that the issue is due to AE2 not sending neighbour changed events - would it be possible to work around this by storing in the conduit's NBT (or wherever you store conduit settings - not too familiar with EIO source) that a conduit is attached to an AE2 device and on load, delay the connectivity check by a tick or two to allow the AE2 devices to initialize?\r\n\r\nThe issue occurs regardless of whether the conduit is inside a facade, and happens very regularly - almost every restart triggers the issue, though there are some rare instances where the conduits will reconnect with no problem.\r\n\r\nKnown Affected Versions:\r\nEnderIO-1.7.10-2.2.8.367.jar (FTB Direwolf20 1.3.1 pack)\r\nENDER IO 1.7.10-2.2.8.349 (FTB Infinity 1.2.1 pack)\r\n\r\nScreenshots\r\nPre-restart: ![2015-05-25_19 11 13](https://cloud.githubusercontent.com/assets/830645/7794898/b01f0110-0312-11e5-9518-b2b0f5fd9a76.png)\r\nPost-restart: ![2015-05-25_19 11 40](https://cloud.githubusercontent.com/assets/830645/7794899/b0246f2e-0312-11e5-82d1-a4338f50a5b1.png)\r\n\r\nAs an SSP player, this is quite a pain - having to rewire hidden sections of my base on each reload is not very fun, which is why I suggest a workaround for now."}}