How to contribute: Difference between revisions

← Older edit Newer edit →

VisualWikitext

Revision as of 07:27, 2 August 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. A variety of topics are yet to be covered
Here you can find articles that need content: Category:Needs Content

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 to automoderated 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 select Load 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
1. Click on the quads layer
2. Right-click the corners of the rectangle
3. Insert the color value #5E84AE 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 grass_main, combined with generic_unhookable and font_teeworlds)
- Make it loopable, you can get creative with that :)
- Insert a scale if suited

Step 2.1: Recording the demo

Turn demo recording on
- I suggest Settings -> General -> Automatically record demos
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
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

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:

Category:Templates

@@ Line 88: / Line 88: @@
 * Select the correct demo
 * Click <code>Render</code> 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 <code>crop.sh</code> script. You can find it in <code>/scripts/crop.sh</code>.
-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'''!
-=== 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 <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 ===
-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 ==