Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!


1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


#Actualrip-off

Posted 31 October 2013 - 05:35 PM

Here are the slightly revised "rules" - note that they are self enforced. Please abide by the spirit of the experiment.
  • There are two experiments, one in C++ and one in HTML 5
  • Each experiment will have a thread, to be created by me, which will be populated with a minimal, terrible program
  • Each experiment will have a separate but related theme. Strive to make a playable, or even fun, game!
  • The threads will act as a kind of revision control system, each post containing code is a commit
  • You must attempt to amend the current version of the code
  • If, having posted, you find someone has committed something new, please immediately edit your post to remove the code (to avoid confusion)
  • Posts must include the full source of the program so far, but please highlight what was changed
  • The program will be in a single file only
  • Dependencies are limited to the standard library and the multimedia library only
  • Assets can be procedurally generated, or inlined into the source file, do not refer to external assets
    • For C++, the GIMP has the ability to export images into C source
    • For HTML 5, you can use a data URI
  • Remember, any assets and source code must be free of copyright restrictions
  • You can only add new code, do not remove existing code
    You may alter existing code, but please be conservative. Here are some examples:
    • Changing numeric or string constants
    • Adding a new clause to a condition
    • Adding to an existing expression
    • Adding parameters to existing function declaration/definition/call sites
    • Adding a comment at the start of a line is allowed by this rule, but please minimise such use
    • You may also "insert" a newline after a single line comment (thus uncommenting such code)
  • The code must compile on your platform of choice, and should strive to be cross platform
    • A simple example in C++ is assuming that certain types have or share a particular size
    • Do not make OS or Browser specific calls
  • Your code must not crash (to the best of your ability)
  • Bad commits are ignorable under the "amend the current version" rule. Please clearly state if this step is taken
  • For the sake of the experiment, please:
    • Try keep each commit relatively small and cohesive - for example add or change a single feature at most
    • Avoid committing twice in a row (if the thread is quiet, feel free to ignore this one)
  • Have fun everyone!

#1rip-off

Posted 31 October 2013 - 05:16 PM

Here are the slightly revised "rules" - note that they are self enforced. Please abide by the spirit of the experiment.
  • There are two experiments, one in C++ and one in HTML 5
  • Each experiment will have a thread, to be created by me, which will be populated with a minimal, terrible program
  • Each experiment will have a separate but related theme. Strive to make a playable, or even fun, game!
  • The threads will act as a kind of revision control system, each post containing code is a commit
  • You must attempt to amend the current version of the code
  • If, having posted, you find someone has committed something new, please immediately edit your post to remove the code (to avoid confusion)
  • Posts must include the full source of the program so far, but please highlight what was changed
  • The program will be in a single file only
  • Dependencies are limited to the standard library and the multimedia library only
  • Assets can be procedurally generated, or inlined into the source file, do not refer to external assets
    • For C++, the GIMP has the ability to export images into C source
    • For HTML 5, you can use a data URI
  • Remember, any assets and source code must be free of copyright restrictions
  • You can only add new code, do not remove existing code
    You may alter existing code, but please be conservative. Here are some examples:
    • Changing numeric or string constants
    • Adding a new clause to a condition
    • Adding to an existing expression
    • Adding parameters to existing function declaration/definition/call sites
    • Adding a comment at the start of a line is allowed by this rule, but please minimise such use
    • You may also "insert" a newline after a single line comment (thus uncommenting such code)
  • The code must compile on your platform of choice, and should strive to be cross platform
    • A simple example in C++ is assuming that certain types have or share a particular size
    • Do not make OS or Browser specific calls
  • Your code must not crash (to the best of your ability)
  • Bad commits are ignorable under the "amend the current version" rule. Please clearly state if this step is taken
  • For the sake of the experiment, please:
    • Try keep each commit relatively small and cohesive - for example add or change a single feature at most
    • Avoid committing twice in a row (if the thread is quiet, feel free to ignore this one)
Have fun everyone!

PARTNERS