Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Prog Wars: Command Line

Name: Anonymous 2009-06-20 15:31


//RTS CONCEPT: C vs Java vs LISP vs Scheme vs Python

What units should each army have? What should their building structures be? If enough good ideas are posted, my  game development club might take on this endeavor.

Name: Anonymous 2009-06-20 15:35

scheme: all buildings are escherian
java: all buildings are thrice-redundant
python: all buildings are identical in form

Name: Anonymous 2009-06-20 15:36

>>1
Doomed to failure as it is inevitable that the language it is coded in will be overpowered.

Name: Anonymous 2009-06-20 15:39

LISP needs parenthesis as their base unit (duh).
Java should have some bytecode as theirs.
C, maybe some brackets or something?
I dont know enough about the other three to give a comment.

Name: Anonymous 2009-06-20 15:40

C will be played 95% of the time.
Java has the slowest build times.
Scheme will conjure their buildings with spells.
Python will be the beginners army of choice and force buildings to be aligned in a certain manner.

Name: Anonymous 2009-06-20 15:40

>>3
Program it in RUBY lol!

Name: Anonymous 2009-06-20 15:46

>>1
If you ever finish this please send a link back here.

Name: Anonymous 2009-06-20 15:47

LISP will have a suave space toad for commander.

Name: Anonymous 2009-06-20 15:48

>>1
Not particularly fair, as Scheme and Lisp would have the ability to define new unit types on the fly.

Name: Anonymous 2009-06-20 15:50

>>9
I loled.

Name: Anonymous 2009-06-20 15:52

>>9
Not particularly fair, as Scheme and Lisp would have the ability to define new unit types on the fly.
But!  They'd only be 30% as good as a C unit.

Name: Anonymous 2009-06-20 16:23

>>9
Unfortunately, for LISP, the spaces units can occupy must be separate from the actions they perform, making them unable to do anything.

Name: Anonymous 2009-06-20 16:31

>>11
True, but how then would you balance java and python? My guess:

Java - Super fast unit build time(maybe builds multiple similar units at the same time?) but their attack speed is slow.

Python -  Strong (and forced) starting game, but weak end game.

Python and Java would be the 'rush' armies.

Name: Anonymous 2009-06-20 16:33

>>13
Java - Super fast unit build time(maybe builds multiple similar units at the same time?) but their attack speed is slow.
are you kidding me

Name: Anonymous 2009-06-20 16:34

Each army would be scriptable in their own language.

Name: Anonymous 2009-06-20 16:45

>>14
No, the build time would be fast because of 'lol enterprize' and code reusability. The units attack speed and possibly movement speed would be decreased because of obvious reasons.

Name: Anonymous 2009-06-20 16:47

>>16
Yep, also due to huge libraries.

Name: Anonymous 2009-06-20 16:51

>>1
I like that name. The sequel should be 'Enterprise strikes back'

Name: Anonymous 2009-06-20 16:57

>>16
Nah, they should have a head start on research and available units, with big, heavy units that move quickly but take forever to build.

Name: Anonymous 2009-06-20 16:59

>>17
Java would have only three humongous buildings available:
- JDK as the main HQ
- Eclipse or Netbeans as the humongous factories which takes ages to build. Each will give you slightly different units but can't coexist in the same base.
Plot twist: Every faction relies strongly on C which rules all.

Name: Anonymous 2009-06-20 16:59

C - Super-strong, super-fast, fastest build-time, adaptable to any terrain.

Any other language - Super-weak, super-slow, slow build-time, can only walk through swamps, some random gimmick.

Name: Anonymous 2009-06-20 17:01

C++: slowest build time, fastest units, ugly units, most complicated tech tree.  Units take smallest amounts of supply, but if you run over supply it will cause random problems with your units.

Java: Units start slow but get faster the more they are used, also pause and stop attacking at random intervals.  Units require a lot of supply. Simple tech tree.

LISP: Plays differently from other languages.  Units can be combined to form strong units, or to modify other units. 

Python: fast construction time but units are weak and slow. Requires a lot of supply.  Has restriction on how you must build your base(like zerg crepe).

Name: Anonymous 2009-06-20 17:04

>>20
Plot twist
You're right.  C should not be a playable ... race.

Name: Anonymous 2009-06-20 17:10

>>21
C - Super-strong, super-fast, fastest build-time, adaptable to any terrain.
C should allow a fast build time, but at the expense of having all your units and buildings randomly backfire and explode. C units should also be the most vulnerable to takeover by the enemy.

Name: Anonymous 2009-06-20 17:53

Yea, maybe instead of C, it should be C#.

Name: Anonymous 2009-06-20 17:56

>>25
So you'd have two factions with the exact same units, except one would be slightly shinier than the other?

Name: Anonymous 2009-06-20 18:01

>>26
Not both C and C#, just the latter.

Name: Anonymous 2009-06-20 18:03

Java air unit: Signed Applets

Name: !hMAFaNGAR. 2009-06-20 18:06

Hax my anus!

Name: Anonymous 2009-06-20 18:11


   //Step 1: Take off C from playable factions.
   //Step 2: Add Ruby.
   //Step 3: Program game in C.
   //Step 4: 10 points for Gryffindor!
   Step 5:   PROFIT!!!

Name: Anonymous 2009-06-20 18:30

OP, this is a terrible idea.

Name: Anonymous 2009-06-20 18:34

the forced indentation of buildings

thread over

Name: Anonymous 2009-06-20 18:40

>>27
Ignorant idiot.

Name: Anonymous 2009-06-20 18:42

>>27
I think he meant Java.

Name: Anonymous 2009-06-20 19:29

>>32
lol

Name: Anonymous 2009-06-20 19:40

This thread is amazing!
also: C vulnerability -- null pointer exceptions. I guess this would work like taking down their shields like you could with protoss in starcraft.

Name: Anonymous 2009-06-20 19:52

This game might be better as sort of a 2D zelda style multiplayer battle game. You choose your language(class) and you fight other players using that languages abilities.

Name: Anonymous 2009-06-20 20:16

>>37
That could be cool, but I think a cool idea would be to make this into a RPG. You could start off as a stripped down language (brainfuck or some simple assembler) and as you move through the levels fighting these other languages you can pick up some of their features i.e. you kill C and get some real program control (you'd start off with a conditional goto), all the way up until you fight the master boss. Which, predictably, is a lisp-interpreter written in lisp.

Name: Anonymous 2009-06-20 20:32

>>38
[code]
//The sheer amount of win in this post is unfathomable.
[code]

Name: Anonymous 2009-06-20 20:33

>>39
And yet I failed to add the '/' to [/code].

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List