How to contribute: Difference between revisions
No edit summary |
m caps at beginning of bullets and lists; other minor details |
||
Line 2: | Line 2: | ||
We encourage every kind of contribution. Here are a few examples what you could do: | We encourage every kind of contribution. Here are a few examples what you could do: | ||
* | * You can always fix problems, correct grammar, make sure wording is accurate, etc. (See Editing Pages) | ||
* | * Expand an article by covering another topic | ||
* | * Create videos for articles (How to create videos) | ||
* | * Write a new article. Topics includes a variety of topics yet to cover | ||
== Moderation == | == Moderation == | ||
Line 29: | Line 29: | ||
To use maps from videos in the wiki: | To use maps from videos in the wiki: | ||
# | # Right-click the video and click ‘View Video’, now you can find the name of the video in the URL | ||
# | # Go here and download the correct demo | ||
# | # Open the demo in your client (you need to move the demo into your <code>data/maps</code> folder) | ||
# | # While you have the demo open, go into the editor, click <code>File</code>, and select <code>Load Current Map</code> | ||
Now you can edit and use the map for the demo. | Now you can edit and use the map for the demo. | ||
Line 38: | Line 38: | ||
==== Variant 2: Creating a new map ==== | ==== Variant 2: Creating a new map ==== | ||
# | # Create a new map in the editor | ||
# | # Set the background color to <code>#5E84AE</code> | ||
## | ## Click on the <code>quads</code> layer | ||
## | ## Right-click the corners of the rectangle | ||
## | ## Insert the color value <code>#5E84AE</code> into the third to last field each each | ||
# | # The main focus should be that it is comprehensible | ||
# | # Keep the style simple and similar to the other videos | ||
#* | #* Use simple textures (preferably <code>grass_main</code>, combined with <code>generic_unhookable</code> and <code>font_teeworlds</code>) | ||
#* | #* Make it loopable, you can get creative with that :) | ||
#* | #* Insert a scale if suited | ||
=== Step 2.1: Recording the demo === | === Step 2.1: Recording the demo === | ||
# | # Turn demo recording on | ||
#* | #* I suggest <code>Settings -> General -> Automatically record demos</code> | ||
# | # Load the map on a server | ||
#* | #* Start your own DDNet server or use the [https://trashmap.timakro.de/ Trashmap] hosting service | ||
# | # Join it with your client, try the trick until you are satisfied with the result and keep loopability in mind | ||
=== Recording Settings === | === Recording Settings === | ||
Set consistent skin: | Set consistent skin: | ||
* | * Hammer: brownbear | ||
* | * Pistol: coala | ||
* | * Shotgun: cammo | ||
* | * Grenade: redstripe | ||
* | * Laser: bluestripe | ||
* | * Hook: default | ||
* | * Jump: bluekitty | ||
=== Step 2.2: Cutting the demo === | === Step 2.2: Cutting the demo === | ||
# | # In your client, go to <code>Demos -> auto/</code> | ||
# | # Open the demo you recorded | ||
#* | #* Tip: Click on <code>Date</code> to sort by date | ||
# | # Press <code>Escape</code> for demo functions | ||
# | # Use the 2 buttons on the left of the camera icons to select a starting and end point | ||
# | # Use the camera icon to save the shortened demo | ||
Tip: you can repeat these steps multiple times to be able to cut the demo more precisely | Tip: you can repeat these steps multiple times to be able to cut the demo more precisely | ||
Line 82: | Line 82: | ||
Once you have the client, converting a demo is as simple as: | Once you have the client, converting a demo is as simple as: | ||
* | * Open the client (with the converting functionality) | ||
* | * Set zoom to 10: <code>cl_default_zoom 10</code> | ||
* | * Go to the <code>Demos</code> tab | ||
* | * Select the correct demo | ||
* | * Click <code>Render</code> at the bottom | ||
=== Step 4: Cropping the video === | === Step 4: Cropping the video === | ||
Line 93: | Line 93: | ||
To use it: | To use it: | ||
# | # First '''edit the <code>crop.sh</code> script to set the <code>PIXEL_PER_TILE</code> value correctly!''' | ||
# | # Use it as a commandline tool: | ||
#* | #* The first argument is the input video file | ||
#* | #* The second argument is the output video file | ||
#* | #* The third to sixth arguments are each, how many tiles upwards/downwards/to the left/to the right should be seen in the video | ||
# | # Try different settings to get the best result | ||
# Remember to '''include the exact command you used in the commit message, as well as your <code>PIXEL_PER_TILE</code> value'''! | # Remember to '''include the exact command you used in the commit message, as well as your <code>PIXEL_PER_TILE</code> value'''! | ||
Line 104: | Line 104: | ||
You don’t have to be familiar with git to create a merge request: | You don’t have to be familiar with git to create a merge request: | ||
# | # Go to the folder view | ||
# | # Click on the drop-down menu next to the <code>videos</code> folder | ||
# | # Click <code>Upload file</code> | ||
# | # Upload all relevant files this way, for each video include the .demo | ||
# | # Click on the blue button <code>Commit...</code> | ||
# | # Write into the ‘Commit Message’ what you are changing (e.g. which video you are adding) | ||
# | # Insert the crop command(s) you used from step 4! | ||
# | # Create a new branch; it should be selected by default, if not, tick it | ||
# | # Press the green button ‘Commit’ | ||
=== Step 6: Insert videos in pages === | === Step 6: Insert videos in pages === | ||
See About for how to edit pages. Adding <nowiki>{{% vid vid-name %}}</nowiki> to markdown pages includes <code>/video/vid-name.mp4</code> in the | See About for how to edit pages. Adding <nowiki>{{% vid vid-name %}}</nowiki> to markdown pages includes <code>/video/vid-name.mp4</code> in the HTML page. | ||
== Templates == | == Templates == |
Revision as of 18:42, 21 January 2021
What to contribute?
We encourage every kind of contribution. Here are a few examples what you could do:
- You can always fix problems, correct grammar, make sure wording is accurate, etc. (See Editing Pages)
- Expand an article by covering another topic
- Create videos for articles (How to create videos)
- Write a new article. Topics includes a variety of topics yet to cover
Moderation
Changes made to the wiki go to a moderation queue, where moderators will check if the change you made is vandalism.
Here are our practices we follow when moderating content, which the extension itself recommends:
Recommended use / good practices when moderating
The following good-practices are advised:
- Only vandalism should be Rejected. Not-so-good edits with good intentions (e.g. adding excessive plot details into the Wikipedia article about film) are better made Approved and then reverted as usual. This way the author is not offended and the text is saved in page history, viewable by anyone.
- Any user that is deemed legitimate (does N good edits) should be added into
automoderated
group. - Adding users to
automoderated
group via$wgAutopromote
is NOT recommended, as it motivates the vandals to do many very-minor edits (e.g. adding interwiki). Better promote them toautomoderated
manually for one good edit and not promote for 30 useless-edits-made-for-count. - Abstain from using blocks. Don't protect pages "just in case", except maybe for important templates.
- Allow the full rehabilitation of users with a bad history of editing. Their useful edits to the articles should be allowed, no matter how many times they were blocked. At the same time, trolling on talk pages should be rejected, so are the purposely-low-quality edits.
How to create a video
(TODO: Update this section to be usable on the new wiki)
Step 1: Getting a Map
Variant 1: Using an existing map
To use maps from videos in the wiki:
- Right-click the video and click ‘View Video’, now you can find the name of the video in the URL
- Go here and download the correct demo
- Open the demo in your client (you need to move the demo into your
data/maps
folder) - While you have the demo open, go into the editor, click
File
, and selectLoad Current Map
Now you can edit and use the map for the demo.
Variant 2: Creating a new map
- Create a new map in the editor
- Set the background color to
#5E84AE
- Click on the
quads
layer - Right-click the corners of the rectangle
- Insert the color value
#5E84AE
into the third to last field each each
- Click on the
- The main focus should be that it is comprehensible
- Keep the style simple and similar to the other videos
- Use simple textures (preferably
grass_main
, combined withgeneric_unhookable
andfont_teeworlds
) - Make it loopable, you can get creative with that :)
- Insert a scale if suited
- Use simple textures (preferably
Step 2.1: Recording the demo
- Turn demo recording on
- I suggest
Settings -> General -> Automatically record demos
- I suggest
- Load the map on a server
- Start your own DDNet server or use the Trashmap hosting service
- Join it with your client, try the trick until you are satisfied with the result and keep loopability in mind
Recording Settings
Set consistent skin:
- Hammer: brownbear
- Pistol: coala
- Shotgun: cammo
- Grenade: redstripe
- Laser: bluestripe
- Hook: default
- Jump: bluekitty
Step 2.2: Cutting the demo
- In your client, go to
Demos -> auto/
- Open the demo you recorded
- Tip: Click on
Date
to sort by date
- Tip: Click on
- Press
Escape
for demo functions - Use the 2 buttons on the left of the camera icons to select a starting and end point
- Use the camera icon to save the shortened demo
Tip: you can repeat these steps multiple times to be able to cut the demo more precisely
Converting the demo
Once you have the client, converting a demo is as simple as:
- Open the client (with the converting functionality)
- Set zoom to 10:
cl_default_zoom 10
- Go to the
Demos
tab - Select the correct demo
- Click
Render
at the bottom
Step 4: Cropping the video
Now that we have our video, we will now want to crop it down, so that only the relevant area of it is shown. For this exact process we have created the crop.sh
script. You can find it in /scripts/crop.sh
.
To use it:
- First edit the
crop.sh
script to set thePIXEL_PER_TILE
value correctly! - Use it as a commandline tool:
- The first argument is the input video file
- The second argument is the output video file
- The third to sixth arguments are each, how many tiles upwards/downwards/to the left/to the right should be seen in the video
- Try different settings to get the best result
- Remember to include the exact command you used in the commit message, as well as your
PIXEL_PER_TILE
value!
Step 5: Creating a merge request for the repository
You don’t have to be familiar with git to create a merge request:
- Go to the folder view
- Click on the drop-down menu next to the
videos
folder - Click
Upload file
- Upload all relevant files this way, for each video include the .demo
- Click on the blue button
Commit...
- Write into the ‘Commit Message’ what you are changing (e.g. which video you are adding)
- Insert the crop command(s) you used from step 4!
- Create a new branch; it should be selected by default, if not, tick it
- Press the green button ‘Commit’
Step 6: Insert videos in pages
See About for how to edit pages. Adding {{% vid vid-name %}} to markdown pages includes /video/vid-name.mp4
in the HTML page.
Templates
If you identify a common occurrence, such as weapon info boxes, you can automate it creating templates, more info here.
List of created templates: