Skip to main content
Puzzling

Return to Answer

included interactive puzzles in ask section
Source Link
Adam
Adam
  • 2.9k
  • 6
  • 8

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.
added some extra links which provide some context
Source Link
Adam
Adam
  • 2.9k
  • 6
  • 8

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

  • Our questions are mostly puzzles of our own invention.
  • Puzzles should have a unique answer identifiable as such.
  • Questions that look like maths homework will be closed.
  • Asking questions related to puzzles and puzzle design is also ok.
  • Respect copyrights. Only use material you have a permission to use.
  • If you post a puzzle you didn't create yourself, always attribute the original author.
  • The common practise is to accept the first correct answer, but you are free to accept any answer by whichever criteria you like.
  • Avoid major changes to questions after they have been answered.
  • It's ok to add hints to questions, but waiting 24 hours before doing so is appreciated.
  • Some tag wikis provide good advice on what (not) to do when asking. Typical examples include "What is a XYZ™ item", "Number Sequences" and "Code Puzzles". TODO: Add more examples

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.
added 547 characters in body
Source Link
Omega Krypton
Omega Krypton
  • 21.7k
  • 6
  • 9

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

  • Our questions are mostly puzzles of our own invention.
  • Puzzles should have a unique answer identifiable as such.
  • Questions that look like maths homework will be closed.
  • Asking questions related to puzzles and puzzle design is also ok.
  • Respect copyrights. Only use material you have a permission to use.
  • If you post a puzzle you didn't create yourself, always attribute the original author.
  • The common practise is to accept the first correct answer, but you are free to accept any answer by whichever criteria you like.
  • Avoid major changes to questions after they have been answered.
  • It's ok to add hints to questions, but waiting 24 hours before doing so is appreciated.
  • Some tag wikis provide good advice on what (not) to do when asking. (TODO: add links to some Typical examples) include "What is a XYZ™ item", "Number Sequences" and "Code Puzzles". TODO: Add more examples

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

  • Our questions are mostly puzzles of our own invention.
  • Puzzles should have a unique answer identifiable as such.
  • Questions that look like maths homework will be closed.
  • Asking questions related to puzzles and puzzle design is also ok.
  • Respect copyrights. Only use material you have a permission to use.
  • If you post a puzzle you didn't create yourself, always attribute the original author.
  • The common practise is to accept the first correct answer, but you are free to accept any answer by whichever criteria you like.
  • Avoid major changes to questions after they have been answered.
  • It's ok to add hints to questions, but waiting 24 hours before doing so is appreciated.
  • Some tag wikis provide good advice on what (not) to do when asking. (TODO: add links to some examples)

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.

Since the question is getting a lot of support, but there are no answers yet, I'm starting this CW on Rand's idea: FAQify the posts in here and summarise the rules.

Since I lack the power to add the tags, I'm just writing some summaries here, grouped by the newcomers action for which they are relevant. Most links are still missing, as are probably some other conventions that it would be useful for a newcomer to know.

This community wiki answer is a work in progress, and not yet complete.

Asking:

  • Our questions are mostly puzzles of our own invention.
  • Puzzles should have a unique answer identifiable as such.
  • Questions that look like maths homework will be closed.
  • Asking questions related to puzzles and puzzle design is also ok.
  • Respect copyrights. Only use material you have a permission to use.
  • If you post a puzzle you didn't create yourself, always attribute the original author.
  • The common practise is to accept the first correct answer, but you are free to accept any answer by whichever criteria you like.
  • Avoid major changes to questions after they have been answered.
  • It's ok to add hints to questions, but waiting 24 hours before doing so is appreciated.
  • Some tag wikis provide good advice on what (not) to do when asking. Typical examples include "What is a XYZ™ item", "Number Sequences" and "Code Puzzles". TODO: Add more examples

Answering:

  • An answer to a puzzle should always explain why it's the correct answer.
  • Partial answers are ok, but not always so.
  • Use spoiler tags >! at the start of lines to hide the crucial parts of the answer from accidental views.

Commenting:

  • If you have a minor improvement to an existing answer, add a comment rather than a new answer.
  • Rot13 encryption is sometimes used to hide possible spoilers in comments. @Alconja's nice script can encrypt/ decrypt rot13 upon mouseover.

Voting:

  • Use upvotes and downvotes as you please. When downvoting, adding a constructive comment is much appreciated.

Other:

  • A collection of helpful tools to assist you can be found here.
  • If you need help, the easiest way is to ask at The Sphinx's Lair.
Added a reference to the tools meta page
Source Link
Adam
Adam
  • 2.9k
  • 6
  • 8
Source Link
Bass
Bass
  • 77.9k
  • 8
  • 17
Post Made Community Wiki by Bass