{"action":"created","issue":{"url":"https://api.github.com/repos/aidancbrady/Mekanism/issues/3073","labels_url":"https://api.github.com/repos/aidancbrady/Mekanism/issues/3073/labels{/name}","comments_url":"https://api.github.com/repos/aidancbrady/Mekanism/issues/3073/comments","events_url":"https://api.github.com/repos/aidancbrady/Mekanism/issues/3073/events","html_url":"https://github.com/aidancbrady/Mekanism/issues/3073","id":127133340,"number":3073,"title":"Logistical transporters \"seize up\" when overloaded?","user":{"login":"pfmoore","id":1110419,"avatar_url":"https://avatars.githubusercontent.com/u/1110419?v=3","gravatar_id":"","url":"https://api.github.com/users/pfmoore","html_url":"https://github.com/pfmoore","followers_url":"https://api.github.com/users/pfmoore/followers","following_url":"https://api.github.com/users/pfmoore/following{/other_user}","gists_url":"https://api.github.com/users/pfmoore/gists{/gist_id}","starred_url":"https://api.github.com/users/pfmoore/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pfmoore/subscriptions","organizations_url":"https://api.github.com/users/pfmoore/orgs","repos_url":"https://api.github.com/users/pfmoore/repos","events_url":"https://api.github.com/users/pfmoore/events{/privacy}","received_events_url":"https://api.github.com/users/pfmoore/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-01-17T23:53:38Z","updated_at":"2016-01-18T09:39:23Z","closed_at":null,"body":"I'm not sure if this is a genuine bug with logistical transporters, but there's something odd going on, so I thought I'd raise an issue in case it was more obvious to you what was going on.\r\n\r\nI've got a network of logistical transporters - 6 chests fed by hopperhocks, all with advanced logistical transporters connected in \"pull\" mode. The transporters run together into a single central \"trunk\" line that connects to a series of (many - over 20) JABBA barrels. The transporters connect to the barrels in \"normal\" mode. There's no sorters or colouring involved - I rely on the fact that each barrel is locked to a single item type for routing.\r\n\r\nThings initially were working fine, but after a while (when I was AFK, so I don't know precisely what happened) the transporters stopped extracting items from the chests. From what I could tell, they seemed to have stalled on certain item types - if I removed the last stack(s) from the chest, to expose a new type of item, things would get extracted again for a while - but would then stall, sometimes mid-stack on a new type of item.\r\n\r\nI had this happen one time previously on a smaller scale system, and I had to swap barrels around to get things unstuck - it's as if the pipe connecting to (for example) the osmium essence barrel decided it would no longer accept osmium essence, but switching that barrel with the diamond essence barrel got both diamond and osmium moving again. But that was the only thing that did. I've broken and recreated transporters and barrels without success.\r\n\r\nI'm at a loss as to how to give you any better explanation of the issue. I haven't been able to reproduce it on a smaller scale, or in a predictable way. If you have any suggestions on how to investigate the issue, I'll be happy to perform experiments. Or I can provide a savefile (it's the Regrowth modpack, not vanilla Mekanism, unfortunately) if that's of any use."},"comment":{"url":"https://api.github.com/repos/aidancbrady/Mekanism/issues/comments/172477289","html_url":"https://github.com/aidancbrady/Mekanism/issues/3073#issuecomment-172477289","issue_url":"https://api.github.com/repos/aidancbrady/Mekanism/issues/3073","id":172477289,"user":{"login":"pfmoore","id":1110419,"avatar_url":"https://avatars.githubusercontent.com/u/1110419?v=3","gravatar_id":"","url":"https://api.github.com/users/pfmoore","html_url":"https://github.com/pfmoore","followers_url":"https://api.github.com/users/pfmoore/followers","following_url":"https://api.github.com/users/pfmoore/following{/other_user}","gists_url":"https://api.github.com/users/pfmoore/gists{/gist_id}","starred_url":"https://api.github.com/users/pfmoore/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pfmoore/subscriptions","organizations_url":"https://api.github.com/users/pfmoore/orgs","repos_url":"https://api.github.com/users/pfmoore/repos","events_url":"https://api.github.com/users/pfmoore/events{/privacy}","received_events_url":"https://api.github.com/users/pfmoore/received_events","type":"User","site_admin":false},"created_at":"2016-01-18T09:39:23Z","updated_at":"2016-01-18T09:39:23Z","body":"Sorry, I really should know to provide proper information on bug reports :-)\r\n\r\nIt's the Regrowth modpack, version 0.9.1. The Mekanism version in that pack is 1.7.10-8.1.7.252. I'm running the world in a server on my local PC, which is Windows 10 64-but, with Java 8. The server is as downloaded from the FTB launcher. I'm running the client on the same PC, from the FTB launcher again.\r\n\r\nI've just checked the Mekanism site and I see there's a newer version. I'm happy to try that if you think it might help, but I've only ever used modpacks \"as delivered\" so far - is it just a case of putting the relevant jar files into the \"mods\" folder on the server and client? Regrowth does some pretty extensive changes to recipes, as I understand it - should I ask the Regrowth developer if there are any problems with putting in a newer version?"}}