Slashdot Mirror

← Back to Stories (view on slashdot.org)

Loki Announces Loki Hack 1999 Contest

Posted by CmdrTaco on from the this-is-interesting dept.

Ethelred Unraed writes "Loki Entertainment Software has announced a contest where an elite group of hackers (in C++, that is) will be chosen to improve their port of Civilization: Call to Power. The winner will get a dual-processor Linux box as a prize. Take a look at their info page for more. " Thats a pretty crazy contest idea. They ought to give the winner a job.

7 of 126 comments (clear)

  1. Loki Hack by Anonymous Coward · · Score: 5

    I'd like to dispel any confusion about what we're trying to accomplish with Loki Hack. Seems like some people have assumed that we're looking for free work on the port, bug fixes, or the like. Wrong.

    The idea is this. When's the last time you got to see the source code for a commercial game -- and not several years after the fact. When's the last time you got to modify a game, change the rules the way you like, add something you think is missing? Then get your changes posted for the rest of the world to play around with. And all of this supported by the developer? And we throw in some prizes too.

    This is the closest we can get to open source with our products. The world won't see the source, but the contestants will. And all the hacks, mods, changes will be posted in binary form, freely downloadable for the world to see. Know anyone who has seen the Windows code for this game?

    Of course, we're going to help people along. Loki developers will be present to answer questions during the hack. We'll also have an intro session to get people familiar with the code.

    For those unaware, it's a very big deal for a commercial game company to let you look at their source for a current product. Activision is going out on a limb with this. We want to show them what the open source community can accomplish.

    Scott Draeker
    President
    Loki Entertainment Software

  2. Don't Do It by copito · · Score: 5

    CTP is a slow game with serious bugs that is barely playable on a Celeron 300 w/ 64 MB. All this for a 2D game that would have been revolutionary in the late 80's. Yes I paid my $40 bucks. Yes I wanted to support a cool company and Linux. And yes, I'm bitter.

    Loki isn't all bad. Their developers field actual bug reports and there has been one patch set to cure some of the more serious problems. They are a new place and they might port or create a good game someday. Apparently a lot of the problems with CTP exist in the Windows version, so they might have been just dealt a bad hand.

    That being said, the new contest they have created is a joke. Imagine if someone said to you, "you're a damn good programmer. I want you to spend some time doing some programming for us. No
    we won't pay you, but you might get a decent computer out of it and we get to keep your code and sell it."

    Considering this, what are your incentives:

    You really need that 'puter:
    A good C++ programmer can make enough money to buy the computer in what, a couple of days?

    Pure altruism:
    Perhaps, but you would be probably increase your cosmic oneness more by contributing to an open source project.

    Ego:
    Your kung fu is the best. You want everybody to know it. Well good luck, but here's a hint. If you're that good you should either be getting pay or serious recognition out of the deal, or possibly both.

    A job at Loki:
    Ok, you want to work at Loki, this might be a good way to strut your stuff, but they are getting far more out of the deal than you. Companies typically pay thousands to track down and hire a qualified candidate for a job, without immediate benefit to themselves.

    You really like CTP and want to see how it works:
    I don't agree, but curiousity is a valid reason for anything in life.

    You really like CTP but the bugs annoy the crap out of you:
    There are probably lots of people that fit in this category. Probably enough to give Loki their computer's worth. Go a head, give the Man a hand. He'll make it worth your while.

    --

    --
    "L'IT c'est moi!"
    1. Re:Don't Do It by slashdot-terminal · · Score: 4

      To address some of these complaints:
      1. The game is slow
      1.1. The code might be inefficient
      1.1.1. The contest may address this by weeding out the bad portions of the code and allowing the better parts to come out and the best to survive
      1.1.2. The code is not optimized correctly for the processor.
      1.1.2.1. Most code for linux systems is set for 486 target architectures
      1.1.2.1.1. The exception to this are things like pgcc/some of the egcs flags, Mandrake, etc however I would still advocate software to be compatable with the 486 style I don't want to be forced into an upgrade because "The world moves on..."
      1.2. The current config for the hardware is in conflict
      1.2.1. Many programs have the potential to conflict with particular configs.
      1.2.1.1. some corel apps have conflicted with recent or experimental designs
      1.2.2. Overclocking of the processor
      1.2.2.1. Processor intensive operations are very able to vause exceptions that may be getting caught in some kind of exception manager that is taking up something like 30% of the Celeron hence causing slowdown.
      2. Needing a computer
      2.1. Avaibility
      2.1.1. It seems that most individuals cannot buy an SMP enabled machine from their local computer store (compusa, radioshack, bobslocalcomputeremporium)
      2.2. To code?
      2.2.1. Not unless you code something like your own version of a CTP similar app with 500Mb or source and tons of time intersive operations
      2.2.2. Need to program a device driver that uses hardware exclusively found on a new computer
      2.2.2.1. Usually open docs take care of this
      2.3. To play CTP or other like games on
      2.3.1. Kind of defeats the purpose and wastes the cause of efficiency.
      3. Altruism
      3.1. The company is hard up
      3.1.1. Perhaps because they produce crappy games they need help right where they need it (in their wallet)
      3.2. Their programmers are all stupid
      3.2.1. They are testing the waters to find new people or to shame their current ones
      3.2.1.1. In that case it would be most beneficial to do a good job and a nice career can be yours
      3.2.2. Programs that need to have the likes of Einstein to work on them are just plain wrong and perhaps hurt human intellecutal ability to accomplish
      3.3. You like giving to the first person who asks
      3.3.1. A typical tactic to anyone who has ever done anything that involves free or reduced services of any form
      3.3.1.1. It is really bad form to refuse a person who initially had your help when someone new comes along
      3.3.1.2. You establish report with people that you serve with and make the person you helped grateful
      4. A Job at the host company
      4.1. Sucking up
      4.1.1. Nice especially if you want to seem selfless (ok not totally they are giving out a computer to the winner)
      4.1.2. People remember the person who gives them nice comments without seeming to be giving insincere flattery. This would be a nice time to show them that you are selfless enough and dedicated to their vision to do what they want and need
      4.2. Show level of competence
      4.2.1. Competent people have an increasing need of physical evidence to prove who they are and what they do a nice directed project.
      4.2.2. It's the type of competence that is directed to the job
      5. Curiousity
      5.1. Efficiency (see above)
      5.1.1. Answer the burning question (why is this so slow?). Is there a better way to do this?
      5.2. Obtaining a good strategy to win
      5.2.1. Cheat codes are usually embedded in games and are not all totally obvious at first glance
      5.2.1.1. These codes override the things that make you loose and conversely make you win.
      5.2.2. If there is a function create_big_scary_monster_with_sharp_teeth(player)
      {
      some code here...
      ...
      }
      perhaps you can defeate his logic and then win that way. This is usually how we win games of this sort look for patterns and then reduce those complex patterns.
      6. You hate bugs
      6.1. Don't play the game
      6.1.1. I have programs that have been on my computer that have for various reasons failed me
      6.1.1.1. I usually take this as a personal problem and then just use something else.

      --
      Slashdot social engineering at it's finest
  3. An even better contest! by chandoni · · Score: 5
    Freeciv Hack 2000

    Make your contribution to Civilization! No, not all civilization, but rather you have the chance to take part in our Freeciv Hack 2000 contest to improve Freeciv. Recent improvements include more races and nations, city build lists, and the addition of more CivII rules (paratroopers, more terrain specials). Other improvements such as GUILE scripting, improved AI, hex maps, and stacked combat are being developed. (Read our mailing list archives for more info.)

    What is Freeciv Hack 2000? It's a special contest in cooperation with an international term of developers, where you can show off your Linux (and BSD, commercial Unix, BeOS, Java, even Windows) hacking skills to everybody...and win prizes to boot! First prize is the ego gratification of getting your name in the PEOPLE file.

    Here's how it works: download the source from ftp.freeciv.org and get to hacking. Everybody with a C compiler will be chosen. If you're chosen, you can show up to our hackfest, which will conveniently be held on your own computer!

    Any and all changes and improvements worthy of improving Freeciv (and, by extension, civilization as a whole) will be included in the CVS snapshots and new public releases starting with 1.8.2. So what are you waiting on? Download the source and get hacking!

    JMC

  4. Gift Horse for Sale, needs dental work... by redwolf · · Score: 4

    "Flame On!"
    I can't believe people are complaining that Loki's prize
    isn't big enough or doesn't cost enough to 'make it worth my time.'

    Here's my advice: If the prize offered isn't big enough... DON'T ENTER!
    But please, stop the complaining.

    "Flame Off!"
    Thanks to Johny Storm and the Fantastic 4.

  5. Slashdotted server? by Alphix · · Score: 4

    Im not sure why or if it's just slow.....anyway...here's the text on the page if thats all you want (and the server keeps crawling).

    Loki Hack 1999

    Make your contribution to Civilization! No, not all civilization, but rather you have the chance to take part in our Loki Hack 1999 contest to improve our Linux port of Civilization: Call to Power. (Then again, by making Civilization better, you can make civilization better, too. You get the idea.)

    What is Loki Hack 1999? It's a special contest in cooperation with Activision, Inc., the Atlanta Linux Enthusiasts, and the Atlanta Linux Showcase, where you can show off your Linux hacking skills to everybody...and win prizes to boot! First prize is a dual-processor screamer of a machine, running Linux, of course.

    Here's how it works: apply to enter below and tell us about yourself. Thirty participants will be selected based on experience and involvement in Linux development--strong C++ skills are a must--and chosen participants will be notified via e-mail. Then, if you're chosen, you can show up to our invitation-only hackfest, which will run for 48 hours in a secure setting, on October 11-13, 1999 at the Atlanta Linux Showcase at the Cobb Galleria Centre.

    Any and all changes and improvements worthy of improving Civilization: Call to Power (and, by extension, civilization as a whole) will be included in an upcoming special-edition update for the game. The best of the best will receive that beast of a computer. So what are you waiting on? Fill out the form below and get hacking!

  6. 48 hours? by slag187 · · Score: 4

    How many lines of code does CTP have? I really don't know, but this is a significant piece of work here. The contestants will have 48 hours to compete in this thing.

    My point being, it's going to take them most of the time just to read through the code to get a good grasp of how the system works. It will be the first time they see the header files, etc so they'll have to figure out what functions and classes do what and what they need to be passed, etc.

    For this to be impressive, they would have to get the code and then have at least a week . . . then we would have some real bug fixes and imporvements. As is, this is just a publicity stunt.