Difference between revisions of "Talk:Main Page"

From Gladiabots Wiki
Jump to: navigation, search
Line 92: Line 92:
  
 
This is not wrong. Halving for a draw happens not outside the rounding part
 
This is not wrong. Halving for a draw happens not outside the rounding part
 +
: true --[[User:Pier4r|Pier4r]] ([[User talk:Pier4r|talk]]) 22:16, 20 September 2017 (CEST)
  
 
[[File:League score delta.png|778px]]  
 
[[File:League score delta.png|778px]]  
Line 237: Line 238:
 
30
 
30
 
</math>
 
</math>
 +
 +
: since the italic font is normally used for single letter (or short) variables. I would use monospaced or "normal text" for longer variables. Moreover it is more compact. An alternative is saying "score_player" as "s_p" and then explaining all the shortening after the formula. --[[User:Pier4r|Pier4r]] ([[User talk:Pier4r|talk]]) 22:16, 20 September 2017 (CEST)

Revision as of 21:16, 20 September 2017

Global ToDo List

Comments

Nice idea to make an overview of todos --Pier4r (talk) 13:56, 6 September 2017 (CEST)

Really a huge work Lubeno! I feel doing nothing but I know how wiki works, it is endless so I will recover later (as I did a bit before on orum and reddit). Still, super kudos for the effort! --Pier4r (talk) 21:15, 13 September 2017 (CEST)

Guideline for structure

Let's agree slowly on a guideline for the wiki structure otherwise it will end having several pages about related topics --Pier4r (talk) 20:53, 22 August 2017 (CEST)

For example I am going to (slowly) collect the info of all those meta thread about the game. I'll put this under the page/namespace "Meta information". So like: "Meta information:data:recorded_best_scores" --Pier4r (talk) 21:04, 22 August 2017 (CEST)

I think there should be an easy to use navigation tree. All articles should be accessible by 2 or 3 steps. For your example: IMO there should be an article about the elo and in it should be the link to the subpage elo_recorded_best_scores or similar. I don't mind the naming convention this much. For me it is important to have it either direct in the navigation tree or easy to find in the articles of it. --LuBeNo (talk) 11:21, 26 August 2017 (CEST)

Yeah that is not a problem. The idea of main pages shown in a tree with 2-3 clicks is reasonable (having everything 2-3 clicks away is not). For example: introduction page -> "meta" (one click), then a list of subtopics and "best scores" (2nd click).
I do like the actual list of topics. Yet I am unsure about the Strategies section. That can grow slowly. I mean, I will keep the structure but I would compress the "Strategies" section to one page that then can be split up.
Another point is: in general is not bad to set a topic first, and then see how things evolve from this refactoring the pages. For example imagine a page about strategies. It grows, and then get split in more pages. Trying to do everything detailed from the start may backfire.

--Pier4r (talk) 12:58, 26 August 2017 (CEST)

Videos

As an heavy wiki user, I do not see videos properly unless they are organized in their pages (like a page for videos). Normally videos breaks the flow of reading (indeed they do not require reading at all) and so mess up with an entire page unless they are at the end or, as wrote, in their own pages. --Pier4r (talk) 12:05, 3 September 2017 (CEST)

  • I would probably put the video back on the top instead of the bottom or at the top of introduction. IMO GFX47 should tell what he thinks / decide. --LuBeNo (talk) 00:33, 4 September 2017 (CEST)

Tests

[math]E=mc^2[/math]

This is not wrong. Halving for a draw happens not outside the rounding part

true --Pier4r (talk) 22:16, 20 September 2017 (CEST)

League score delta.png

[math] Score\ delta_{player} = round \left ( K \cdot \left ( \begin{Bmatrix} {victory:1} \\ {draw:0.5} \\ {defeat:0} \end{Bmatrix} - \frac{1} {1 + 10^{ \left ( {Score_{opponent}} - {Score_{player}} \right ) / 400 } } \right ) \cdot \begin{Bmatrix} {draw:0.5} \\ {else:1} \end{Bmatrix} \right ) [/math]


[math] \Delta \tt{score_{player}} = round \left ( K \cdot \left ( \begin{Bmatrix} \tt{actualResult} \\ \tt{victory:1} \\ \tt{draw:0.5} \\ \tt{defeat:0} \end{Bmatrix} - \frac{1} {1 + 10^{ \frac{ \tt{score_{opponent}} - \tt{score_{player}} }{400} } } \right ) \right ) \cdot \begin{Bmatrix} \tt{multiplier} \\ \tt{draw:0.5} \\ \tt{else:1} \end{Bmatrix} [/math]

League score delta example.png

[math] Score\ delta_{player} = round \left ( 40 \cdot \left ( 1 - \frac{1} {1 + 10^{ \left ( {1200} - {1000} \right ) / 400 } } \right ) \cdot 1 \right ) = round \left ( 40 \cdot \left ( 1 - \frac{1} {1 + 10^{ 0.5 } } \right ) \right ) = 30 [/math]

[math] \Delta \tt{score_{player}} = round \left ( 40 \cdot \left ( 1 - \frac{1} {1 + 10^{ \frac{ \tt{1200} - \tt{1000} }{400} } } \right ) \right ) \cdot 1 = round \left ( 40 \cdot \left ( 1 - \frac{1} {1 + 10^{ 0.5 } } \right ) \right ) = 30 [/math]

since the italic font is normally used for single letter (or short) variables. I would use monospaced or "normal text" for longer variables. Moreover it is more compact. An alternative is saying "score_player" as "s_p" and then explaining all the shortening after the formula. --Pier4r (talk) 22:16, 20 September 2017 (CEST)