Regarding Change in Game Publishing Function
May 22, 2015 1:29:33 GMT 1
Ag and ᅚᅚ ᅚᅚᅚᅚᅚᅚ ᅚᅚᅚᅚᅚᅚ like this
Post by Jatsu on May 22, 2015 1:29:33 GMT 1
While the publish feature has always been available in-client, the recent addition of the screenshot feature is both convenient and appreciated. However, the removal of the website publishing features means that taking screenshots of games with logic states is less than desirable. In effect, these changes remove the ability to take screenshots while in Play mode, which has three consequences:
To clarify with example, please take a look at the current screenshot for Puzzle Me 2:
This screenshot shows one particular scenario of the multi-state puzzle. This is also representative of what a player would see in Play mode. However, due to the recent publishing change, only what can be seen in Edit mode can be captured in the screenshot. This means that all possible states that are laid out will be captured, potentially leading to a less clear and undesirable image. Here's an example:
The combination of model overlap in this example should be enough to display a negative aspect of this forced perspective. Other consequences include revealing hidden states not initially available in the area a screenshot is taken, revealing any models under the effect of a Model Enabler outline, and the inability to capture your avatar in the image. While the first issue is probably trivial to the majority (so few actually use logic), the other two create issues where players use Model Enabler outlines for the illusion of glass and using popular or themed avatars to boost the intrigue of a game's screenshot.
Edit: Oh, solutions... Since it's unclear if the standalone or webgl version will be used in the future, one solution that could work for both is to include a Publish and Take Screenshot button in the Play mode's menu. It's likely there'll be an issue with the large "Play" button in the center of the screen when a player presses 'M' while in Play mode. Another solution is to bind each function to a key that's usable in Play mode. Informing players of this key would be a separate issue. One more possible, but less likely solution is the possibility of reforming the function of the Tab key since score tracking has less use due to tracking UI on the top of the screen and its blatant lack of meaningful information across all game objectives. The Tab key could then be used to reveal publishing and other UI while it's held. Those are just some ideas though. I doubt they're any good. Maybe they might lead to a better design for implementation.
- Logic states in a particular scenario can no longer be individually presented.
- Model Enabler outlines will be overlapped by models that could be deactivated.
- Capturing your own avatar in the screenshot is impossible.
To clarify with example, please take a look at the current screenshot for Puzzle Me 2:
This screenshot shows one particular scenario of the multi-state puzzle. This is also representative of what a player would see in Play mode. However, due to the recent publishing change, only what can be seen in Edit mode can be captured in the screenshot. This means that all possible states that are laid out will be captured, potentially leading to a less clear and undesirable image. Here's an example:
The combination of model overlap in this example should be enough to display a negative aspect of this forced perspective. Other consequences include revealing hidden states not initially available in the area a screenshot is taken, revealing any models under the effect of a Model Enabler outline, and the inability to capture your avatar in the image. While the first issue is probably trivial to the majority (so few actually use logic), the other two create issues where players use Model Enabler outlines for the illusion of glass and using popular or themed avatars to boost the intrigue of a game's screenshot.
Edit: Oh, solutions... Since it's unclear if the standalone or webgl version will be used in the future, one solution that could work for both is to include a Publish and Take Screenshot button in the Play mode's menu. It's likely there'll be an issue with the large "Play" button in the center of the screen when a player presses 'M' while in Play mode. Another solution is to bind each function to a key that's usable in Play mode. Informing players of this key would be a separate issue. One more possible, but less likely solution is the possibility of reforming the function of the Tab key since score tracking has less use due to tracking UI on the top of the screen and its blatant lack of meaningful information across all game objectives. The Tab key could then be used to reveal publishing and other UI while it's held. Those are just some ideas though. I doubt they're any good. Maybe they might lead to a better design for implementation.