{"action":"opened","issue":{"url":"https://api.github.com/repos/OpenRCT2/OpenRCT2/issues/4054","repository_url":"https://api.github.com/repos/OpenRCT2/OpenRCT2","labels_url":"https://api.github.com/repos/OpenRCT2/OpenRCT2/issues/4054/labels{/name}","comments_url":"https://api.github.com/repos/OpenRCT2/OpenRCT2/issues/4054/comments","events_url":"https://api.github.com/repos/OpenRCT2/OpenRCT2/issues/4054/events","html_url":"https://github.com/OpenRCT2/OpenRCT2/issues/4054","id":164823885,"number":4054,"title":"Sorting rides by track type: Misleading research messages","user":{"login":"Wuzzy2","id":1675853,"avatar_url":"https://avatars.githubusercontent.com/u/1675853?v=3","gravatar_id":"","url":"https://api.github.com/users/Wuzzy2","html_url":"https://github.com/Wuzzy2","followers_url":"https://api.github.com/users/Wuzzy2/followers","following_url":"https://api.github.com/users/Wuzzy2/following{/other_user}","gists_url":"https://api.github.com/users/Wuzzy2/gists{/gist_id}","starred_url":"https://api.github.com/users/Wuzzy2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Wuzzy2/subscriptions","organizations_url":"https://api.github.com/users/Wuzzy2/orgs","repos_url":"https://api.github.com/users/Wuzzy2/repos","events_url":"https://api.github.com/users/Wuzzy2/events{/privacy}","received_events_url":"https://api.github.com/users/Wuzzy2/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-11T12:19:52Z","updated_at":"2016-07-11T12:19:52Z","closed_at":null,"body":"**OS:** GNU/Linux (Parabola)\r\n**Version:** 0.0.5-develop\r\n**Commit/Build:** [e.g. 426e106]\r\n\r\n- Reproducible in RCT2 (vanilla)? No.\r\n- Multiplayer? N/A\r\n\r\nThe setting “Sort rides by track types” has usability problems and may make things actually even more confusing to the average non-developer player.\r\n\r\nProblem: Misleading notification messages\r\n\r\n**Steps to reproduce:**\r\n 1. Activate setting “sort rides by track type”\r\n 2. Research something which is lumped together\r\n 3. Read the notification message carefully\r\n\r\nExample: If you research Spinning Wild Mouse, you won't find it in the attraction list (but as “Wild Mouse”). So the notification message just screwed you. ;-)\r\nThe example in general: Rides X and Y are merged and displayed as “X” in the build list. Player has ride X researched. Then researches compatible ride Y. Gets message that ride Y has been researched. Looks into build window but does not find Y, only X. Player may not now that Y is actually X since the names of X and Y are different.\r\n\r\nThe problem: The notification message might be technically correct, but the point of the setting is to pretend that two rides with different cars are really just the same ride and therefore only get 1 entry in the build ride list. The message suggests the player could find a new ride in a build list but this is not true. What the player actually has to do is to look in the car tab of existing rides.\r\n\r\nHere is proof that this is a real usability problem, not just something I just imagine:\r\nhttps://github.com/OpenRCT2/OpenRCT2/issues/3975\r\n\r\nLong example:\r\nGiven that Wild Mouse and Spinning Wild Mouse are both considered the same ride (as “Wild Mouse”) when using this setting:\r\nAssume you already have researched the “normal” Wild Mouse.\r\nIf you research “Spinning Wild Mouse”, you get the message that the spinning wild mouse has been researched but because of the setting, there never appears a ride of this name in the list. Instead, the old “Wild Mouse” is still there.\r\n\r\nWhat actually happened? Well, technically, you have researched the spinning wild mouse, but from an user perspective things things are a bit different. Since the point of this setting is to pretend that the spinning wild mouse is actually the wild mouse with a different cart, the notification message seems to fail to “follow the spirit”.\r\n\r\nWhat I suggest to fix this:\r\nThe notification message should be written in a way that (indirectly) points the user to the correct window using the correct (user-visible) names (not the real names).\r\n\r\nIn the original RCT it was possible to research explicitly for new track tiles and cars. In OpenRCT2 a similar message could be used in such a case.\r\nIn my spinning wild mouse / wild mouse example, the message could be along the lines of “New car for Wild Mouse available: Spinning Wild Mouse”. This message is better because it tells the player exactly where to look, namely, in the car options of existing (pseudo-)wild mouse rides, whereas the original message suggests to look in the attractions which is of course misleading.\r\n\r\nThe final question which remains is which message to display when a completely new ride/track (not just a “car” variant) has been researched. For example, if you have (internally) neither researched wild mouse and rotating wild mouse, then research either of them, the research message should claim you have researched wild mouse. Generally, the research message should show always pretend you researched the ride which will be displayed in the build window. So if you research rotating wild mouse, it should still say you researched wild mouse because it will be displayed as “wild mouse” in the build menu, not as “rotating wild mouse”.\r\n\r\n"}}
{"actor":{"display_login":"Wuzzy2"}}