We have reduced support for legacy browsers.

What does this mean for me? You will always be able to play your favorite games on Kongregate. However, certain site features may suddenly stop working and leave you with a severely degraded experience.

What should I do? We strongly urge all our users to upgrade to modern browsers for a better experience and improved security.

Proper Forum Code Formatting Guide

Reading posts without code properly formatted causes more problems then it solves because we are forced to attempt to interpret what the intended code was, and it’s not always right.
# Code blocks
To get this:
> Some text. next line must be blank
>
> `[code here]`
>
> some more text. next line must be blank
>
> `[code]
> [code]
> [code]`
>
> still more text
You need to do this:
> Some text. **next line must be blank**
> &nbsp;
> \<pre\>[code here]\</pre\>
> &nbsp;
> some more text. **next line must be blank**
> &nbsp;
> \<pre\>[code]
> [code]
> [code]\</pre\>
> &nbsp;
> still more text
**Not having blank lines before \<pre\>
and after \</pre\> _will cause issues_.**
# Inline Code
For small single lines of code, or to make something stand out a bit use `code` tags or the @ symbol, as such:
> Yet more text \<code\>[code]\</code\> and more text @[code]@
To get:
> Yet more text `[code]` and more text `[code]`
# Preventing Formatting
To get special characters like @ without them being formatted enclose them in `==` or `notextile` blocks, \< or \> when they’re around certain words (like pre, a, p, etc.) and &:
> Yet more text ==\*asterisks\*== and more text \<notextile\>@[code]@\</notextile\> &lt;a&gt; &amp;
To get:
> Yet more text \*asterisks\* and more text @[code]@ \<a\> &

> *Originally posted by **[jonathanasdf](/forums/4/topics/39889?page=1#posts-841935):***
>
> easier to use &lt; and &gt;
>
> lt = less than, gt = greater than.
>
> although it won’t matter if it’s in pre tags.
>
> And STICKY THIS PL0xXx
>
> Edit: actually it won’t matter for forums, only matters for chat. forums nonsense tags or blocked tags won’t be formatted.
>
> see?
>
> \<asdf\>\</asdf\>
>
> \<font\>\</font\>
Well, it is very useful to use &# 95; for “\_” and &# 42; for “\*” because of Kong’s stupid formatting settings. (You can use the text version also instead of this ASCII numberic version to display such characters.)

> *Originally posted by **[jonathanasdf](/forums/4/topics/39889?page=1#posts-842041):***
>
> you can still just put them in the pre tag and they won’t be formatted…. which I find easier to use.
…No, you can’t. The website’s settings \> the “pre” tag’s settings for those characters.

> *Originally posted by skyboy, up at the top of this here thread*
>
> not having empty lines before \<pre\> and after \</pre\> will cause issues.
specifically, it will put in a lot of goddamn whitespace into your code, which I couldn’t figure out until just now. much obliged, skyboy.
This is what you want:
`
while(true)
{
trace("My milkshake brings all the boys to the yard");
trace("And there like, its better than yours.");
trace("damn right, its better than yours.");
trace("I could teach you, but I'd have to charge.");
}
`
and this is what you get if the `<pre>` tag don’t have their hard returns.
`
while(true)
{
trace(“My milkshake brings all the boys to the yard”);
trace(“And there like, its better than yours.”);
trace(“damn right, its better than yours.”);
trace(“I could teach you, but I’d have to charge.”);
}
`

> *Originally posted by **[Dynamite\_Studios](/forums/4/topics/39889?page=2#posts-1999467):***
>
> BUMP SO PEOPLE READ THIS!
Well with Skyboy posting the link to this thread every time someone doesnt/forget-how-to do this, im pretty sure alot of people are gonna read this :P