Talk:Code Break

These codes.... are they akin to Javascript? TRS NX  17:27, 25 June 2015 (UTC)
 * Looks like it's supposed to be an allusion to Java or Python, yeah. 18:50, 25 June 2015 (UTC)

Images
The images really aren't very good here. The code is hard to read, and they're not demonstrating the actual technique being performed. I don't think we should be using screenshots unless they are depicting the performance itself. 19:00, 31 January 2016 (UTC)
 * I find the code themselves interesting to read so I'd replace them with full gifs of the entire techniques, but keep the screenshots in a gallery as a curio. 20:57, 31 January 2016 (UTC)
 * I definitely think we should have the code, but it's probably better if it's actually written out so that it's readable. Most of the images we have have bright objects behind the code that makes it extremely difficult to read. 04:37, 1 February 2016 (UTC)
 * If it's possible, we could remove the background from the text, keeping us with the same text font and colours used in the game. 17:33, 1 February 2016 (UTC)
 * The only ones I see with a background problem are ENERGY JAMMER and MOVING SPARK. Rex Ronald Rilander (talk) 22:08, 1 February 2016 (UTC)
 * And Auto Destruct, Prize Shot, and Unlock. The point of having images is to demonstrate the technique. The code can be written as code, unless we're actually showing a gif of it being activated. These images don't make sense. 15:52, 2 February 2016 (UTC)
 * I'm really not seeing a problem with those three. Could you perhaps elaborate on what the problem is with them? Rex Ronald Rilander (talk) 18:24, 2 February 2016 (UTC)
 * Big ol' bright lines going straight through the text. Regardless, the point of technique images is to show the process, not a detail. We can cover the code itself the way we originally did, as wikicode. 20:06, 2 February 2016 (UTC)
 * Oh yeah, I guess that would be a problem for most people. Not for me though.  Rex Ronald Rilander (talk) 20:24, 2 February 2016 (UTC)