Some Templates for your forum posts

  • Fusionftw
    2nd Apr 2020 Member 3 Permalink

    Element Suggestion:

    Element Abbreviation - Full Element Name

     

    Characteristics: (Things about your element, like color, weight, etc.)

    • Color: rgb(R,G,B)

    • Description: “This is the description for my element, which appears when I hover over it in the element picker.”

    • Category: (The section where you element goes, e.g. Solids)

    • (Other characteristics go here, e.g. My element absorbs photons.)

     

    Properties: (An in-depth description about your element’s abilities; these are what make your element special)

    • (For example: If my element is sparked, it changes color based on how many times it was sparked.)

     

    Uses: (Try to think of as many good uses your element has, don’t list uses like, “My element can be used to build”.)

    • (For example: You can use my element to quickly create computers without needing bulky logic gates.)

     

    Counterclaims: (OPTIONAL. This is meant as a way to discuss possible issues before someone points it out. Note that providing a simple way to code your element will help your suggestion greatly.)

    • (For example: You may ask, “How will the changing color when sparked function be coded?”. It could be coded by creating a variable, and whenever the element detects a spark (code could be taken from ARAY), it increments that variable. The RGB values are just the spark variable, but with 64 added to them.)

     

    Note that these element suggestions, if not even useful, are more likely to get rejected. Do not take your rejection with anger, as you are more likely to get a thread lock and a forum ban.

     

    Element suggestions are even more likely to get rejected. You are not the first to get your element rejected, nor the last.

     

    Game/Forum Suggestion:

    Name of Suggestion

     

    (General description of your suggestion. Make sure that your suggestion is covered in detail, not “Please add more categories”. Also, try to sell your suggestion, as just saying “Please allow double posting. It will be good. I promise.” is more likely to get your suggestion ignored.)

     

    Counterclaims:

    • (This is where you discuss some negative points about your suggestion. For example, “You might say that adding double posting clogs up threads. However, editing your post may leave readers in the dust as to what the original text was.”.)

     

    Note that these suggestions, if not even semi-relevant, are more likely to get rejected. Do not take your rejection with anger, as you are more likely to get a thread lock and a forum ban.

     

    Bug Report:

    Title, or a Brief Description of Bug (e.g. Ambient Heat Bug)

     

    Description of Bug:

    (This is where you explain your bug in detail. You want your description to be clear, concise, and not short. “If I turn on ambient heat, the game does stuff.” is not a good description.)

     

    Steps to Reproduce:

    (This is a list of steps intended to show others how to reproduce the bug. Be specific, but not exhaustive. For example: “1. Open TPT; 2. Click the A; 3. See the Bug” is too vague, and “1. Eat Breakfast; 2. Brush Teeth. 3. Turn on Computer; 4. Log In; 5. Doubleclick the TPT Icon; 6. Click the A at Screen Position 1800,600 for 1920x1080 Monitors…”)

     

    Version:

    (Some bugs are very specific, and are related to the version of your TPT program. You can find this by pressing Ctrl+H on a save. Version (e.g. 95.0.345), and OS (e.g. Windows 10 Pro 1909) are what you should include. Saying “I have a recent TPT version”, or “My computer’s serial number is XXXXXXXXXXXX” is not good.)