Difference between revisions of "User:DnaGonite/sandbox"
(Test) |
|||
| Line 1: | Line 1: | ||
| + | {{Tree-Arrow-Right|1}} | ||
| + | |||
Hey, just putting this comment here. I've been twisting the HTML allowed here on the wiki for the past couple of years and so far, this is the work I've made thus far. https://wiki.warthunder.com/index.php?title=User:U16697154&oldid=16302 If you take a look through the history tab on my page, you can also find all the other nonsense I've been up to. None of which are allowed on the main wiki for the foreseeable future unfortunately. | Hey, just putting this comment here. I've been twisting the HTML allowed here on the wiki for the past couple of years and so far, this is the work I've made thus far. https://wiki.warthunder.com/index.php?title=User:U16697154&oldid=16302 If you take a look through the history tab on my page, you can also find all the other nonsense I've been up to. None of which are allowed on the main wiki for the foreseeable future unfortunately. | ||
Revision as of 21:22, 12 May 2020
Hey, just putting this comment here. I've been twisting the HTML allowed here on the wiki for the past couple of years and so far, this is the work I've made thus far. https://wiki.warthunder.com/index.php?title=User:U16697154&oldid=16302 If you take a look through the history tab on my page, you can also find all the other nonsense I've been up to. None of which are allowed on the main wiki for the foreseeable future unfortunately.
That being said, feel free to keep experimenting. - KornFlaks (talk) 17:15, 17 April 2019 (UTC)
Contents
Visual Editor breaks table for some reason
No idea what the cause is, but Visual Editor seems to randomly add a breakpoint at a random space. Current work-around is to use nbsp as space in table to prevent this.
May be unrelated, but VE didn't insert a return char between Attacker and Bomber nav-lines in cases where table broke.
For reference
I think it is possible to data-mine the tank optics zoom. In a tank BLK file if you divide 74 by the "zoomOutFov" or "zoomInFov" field that gives you the default and zoomed in magnification (it has a load of decimal points after it but when you round it to 1 d.p it is nearly always accurate, sometimes you will be out by 0.1 x though). Not sure the significance of 74, presumably it is the FoV of a 1x zoom or something. I worked this out by taking the standard zoom of the Challenger 2 (stated as x 4 in game), then multiplying it by the "zoomOutFov" field in the challenger 2 blk file to get 74. If I then pick other tanks in game which have a zoom specified and divide 74 by the "zoomOutFov" & "zoomInFoV" fields in their files the number you get nearly always rounds to what the zoom level was stated at in game. --Flame2512 (talk) 12:32, 28 April 2019 (UTC) [1]
Tech-tree fiddling
|
|
|
|
|
|
|
|
| |
II Rank
|
 M10 GMC  |
StuH 42 G  Pz.IV F2   ▀M4 748 (a)  StuG III G  |
T-34 (1941)  T-34 (1942)  |
␗T-34 (1943)  |
▄M10 GMC  |
Inserting codeblocks in numbered lists
- Create a new file with *.blk extension
- Copy all this code below to the BLK file and use it as a template:
className:t="composit"
node{
type:t=""
name:t=""
tm:m=[[1.0, 0.0, 0.0] [0.0, 1.0, 0.0] [0.0, 0.0, 1.0] [0.0, 0.0, 0.0]]
}
- Step 3
