Talk:Robocode/Getting Started

Robocode Basics redirect

Are we sure that Robocode Basics should redirect here and not to Robocode? The Robocode page seems more like an introductory page than this. --AaronR 20:50, 4 December 2007 (UTC)

Hmm.. good question. What do we really mean when we say "Robocode Basics". I think of the basics I should know to get started, not what Robocode is. Perhaps we should drop the "Robocode Basics" page, and do no redirect. We could also make a real Robocode Basics, which kind of explain what exacly the Robocode basics a newcomer should familiarize himself/herself with in order to know all the basics? If you are really against the redirect, then just change it. ;-) --Fnl 22:47, 4 December 2007 (UTC)

Well, at present, this page assumes that you know what Robocode is and that you have already downloaded and installed it. The first thing a beginner is likely to do would be to click on the Robocode Basics link on the home page. Perhaps the name of this page is a misnomer; it seems like "Robocode/Running a Battle" or something along those lines would be more appropriate. --AaronR 01:36, 5 December 2007 (UTC)

Yes, "Robocode/Getting Started" is the "Robocode/Running a Battle", so perhaps we should "just" change the name of this page? (and all places where I have written "Getting started" in links) --Fnl 22:07, 5 December 2007 (UTC)

Learning Robocode

Hmm. Seems to me, learning Robocode is a hard task. I don't know why exactly, but I don't seem to make much progress. How long does it take to master? Does anyone else face these - er - barriers? —Preceding unsigned comment added by Urgood2 (talk • contribs)

Well, I think 'mastery' is an interesting question. I think it was roughly 4 months between when I started robocoding and when I had something I felt ready to release in public, but I wouldn't say I had 'mastered' it by that point. On the other hand, people do often release things earlier than that. I don't think there's any specific level one could call 'mastery'. I would say the two biggest factors that affect how easy/hard it is to learn are one's existing familiarity with programming, and with geometry. May I ask what kind of barriers you mean? If you haven't already my suggestion would be to try making something that can beat the sample bots. If you have any questions, feel free to ask. --Rednaxela 15:30, 23 April 2010 (UTC)

Ok, I'll try that! Thanks ---- Josh S 05:09, 24 April 2010 (UTC)

To master Robocode, I believe, isn't just good at programming and geometry, you need to be good at statistic and have a LOT of patient to fine-turning some precise and sensitive factor in your robot. How much progress you have? --Nat Pavasant 15:36, 23 April 2010 (UTC)

Not much really, though I experiment quite often. Concepts like wall avoidance and linear targeting seem strange to me still. My hopes are though, I'll become better at using them one day :) ---- Josh S 05:09, 24 April 2010 (UTC)

Of course, I imagine everyone faces similar barriers. Familiarity with programming, geometry, trigonometry, Object-Oriented Programming, and programming to APIs will all help. However, I'm sure many Robocoders lack some of these skills, and Robocode is a good place to learn them. Trying to beat the sample bots is indeed a good challenge to start with. If you stick with it, check out Tutorials, and aren't afraid to ask questions on the wiki, I'm sure you'll do fine. =) I'm also a fan of Special:Randompage. --Voidious 15:45, 23 April 2010 (UTC)

I hope so =) ---- Josh S 05:09, 24 April 2010 (UTC)