{"action":"created","issue":{"url":"https://api.github.com/repos/Blood-Asp/GT5-Unofficial/issues/204","labels_url":"https://api.github.com/repos/Blood-Asp/GT5-Unofficial/issues/204/labels{/name}","comments_url":"https://api.github.com/repos/Blood-Asp/GT5-Unofficial/issues/204/comments","events_url":"https://api.github.com/repos/Blood-Asp/GT5-Unofficial/issues/204/events","html_url":"https://github.com/Blood-Asp/GT5-Unofficial/issues/204","id":109484202,"number":204,"title":"Additional OreDict names for ores","user":{"login":"AT611","id":1901010,"avatar_url":"https://avatars.githubusercontent.com/u/1901010?v=3","gravatar_id":"","url":"https://api.github.com/users/AT611","html_url":"https://github.com/AT611","followers_url":"https://api.github.com/users/AT611/followers","following_url":"https://api.github.com/users/AT611/following{/other_user}","gists_url":"https://api.github.com/users/AT611/gists{/gist_id}","starred_url":"https://api.github.com/users/AT611/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AT611/subscriptions","organizations_url":"https://api.github.com/users/AT611/orgs","repos_url":"https://api.github.com/users/AT611/repos","events_url":"https://api.github.com/users/AT611/events{/privacy}","received_events_url":"https://api.github.com/users/AT611/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-10-02T12:46:02Z","updated_at":"2015-10-02T13:07:52Z","closed_at":null,"body":"We're using Logistics Pipes on our server, creating ore processing plants based on those pipes, and there is one small problem, when we're setting up filters using OreDict ItemSink modules: all versions (rock-based) of any ore have different ore dictionary names. For example:\r\n\"oreRedstone\" for generic (overworld) redstone ore\r\n\"oreEndstoneRedstone\" for endstone one\r\n\"oreRedgraniteRedstone\" for red granite based\r\nCould you add additional names for ores, like \"oreRedstoneAny\"? Because we need to add all variations of an GT ore we met into our filters all the time, and that's not only annoying, but also requires more chassis pipes to be installed on a machine."},"comment":{"url":"https://api.github.com/repos/Blood-Asp/GT5-Unofficial/issues/comments/145015653","html_url":"https://github.com/Blood-Asp/GT5-Unofficial/issues/204#issuecomment-145015653","issue_url":"https://api.github.com/repos/Blood-Asp/GT5-Unofficial/issues/204","id":145015653,"user":{"login":"AT611","id":1901010,"avatar_url":"https://avatars.githubusercontent.com/u/1901010?v=3","gravatar_id":"","url":"https://api.github.com/users/AT611","html_url":"https://github.com/AT611","followers_url":"https://api.github.com/users/AT611/followers","following_url":"https://api.github.com/users/AT611/following{/other_user}","gists_url":"https://api.github.com/users/AT611/gists{/gist_id}","starred_url":"https://api.github.com/users/AT611/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AT611/subscriptions","organizations_url":"https://api.github.com/users/AT611/orgs","repos_url":"https://api.github.com/users/AT611/repos","events_url":"https://api.github.com/users/AT611/events{/privacy}","received_events_url":"https://api.github.com/users/AT611/received_events","type":"User","site_admin":false},"created_at":"2015-10-02T13:07:52Z","updated_at":"2015-10-02T13:07:52Z","body":"That sounds like an option (and I'll give it a try in some way, shape or form), but not all ores needs to be processed the same way the default ones have. And collecting all the ores in one spot may be problematic: there is no priorities (only by module type, like \"itemsink > terminus\" and so on) in itemsink modules, and setting the \"default route\" on a processing plant is not an option for most of us. We could use the type filter to filter out all crushed ores from a HV macerator from all \"bonus\" dusts, but that's also not a problem with the current way we use. The problem is mostly with ores."}}