User talk:THE OWL

[[File:|link=|]]

This is the user talk page of User:THE OWL. To add a comment, use the Edit button near the headline of the appropriate section. To create a new section, you can use the Add topic button at the top of this page.
Comments on talk pages should be signed with "~~~~", which will be converted into your signature and a timestamp.

Should we use the original engine branch or current engine branch on software page template?

(using Template:Message)  Hey there, I was wondering whether or not we should use the current engine branch for the game on the software page template or the original. For example, should we use src04 or hl2 or src13? Equalizer5118, an idiot who cant spel (talk)  --Equalizer5118 (talk) 12:21, 28 March, 2023 (UTC)

(using Template:Message)  {{Src13}} and others don't give exact information about what exactly the game is based on. If you specify {{Src13}} for the conditional Half-Life 2, it turns out that the game is based on both versions at once - Singleplayer and Multiplayer.

I don't see any problems in using {{Src13}}, {{hl2}} and others if it will give enough information to understand what a person should use to create a similar game.  --THE OWL (talk) 5:45, 29 Mar 2023 (UTC)

(using Template:Message)  Aight, cool. Thanks man!  --Equalizer5118 (talk) 8:10, 29 March, 2023 (UTC)

hidden categories for Software page template

(using Template:Message)  Hey there, I have a question about the hidden categories for the Software page template. The current links that you have in the section link to categories with the abbreviations in the title (eg Ps3) instead of the full name from the /strings subpage (PlayStation 3). When I added automatic categories a little while back, I used the strings for the titles instead of the abbreviations. Should we use the existing full name categories or should we use the abbreviated categories?  --Equalizer5118 (talk) 20:46, 7 Apr 2023 (UTC)

(using Template:Message)  It would be more correct to use full names. Wiki should not take abbreviations as a basis, but it can use them for redirects.  --THE OWL (talk) 21:26, 7 Apr 2023 (UTC)

(using Template:Message)  Hmm, interesting. Your time zone is displayed incorrectly (I see UTC+7 instead of UTC-7)  --THE OWL (talk) 21:39, 7 Apr 2023 (UTC)

(using Template:Message)  Yeah, I noticed that as well. Thought it was a slight mistype on the user settings page that I fixed yesterday but apparently not. It displays correctly on my settings page though...  --Equalizer5118 (talk) 16:06, 7 Apr 2023 (UTC)

Restoring Template:Param to the Wikipedia import from revision 230178

(using Template:Message)  Hey c: This is an inquiry as to why Template:Param has regressed first and a recommendation for revertion second.

As of this message, Template:Param has regressed significantly from revision 230178:

• {{[safe]subst:param}} will substitute in the wrapping tag (here, <code>);
• the template always uses <code> instead of allowing the editor to specify a tag via {{{tag}}}, which may be semantically incorrect in some situations;

• a noticeable side-effect is that most template documentation pages specify parameters with the invocation {{code|{{param|foo}}}} which could be simplified to {{param|foo|tag=whatever}}, where tag is optional

• this saves space and reduces template expansion depths

• specifying the parameter value now requires a user-specified pipe character (e.g., {{Param|2=&#124;text}} or {{Param|2={{!}}text);

• this is unintuitive behaviour since this template is used to describe template parameters and not other WikiText syntax
• because the pipe character is no-longer transcluded, editors can misuse this template to notate non-template parameters (e.g., {{{

1. if|:syntax abuse}}})

• nesting parameters becomes tedious and potentionally unmanageable (e.g., {{param|foo|{{param|bar|{{param|baz|derp}}}}}} results in {{{foo|{{{bar|{{{baz|derp}}}}}}}}}; needs {{param|foo|{{!}}{{param|bar|{{!}}{{param|baz|{{!}}derp}}}}}} to produce {{{foo||{{{bar||{{{baz||derp}}}}}}}}})

• there is spurious functionality inappropriate for contexts outside of template documentation (selection, bold styles)

• this situation-dependent and should be left to the editor’s discretion

For these reasons, I would recommend reverting the template to revision 230178 (already tried; you’ve immediately reverted it). Understandably, editors have already updated other pages with these regressions in mind, so a revert will need tooling to maintain backwards-compatibility until all pages can be sanitized.  --結衣 (talk) 16:16, 29 Apr 2023 (UTC)

(using Template:Message)  Max34 told me that he is already improving the template taking into account what you said. Perhaps he has already finished his work :]  --THE OWL (talk) 17:39, 29 Apr 2023 (UTC)