{"action":"opened","issue":{"url":"https://api.github.com/repos/zyel/zyel/issues/3","labels_url":"https://api.github.com/repos/zyel/zyel/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/zyel/zyel/issues/3/comments","events_url":"https://api.github.com/repos/zyel/zyel/issues/3/events","html_url":"https://github.com/zyel/zyel/issues/3","id":113625914,"number":3,"title":"Improvement: Unsocketing recipes","user":{"login":"bloodyshade","id":1421140,"avatar_url":"https://avatars.githubusercontent.com/u/1421140?v=3","gravatar_id":"","url":"https://api.github.com/users/bloodyshade","html_url":"https://github.com/bloodyshade","followers_url":"https://api.github.com/users/bloodyshade/followers","following_url":"https://api.github.com/users/bloodyshade/following{/other_user}","gists_url":"https://api.github.com/users/bloodyshade/gists{/gist_id}","starred_url":"https://api.github.com/users/bloodyshade/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bloodyshade/subscriptions","organizations_url":"https://api.github.com/users/bloodyshade/orgs","repos_url":"https://api.github.com/users/bloodyshade/repos","events_url":"https://api.github.com/users/bloodyshade/events{/privacy}","received_events_url":"https://api.github.com/users/bloodyshade/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-27T16:33:56Z","updated_at":"2015-10-27T16:33:56Z","closed_at":null,"body":"Hi,\r\n\r\nThis isn't really an issue but a suggestion, could an unsocketing recipe be added (rem in this case, so we don't lose the socketed items in the process)?\r\n\r\nI searched inside cubemain.txt but didn't find a match for rem, or even uns so I'm guessing that isn't implemented, I can add it for myself, but I thought it would be a better solution if it was implemented into the main version.\r\nThis is one of the features I always wished the original had, but couldn't since it was still 1.09d, where the unsocketing opcodes didn't exist yet."}}