View source for Talk:Main Page

For old discussion, see Archived talk:Main Page 20110903.

I've got the following major issues:

• In LiquidThreads, when I type a reply the spinning loading icon never goes away, and the shortcuts at the top never load.
• When I try to edit the RoboRumble/Participants page it tells me that the server did not receive some of the message and that I should confirm the edits, but it shows me an empty box instead of all the participants data.

These behaviours are seen on both Firefox 21 b6 and Chrome 26.0. I've cleared cache and done a hard reload in both.

Is anybody seeing these?

Yeah, LiquidThreads spinners all over the place for me. I haven't tried editing the participants list but that seems pretty high priority. Hrm..

I'm definitely noticing the first problem. I haven't yet tried editing the participants page.

We seem to be getting a lot of user registrations, did the update break some of the blockers?

Yeah, Rednaxela had some custom things in that got broken. He's working on it now.

Yeah, the update removed the Math extension which used to be part of the core of MediaWiki, but got moved into an extension. This broke some pages, and also broke the extra math question I added in added to the reCaptcha check. (Besides the extra math question, my modifications also included a "same IP address as received the captcha must solve it" check, which based on server logs was very effective)

Due to the error that was happening on the new user creation page, Voidious reverted back to the traditional reCaptcha extension temporarily, which let that flood of bots register.

Gladly, the custom extension I added which disallows accounts less than 24 hours old inserting external links was still intact after the upgrade, and appears to have foiled those spambots.

Also, I've now reinstalled the Math extension, both fixing some wiki pages and making my modified captcha checker work again, so all should be well now :)

Good to know. On that point though, I still think KittenAuth/Asirra would be a good auth system (and has nothing to do with me liking kittens, honest).

Asirra was mentioned in some emails that went around. I don't think Asirra is fundamentally any better than reCaptcha for the main problem. I suspect there's a high probability that rather than pure computer-based bots, the reCaptcha system was being broken by a Mechanical Turk style system that farmed the captcha breaking task out to humans. From what I understand that is common these days. Asirra is equally vulnerable to that technique. Assuming that is the case, the reason my modifications help, would be that rather than preventing the captcha-breaking itself, they make it incompatible with some automation systems used to farm out captcha breaking. I have nothing against using Asirra if people want to switch it to that instead of reCaptcha, but at least in theory I doubt Asirra vs reCaptcha makes much of a difference.

Well fair, I do know Asirra is much more difficult to break then reCaptcha for computers. It might also be easier for humans to do as well ( a few clicks instead of the need to type). It could replace the two captcha systems with one (math+reCaptcha with Asirra).

But I am not going to push the topic if no one else thinks it is a good idea. I do not know the compatibility or reliability of the system, and there is always the ever present "don't fix what isn't broken" mantra as well.

A quick update regarding the RoboRumble/Participants issue: I've confirmed it's definitely related to the total size of the page. I see the error if I click preview there normally, but I don't see the error if I delete half the content of the text box before hitting preview. I don't know why it only started happening after the update though, or what a good fix would be.

Participants issue is fixed, but the spinners persist!

Testing to see if the infinite spinning icon is fixed...

Yep! It's now fixed!

When the infinite spinning icon thing was happening, I checked in the browser for javascript errors. Sure enough, there was an "ext.WikiEditor" error. I looked around, and tried installing the WikiEditor extension, and it fixed the infinite spinning circle issue. It seems that the version of LiquidThreads we got in the update depends on the WikiEditor extension.

Any interest in helping me rewrite the Wikipedia entry for Robocode sometime? We can do it there (like on a user page), but just wanted to bring it up here first. It's all pretty stale, and I think could use a major overhaul besides the first 2-3 paragraphs. I also think the final product should be about half the size of what's there now.

I was under the impression that the point of Wikipedia was to have a stale and objective article for every subject.

The problem with the Robocode page is that it is not objective. It reads like an advertisement, or a fan's website. It also goes into unnecessary detail in some places, while leaving out important information in other places.

Yeah, "stale" like "hasn't been updated in a long time" seems appropriate. Inaccurate information should be fixed or removed though.

I don't think anyone (on Wikipedia) cares about which robot is best at what and such, and keeping those up to date would be a pain anyway, last update was claimed to be in 2009. So I think the RR@H champions should be removed.

The influencial robots section needs to be adjusted some. For example to me Phoenix's entry reads like an advertisement, and is YersiniaPestis' passing Shadow for a bit really worth mentioning? Plus a few are missing like Raiko/RaikoMX (First Open Source Surfer), Chalk (Open Source kNN), BulletCatcher (Bullet Shielding), MoxieBot? (Bullet Shadows? Was it the first?).

But I wouldn't mind seeing a list of past competitions on there, might give the game more clout.

Yep, I agree on all those points.

Taking a few of the bots on the Open Source page might be a good start for replacing the "influential bots" list. Maybe list more current/past competitions, but with less description of each than what's there now. For movement/targeting techniques, maybe instead of mentioning all those Robocode-specific terms, we could just mention some of the machine learning techniques that are widely used, like KNN, kernel density, multi-variate histograms (VCS), pattern matching, and neural networks.

I'm torn as to whether the wiki deserves its own special mention besides the link below. It is a pretty strong part of the online Robocode community and a resource for anyone doing Robocode, but I'm not sure that means it deserves more than just a link near the top of "See also" or "External links".

Agreed on all, unfortunately I am super busy again and don't have time to help with this.

I think there should be some sort of heading called "Community" or something like that, where you list the RoboWiki and the SourceForge forums as well as the dev groups.

I agree, and I like your thinking. Could almost copy Open Source wholesale for that section, after converting some of the jargon.

I think a mention in the actual article to the Robowiki would be justified. It is where most of the developments and long running competitions originate (like RR@H). But it might just be at most a sentence like "A great deal of the innovation occurs around Robowiki[External Link], the games premier wiki."

Perhaps a short mention of some of the licensing that occurs in Robocode. Otherwise there isn't really much to say beyond what is already covered.

Hello! We are creating our first robots, and we export the robots from eclipse, in .jar doing in the project, right click>Export>Java>JAR File.

In the next box, we export to JAR, but when we try to import the robot to robocode, it complete succesful, but it don't appear in the list of robots.

Thanks!

Welcome to the RoboWiki!

You don't need to export every time you want to run your robot. This tutorial shows you how to tell Robocode to get your robots straight from Eclipse.

It's also interesting that you say you imported the robot into Robocode, but it didn't appear on the list of robots. I assume that you used the "Import downloaded robot" feature of Robocode. I might've had the same problem with it. Try downloading this robot and then see if using the Robocode import feature works. If it doesn't, just copy the .jar file into the robot directory, and Robocode should recognize it.

This thread isn't really appropriate for the main page discussion; if you don't mind, I'll move it to User talk:Cristiancompany.

Welcome again and good luck!

Anyone checked out http://fightcodegame.com/ ? The web site seems pretty sleek and it all looks pretty active and well organized. After watching some sample battles, and that the #1 ranked bot is ~350 lines of code, I have to wonder how high a ceiling there is in terms of writing sophisticated robots. The gameplay looks pretty much like a Robocode (or whatever predecessor) clone with only blocking API calls.

It kind of annoys me, on principle, that I have to authorize it with my GitHub account even to see things that are read-only, like the rankings. So I haven't done that yet and thus haven't looked into it in much depth.

Well I have never had much success with normal Robots. Mostly since it seemed like a lot of extra effort for little gain. That is, the rumble was dominated by AdvancedRobots and their non-blocking calls.

I took a look at it, and it is difficult (for me) to write a decent robot on it. Mostly because I would like some kind of debug feature. Supposedly it has a log function to write to a console. But I can't figure out how to access said console.

I played a different Javascript / web-based programming game and also had problems with that aspect. I think it's the browser Javascript console that you need to look at.

(And it was crashing my browser / useless to me for a while before I realized I'd printed like 30k lines to it, which it isn't really designed for, and finally figured out how to clear it.)

After a bit more work I had a semi workable robot, but I don't think we will be able to apply anything more then rudimentary robocode knowledge to the game.

I made a javascript port of sample.Walls on FightCode. Got #13 place.

You're joking? Hah, wow.

Now we just need to make a port of Girl. Which I think is still the highest ranking extends Robot.

Heh. :-) Pretty cool to see sample.Walls in action in a different game.

Down to #45 now: [1] Seeing as the battles are 1 round and I think it may take some manual action to run battles, the rankings may be a couple orders of magnitude less stable than what we're used to with the RoboRumble.

That #13 place was a stream of lucky battles. Ran some more battles later and the rating kept oscilating between 1485 and 1525.

You can also choose whom to fight against and manipulate your rating by choosing only opponents with high PBI, but I avoided it.

My impressions of FightCode:

The API is simpler than "extends Robot" in Robocode.

No energy drop when firing and the gun and bullets are still invisible to radar. So, no way to detect incoming bullets. But you can assume a bunch of tick-head-on bullets.

No independent radar axis, the radar is always pointing to the same direction the gun is.

No velocity and heading in scans, making even linear targeting a challenge.

No "scan()" method, making bots miss a lot of scans, even when there is a sitting duck in front of their guns. I had to hack Walls code a bit to improve scans, but it is still missing a lot of them. And it is a key strategy in Walls to avoid being crushed by opponents close to walls, like Corners.

I wonder how a rambot will perform there. Since it is hard to keep track of opponents due to limited radar, and the only thing which works together with "ahead()" is "fire()", a bot moving and shooting straight forward can do a lot of damage.

Cool, thanks for the info MN. It's worth noting this game is really young - the first version was built from scratch in a month for a GitHub hacking contest near the end of 2012. They also replied to me on Twitter that some new stuff is coming: "we have some feats in the oven for advanced bots: independent queues for radar, cannon and tank; data storage for machine learning"

I'm curious to see how it does. The whole web-ness and feel of it all really impresses me, and I could see a lot of people trying it that wouldn't have bothered to download Robocode. But at the same time, being stuck with the web interface for all your running and testing and unstable rankings might make it hard to retain power users and maintain a passionate community. Support for local and batch battles would be nice, though it wouldn't be my top priority (yet) as a dev either. It also seems like the gameplay needs some work to approach the depth of Robocode, but it sounds like they're working on that.

What bothered me most was the missed scans, making Walls a lot weaker than it is in Robocode. Feels like bot width is only 1 pixel wide, but didn´t check the engine to be sure.

And FightCode web design is far superior to what RoboRumble is today. Robocode could copy that by having an applet version.

I dunno, with the recent Java security issues, I consider Java in the browser pretty much dead.

I did a bit of tweaking on walls to improve it specifically for FightCode (clone and invisible). I also made a copy of spinbot.

http://fightcodegame.com/profile/Chase-san/

Boo :)

You're back!

You've been a great inspiration to me. I learned a lot about shrinking Codesize from reading your code.

Are you planning to continue writing nanobots? Maybe you could help me unravel DoctorBob's secrets. :)

Thanks! I have uncovered may of Doctor Bob's secrets. You can nearly 100% him if you watch energy drops and reverse direction at around 120 distance. Then just aim a little behind him.

I meant the secrets of how successful it is, not how to beat it. I am trying my hand at nanomelee, but I haven't had much success. (My robot TestMelee is a really crappy derivative of Infinity.) DoctorBob says it has NanoAndrew's movement, but it looks like there must be a little something more. I wondered if you had ever seen DB's code, or heard something from the author.

His code cannot be completely decompiled as he obfiscated it, but if you look around a bit, there are ways of figuring out what he did. Honestly, you can reverse engineer his good pretty easily by the fact that he cannot hit stop and go targets. His radar is lock onto nearest person and charge - which against weaker melee guns and movement works great. The bots that hide in the corner and make small movements counter him well though. Dustbunny does well because it runs from him (and everyone else) :)

What about reversing or not reversing directions when the enemy fires? It seems like DB's pattern is a lot more complex than reversing every other shot.

Hey there Miked. You have interest in fightcodegame?

These guys should be paying me a commission... :-) Welcome back Miked!

And work. Thanks for the good words! I am still attempting to get caught up with a new job and such. I do intend to keep track of things a bit better though going forward and maybe even update things as time allows.

I have a nano project that is currently stalled due to issues with my installation of Robocode, but looks very promising. It has three modes of movement, two of them reacting to enemy fire, and a PM gun.

The only problem is, I can't store .5 as a char, it gets rounded down to 0. So, I had to switch to 1 stored as a char and then divided by 2 to decode the value to a double. Then it was a few bytes over, so I had to switch from WeekendObsession's gun to Moebius's gun. But, in order to have any accuracy with that, I needed to add a setAdjustGunForRobotTurn(true);, which cost 5 bytes and still left me 2 bytes over. If you think you could help, I could post my code.

By the way, I recently helped Chase with his Talon project--a nano with MRM. But I have a feeling that there is a more effective way to implement wall avoidance...

Send me your version that has the best performance but is only a few bytes over, I might have an idea of how to shrink it... as well as a secret weapon which does the same ;-)

THANKS! If I can get it below 250 with the original gun, it would probably take 2nd from Sabreur, and might even give LBB a rough time (until, of course, Mike updates the tables).

Do you want me to post the code here, on a new page, or actually package the bot and host it on the repository?

Just the code is great.

I didn't compile this so there may be a few minor errors. Thanks again.

/*
Epeeist v2.0.0 by Sheldor.  03/19/2013
A NanoBot with multi-mode movement and a Pattern Matching gun.
Codesize: ??? Bytes without any colors.

Epee (pronounced aay-pay) is one of the three forms of modern sport fencing,
along with Foil and Sabre.  http://en.wikipedia.org/wiki/Epee

Credits: 
Pattern Matching code from simonton.WeekendObsession_S and mld.Moebius,
and a general thanks to all open source bot authors and contributors to the RoboWiki.

Epeeist is open source and released under the terms of the RoboWiki Public Code License (RWPCL) - Version 1.1
see license here: http://robowiki.net/wiki/RWPCL
*/

package sheldor.nano;

import robocode.*;
import robocode.util.Utils;

public class Epeeist extends AdvancedRobot
{
	//Global variables.
	static double direction;
	static double enemyEnergy;
	
	static int deathCount;	
	
	//En garde!
	public void run()
	{
		//setAdjustGunForRobotTurn(true);
		
		//Start spinning radar and initialize direction to infinity.
		setTurnRadarRightRadians(direction = Double.POSITIVE_INFINITY);
	}

	public void onScannedRobot(ScannedRobotEvent e)
	{
		//Local variables.
		int matchLength = 30;
		double absoluteBearing;
		double distance;
		int i;
		int index;
		
		//Oscillating/Random movement.
		if (enemyEnergy > (enemyEnergy = e.getEnergy()))
		//if((enemyEnergy - (enemyEnergy = e.getEnergy())) > (Math.round(Math.random() * chancesOfReversing.charAt(deathCount)) * 111))
		//if( (char) ((enemyEnergy - 1.09  - (enemyEnergy = e.getEnergy()))) < 2)
		{
			direction *= (chancesOfReversing.charAt(deathCount) - Math.random());
			//direction *= (chancesOfReversing.charAt(deathCount) - (Math.random() * 2));
		}		
		setAhead(direction);
		
		//Stay perpendicular to the enemy.
		setTurnRightRadians(Math.cos(absoluteBearing = e.getBearingRadians()) + ((160 - (distance = e.getDistance())) * (getVelocity() / 2500)));
		
		//Pattern Matching.
		/*enemyHistory = String.valueOf((char) (e.getVelocity() * (Math.sin(e.getHeadingRadians() - (absoluteBearing += getHeadingRadians()))))).concat(enemyHistory);

    	// search for a match
    	while((matchPosition = enemyHistory.indexOf(enemyHistory.substring(0, integer--), 14)) < 0);

    	// calculate aim offset
    	integer = 14;
    	do { absoluteBearing += ((short) enemyHistory.charAt(--matchPosition)) /  160; } while (--integer > 0);*/
		
		//Pattern Matching
		enemyHistory = String.valueOf((char)(e.getVelocity() * Math.sin(e.getHeadingRadians() - (absoluteBearing += getHeadingRadians())))).concat(enemyHistory);
		while((index = enemyHistory.indexOf(enemyHistory.substring(0, matchLength--), (i = (int)(distance / 12.5)))) < 0);
		do
		{
			absoluteBearing += (short)enemyHistory.charAt(index--) / distance;
		}while(--i > 0);
		
		//Aim at the predicted target.
		setTurnGunRightRadians(Utils.normalRelativeAngle(absoluteBearing - getGunHeadingRadians()));
		
		//Fire!
		setFire(2.5);
		
		//Infinite radar lock.
		setTurnRadarLeftRadians(getRadarTurnRemainingRadians());
	}
	
	public void onDeath(DeathEvent e)
	{
		deathCount++;
	}

	public void onHitWall(HitWallEvent e)
	{
		//Reverse direction when the bot hits a wall.
		direction = -direction;
	}
	
	static String chancesOfReversing = ""
		+ (char) 1 + (char) 0 + (char) 1 + (char) 0
		+ (char) 1 + (char) 0 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5
		+ (char) .5 + (char) .5 + (char) .5 + (char) .5;

	//Preloaded log of enemy movements for pattern matcher.
	static String enemyHistory = ""
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 2
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char)-1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char) 1 + (char) 1 + (char) 1
		+ (char) 1 + (char)-2 + (char)-4 + (char)-6
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-8 + (char)-8 + (char)-8 + (char)-8
		+ (char)-7 + (char)-6 + (char)-5 + (char)-4
		+ (char)-3 + (char)-2 + (char)-1 + (char)1
		+ (char) 2 + (char) 4 + (char) 6 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 8 + (char) 8 + (char) 8 + (char) 8
		+ (char) 7 + (char) 6 + (char) 5 + (char) 4
		+ (char) 3 + (char) 2 + (char) 1 + (char) 1;
}

I'll look at this a bit tonight. There is a savings that can be had by compiling with a different Java compiler. I remember that :)

Thanks.

Skilgannon has already addressed the issue on another talk page, but I would appreciate any help I can get.

BTW, I still feel very that LBB is a pretty cheezy bot. Abusing tables like that probably shouldn't be fair. It takes hours and hours though to get each bot optimized so maybe that makes it a little better overall. besting Moebius is a better accomplishment. At least he doesn't cheat...

Was kinda bummed to see that FightCodeGame is on its way to becoming for-profit and maybe not-open source: [1] They say the game will still be "free" (as in beer, I suppose).

I mean it's their call and best of luck to them, it just feels antithetical to the spirit that's helped communities for Robocode and other programming games thrive for a really long time. And while there's demand for good programming games - a prerequisite to making money off of something - I personally think there will also always be a supply of good / free / open source programming games that make it really hard to turn one into a business. There's just plenty of people that make their living doing other stuff that are happy to create programming games as a hobby.

The majority of non-archive pages on this wiki are either bot pages or user pages. Many of these pages contain outdated information, or could be improved.

So, is it ethical to edit these pages, even though they were personally made by another user for their own work?

For the most part, I think it's fine to edit almost anything on the wiki, particularly if your goal is to improve the wiki and make it more useful to more people. I've migrated/edited lots of such pages. Cigaret and Ascendant are both pages I migrated where I tried to preserve the author's text while also updating inaccurate info and reformatting for the new wiki.

There are a few things I'd consider rude though:

• Major changes to something like User:Chase-san/NewTech.
• On Diamond, editing the ranks in "How competitive" seems fine, but modifying "What's special about it" would seem rude.
• Any major changes to a bot/user page for a user that's active - I'd just say you should discuss it on the talk page first.

Yeah, my thoughts are if the person is active then ask first, if the person isn't active feel free to add, but think very carefully before modifying.

The only good reasons I can think to modify are:

• Grammar/spelling (which is fine)
• Adding links and categories which may not have existed when the author was making the page (also fine)
• Updating rumble positioning and scores (try to stick a date next to the data that's there, then add a new date with current data).
• Possibly adding a brief blurb if the bot was particularly influential in Robocode development.

Is it ethical to edit other people's posts for minor typos/grammatical errors/inaccuracies?

I don't think it's unethical, but it might be unnecessary / annoying. :-) I wouldn't do it for discussion threads, but I might on a content page.

I'm unclear as to when the while loop in the run method starts, so I added a debug command there:

while(true) {
	setDebugProperty("startingWhile", String.format("heading: %.1f° at time %d.", getHeading(),  getTime()));
	ahead(200);
	// ...
}

But to my surprise, this doesn't get displayed until after the ahead and all the following commands are executed, which I would assume should be the beginning of the second iteration. Is there something that prevents these debug properties from being displayed immediately?

To Wombi: Das ist der Fluch der guten Tat. Ich hoffe, Du bereust nicht, meine Frage beantwortet zu haben.

I never used setDebugProperty. Always used plain System.out.println.

Probably, setDebugProperty value is only used inside "execute" events, like all other setter methods.

Hi mate ...

I gave a little example on your user discussion page Discuss - it's a little more appropriate than the main page. Feel free to ask about whatever bother you - no matter what.

Wompi

Hello, please forgive me if this isn't the right place to post this. I'm a noob to Java; two months ago I installed the JDK from Oracle and played around with the examples from the book "Java - A Beginner's Guide". It worked nicely until I installed Robocode. Now, Robocode is working fine, but regardless which of the example programs I try to run, I get the same error:

cd the_directory_that_contains_Example.class 
java Example.class 
Error: Could not find or load main class Example.class

I tried recompiling Example.class from Example.java, but that didn't help. I googled for this error; I found a nice reply at stackoverflow.com/questions/3005433/java-problem-could-not-find-main-class-helloworld, so I tried to explicitly point it to the class directory:

java -classpath . Example.class

But this didn't help either. BTW, I had added the follwing two environment variables for Robocode, but from what I read, they shouldn't matter:

JAVA_HOME="C:\Program Files\Java\jdk1.7.0_07"
Path=C:\Program Files\Java\jdk1.7.0_07\bin;C:\WINDOWS\system32;...

Please help me with this. Thanks!

Hi mate ... Not sure but i guess it should be:

java -cp . Example

not Example.class. Let me know if this worked out for you

That's it! Thanks a lot!

Was just reading oldwiki:RobocodeNG/Archive and came across this choice quote from Albert.

Robocode as it is has reached its maximum. It was more than a year ago that the las truly new idea came (ie. WaveSurfing) and now its all tweaking and optimizing... really boring.

Not sure the date, I think 2005ish. =) And here we are, 7-8 years later, still reaching new heights with our bots. No more paradigm shifting breakthroughs, true, but tons of refinements, many small to medium improvements, and a few pretty big ones along the way. To me, it seems like Wave Surfing was more the beginning of something than an end to Robocode innovation. I think we've taken a more precise and mathemetically sound approach to all aspects of our bots since then.

Since then we've had:

1. Precise Intersection
2. Precise min/max GFs
3. Bullet Shadows
4. Kd-trees (and with them, fast log-based targeting)
5. Super-survivalist bullet powers
6. Gunheat waves
7. Genetic tuning of variables
8. Shoot-everybody melee gun
9. Melee surfing

A lot of these ideas were dependant on wave surfing to begin with, I agree a little with Albert's quote, but it was a bit like saying that now that the transistor (or vacuum tube) was developed, suddenly hardware design was over. I would say no, it has only just begun =) Once we had wave surfing, the same ideas and stats which we used for gun we could adapt for movement, although the lower quantities of data posed a whole new set of problems. I would argue that before wave surfing, the tweaking of movement profiles was much more boring than what we are doing now (although definitely had a lower barrier to entry).

K-nearest neighbours/kd-trees and genetic tuning in particular are bleeding edge AI techniques that come from outside the Robocode world.

New in terms of statistics, I guess. I'm referencing papers for my MSc from the early '90s which were using kD-Trees to speed up KNN search.

Yeah, very well put. At this point, "Wave Surfing" feels to me like a very broad term that would be applied to any intelligent movement system, while there are still so many differentiating details beyond that. I mean, looking at any popular game or sport, most are long past the stages where earth shattering insights can be discovered about game play, but that doesn't mean they are immediately uninteresting. Michael Jordan didn't really do anything new, besides just doing everything better than everyone ever. And he's a pretty exciting chapter in basketball history, if you ask me. =)

Sort of on topic, as I've been working on a new game recently and designing rules, I've been thinking a lot about Robocode's rule set and how much of the game play depth is by luck or by design. It's pretty insane and impressive that the game has held up so well for so long. I try to give credit where it's due and believe it's by design. But then I think about how the scoring had to be changed after release because Mat didn't realize that a non-shooting bot might have the best survival strategy. And how simple the sample bots are, or even the earliest public bots - it's like nobody had any idea where things were going. But maybe if you have some good grasp of game play mechanics at a fundamental level, you don't have to be able to see where things are going to know that you have something with balance and depth. Or maybe Robocode isn't really all that deep compared to what could be, but it's the best we have in a really cool genre and succeeds for lots of other reasons too.

Robocode is NP-complete as most games with depth. Other games might include chess, go and poker.

But Robocode is more than simply a complex game. Having tanks and bullets as theme makes it a lot more fun. There is an intuitive feel about how a tank should behave. Moving and aiming efficiently is simply not enough, robocoders like to make theirs bots move smoothly or turn their guns without shaking.

The engine being open to everyone, with anyone being able to develop a bot (not necessarily competitive) and also being able to upload them in an open internet environment removes most barriers to entry. And being an AI competition ensures there is always someone to compete against. A great deal of Robocode longevity can be credited to RoboRumble.

I think the coolest thing about Robocode is the fact that it has incomplete information, but some information. As in, we don't know what they will be doing, but we can see what they are doing now, and we don't know where they shot, but we can tell that they shot. I'm not sure if this was accidental or not, but it allowed for an extremely complex set of strategies to emerge, and I think it is something which you should attempt to incorporate into BerryBots if you can =)

But yes, I totally agree with MN here, without the rumble and the competition it provides Robocode wouldn't have been nearly as interesting =)

FWIW, I have absolutely been trying to keep some good dynamics with incomplete information in BerryBots. But I haven't spent enough time writing bots yet to get a good feel for what I have so far.

I think what I'll end up with in BerryBots is significantly more information than you get from Robocode on an open battle field, but you also don't see anything beyond walls (besides death events), which is pretty major. I also think that between the visibility stuff and how I'm planning to model the coding of teams, team play could be a lot more fun and popular than it is in Robocode.

Out of curiousity, with regards to teams... how large teams are you thinking of? Some of the videos you've showed with a bunch of bots bouncing around make me think it would be kind of neat to do large swarms if it can be done with acceptable performance :)

Well, I'm certainly leaving the door open for huge teams (say 20, 50, 100 bots?), which I also think would be awesome. Running more than a few complex bots at once is probably not going to be a great experience on the Raspberry Pi, so running huge numbers of bots isn't a major focus just yet. But it should be fine on modern computers.

The big difference in how I want to handle teams is it will just be one program controlling multiple bots, instead of independent programs with only cumbersome messaging between them. You'll have a global view from the visibility of all your bots and be able to control them individually without messing with communication protocols or anything. This should also offer performance gains - the engine has a lot less line of sight calculations to deal with, running 2 Lua states with 50 bots each seems a lot nicer than running 100 separate Lua states, and the bot author can eliminate duplicate processing that would probably exist in each bot if they were running separately.

Imperfect information (invisible bullets) is what makes learning strategies dominant.

If radars could see bullets, Robocode would easily degrade into a ramming game. Imperfect information was probably intentional.

I agree that the game would be much less interesting with visible enemy bullets. However, I don't think that the game would devolve into ramming, or at least, not only ramming at the higher levels. It might make an interesting Robocode sub-species.

Actually, make the bullets visible, crank the gun cooling rate up, and get rid of the turret so that a bot can spit a bullet out in any direction it wants.

With visible bullets, the focus would become (in addition to ramming) the construction of configurations of bullets in air that are impossible to dodge. Pinning the enemy into a corner so that they have limited dodging options would be paramount.

The counter-resonse would be to shoot down the incoming wall of enemy bullets, though this means that one is spending time on defense rather than offense. The refinement of that would be finding the pockets of space-time that bullets could serve both a defensive and offensive function! This would probably represent an investment of processor cycles way beyond what has our bots skipping turns these days.

It'd still be interesting, but probably not as interesting. That information asymmetry really makes things fun!

Yeah, I was thinking that the incomplete information aspect has a lot to do with the depth of Robocode as well, but it's certainly also true that the rumble has a lot to do with it's longevity, allowing it to survive quieter periods when some authors are inactive.

The comparison to other NP-complate games like chess, as well as the incomplete information aspect being brought up makes me wonder how chess strategies would differ if the game rules were modified for incomplete information (i.e. you can only see spaces that your pieces either occupy, can move to, or can attack)

Doing a quick search... seems such chess variations do exist: wikipedia:Dark chess and wikipedia:Kriegspiel (chess).

Oops, NP-complete means the perfect move can´t be easily calculated. NP stands for Non-Polynomial runtime complexity.

But yes, imperfect information is a key feature in Robocode.

Perfect information and imperfect information usually leads to 2 completely different paths. The first leading to backward induction style analysis and the second leading to forward induction.

Man, "Dark Chess" is a really cool sounding game name. =) And appropriate too.

Just decided to put this together, it's a 3D model of a Robocode Robot, I am pretty sure such thing existed in the past, but here it is anyway.

http://file.csdgn.org/robocode/robot3d.png

http://file.csdgn.org/robocode/robot3d.dae

I haven't done the UV mapping or rigid bone rigging yet, but at least the latter is pretty straight forward.

Looks great. The radar is a little bit off - or maybe its just a bad angle. But it looks very very nice so far. Hopefully we can get more of this :)

I'm trying to modify the robocode game for a University assignment and I'm currently stuck so if anyone could help me that would be greatly appreciated. To modify the game I decided to create a new robot type that freezes other robots for a certain amount of turns when it runs into them. I have created a new interface for the freeze robot and altered some of the other code. When the game starts up it goes through all the robots that the user can choose from and creates a RobotPeer for them. And for each RobotPeer they all have a RobotType. If I debug the game here I can check the FreezeRobot that I made that implements the interface and it shows that it has both type FreezeRobot and AdvancedRobot. Which is what I want because if it doesn't implement AdvancedRobot then it can't use any of AdvancedRobot methods. So up till here everything is fine.

Though when I select the FreezeRobot and start a game with it then debug to check the RobotPeer, it is now only an AdvancedRobot. Can someone explain why this is?

In case you are wondering, what I am trying to do is to make edit the RobotPeer code in the checkForRobotCollision method. After it creates a new HitRobotEvent and sends that to the robot, I want to check if the otherRobot is a FreezeRobot and in this case it will change some variable that makes the robot frozen. I haven't worked that part out yet but I need to be able to see if the otherRobot is a FreezeRobot first so hence this post.

If anyone has any advice/tips/help it would be greatly appreciated. Thanks

Hi mate. Not sure if someone here can help you with this. Maybe you should ask your question (or just link it to this post) at the help section of SourceForge Forums. I guess Flamming can say something that might help you.

I hope you keep us informed how it is working out :)

Take Care

Yeah, on the wiki we more deal with robot development than with actual Robocode development. You might want to check out the robocode-developers Google group as well.

Good luck!

Perhaps it is only declared as AdvancedRobot in RobotPeer, but the instance is a FreezeRobot (and, more specifically, your robot class)? If you were seeing the instantiated type, it would show as your robot class. No matter the declared type, in Java you can do "instanceof" to check whether the actual instantiated object is a certain class (like FreezeRobot, or DrussGT), so maybe give that a shot and see if it works.

But yeah, as these guys said, the robocode-developers group and project forums are better places to get input from people who actually work on Robocode. They don't compulsively check the wiki as often as us Robocode addicted bot authors. ;)

Ok thanks I'll try the developers group.

Also I tried 'instanceof' to check the type but it makes a compile error because RobotPeer cannot be compared to FreezeRobot.

Sorry - I meant where ever you're debugging and seeing an AdvancedRobot when you want to see a FreezeRobot, try instanceof on that variable. It's probably true for "instanceof FreezeRobot", which is one way you could test the type of a robot - though probably not the fastest way, so you might want to figure something else in final implementation.

Hey guys, I'd like some input on this. Sometimes it bugs me that the wiki is so disorganized, so much content out of date or needing refactoring, so much unmigrated content on the old wiki. Other times, it feels very organic and like it servers its function perfectly. I'm not sure if spending tons of time cleaning up and migrating old content is really worth the time, but if it is, I'd gladly pitch in on that.

What do you guys think? What would make the wiki better / more usable / more useful / more fun to browse for you?

Personally, I find myself browsing talk pages a lot - it would be nice to have some saner way to browser old / interesting conversations across the wiki. I'd also like to get lots of old bot pages migrated - maybe a semi-automated way of doing that would help.

I´m quite confortable with the wiki the way it is. The only thing that bothers me a bit is having to search for a keyword twice, once in this wiki and again in the old one. Although Google can be a workaround.

I agree that there are some places that need cleanup and such. For my own part, I just need to be bold and go ahead and touch up things when I see them, and not be so afraid to add things. I personally feel far too outclassed and overshadowed by the giants of Robocode to feel myself knowledgeable enough to speak on lots of things, despite my rather thorough mathematical training at university. That might be fixed somewhat when I can get my bot a bit closer to the top of the rumble. *chuckles*

One things that's interesting to think about is the "ownership" of bot pages. There are a lot of bot pages that feature time-specific information (mostly about the bot's current rating) that's quite old indeed. These are bot pages whose authors seem to have left the community, at least for now. The status of what's considered polite to do there is a conversation worth having, I think.

As far as things the wiki could add.. I've noticed lately that there's a Robocoding-term/bot-component that gets mentioned a lot in talk pages and bot version histories and so on, but that doesn't have a wiki page explaining it whatsoever. I've been fiddling with adding this aspect to my bot, and recently decided to scrap everything I've done with it and start it over as a proper Object so it doesn't make a mess of my already messy movement Object. Can anyone guess what it is?

Flattener?

Reminds me... When I started in late 2005, the whole top 10 was Wave Surfing, but there was basically no centralized info on what all is involved or any of the gory details. Sometimes it takes a fresh pair of eyes to notice these gaping holes in the wiki's coverage of topics. =)

Bingo, flattener.

For migrating things over from the oldwiki, a talk page to help coordinate that project might be useful.. maybe have folks vote on whether or not certain articles should get moved over?

I'll try to be more proactive in helping to tidy up and extend the wiki. The information and conversation here is a big part of why I love Robocode! :)

There, started a little stub for Flattener. That's a start anyway :)

Is there a way merge two pages? Or better what is the best way to merge two pages with all the history and discussion stuff? :)

Hmm... I don't think there is a way to merge pages that preserves history for both. I suspect the best option would be... move the page with the most history/content to the new name (if it's not already the correct name), and add the content and discussion-history from the other page.

One thing that could maybe be done is have the "edit summary" include a link to the history of the other page. That way a link to the other appropriate history is there when people are viewing the page history.

I feel like some parts of the wiki could use a little cleanup to expanding on yeah, though I feel that for the most part it works as it should.

Hmm.. MN's comment about search makes me think that if I find some time, I may look into making a little mediawiki plugin to make the search results also show things for the old wiki.

Yeah, I use Google with site:robowiki.net quite a lot myself. That would be pretty cool if you could do that. If not, maybe a custom Google search box could work.

I would like to see something on the main page that shows that the community is active. Maybe some parts of the recent changes, current discussions, lately visited pages or last updated robots. Because when i started with robocode and came to the robowiki (trough the robocode page) it looked to me very abandoned because i was not familiar with the "recent pages" or "talk pages". I had a lot of questions and had no place where i could ask. I think i hit the first talk page by accident 3 month later and it took me even longer to find the "recent pages" (i know its a shame because it is linked on the main page). But i guess if you are not used to how wiki works behind you didn't notice it is there.

Some informations are hidden quite well if you don't know what you are looking for. Lets say the code size related pages. The informations about code size are spread over 3-5 pages i guess and you really have to know what you are searching for.

After i got used to the wiki i found out that most of the interesting informations are on the talk pages. Maybe it is possible to integrate the discussion threads, if they relate to the content, as links in the wiki page as well (probably -1 for bad style but it would save the time to edit the page after each new discussion).

For editing/making pages i would second Tkiesel and feel outclassed and overshadowed by the robocode veterans, plus i don't think my spelling is appropriate for that. I'm also very afraid of moving/summarize pages or insert relevant links because i can not estimate the damage it would bring.

Lately i was in the moot to make a bot pages for the probably most influencing bots to the robocode community - the sample bots :). Just because i think they deserve it and probably most of the robocoders have struggled against these little buggers. I don't know but i guess it would be nice if the new robocoder can start from these bot pages to discover the wiki basics. For example links to linear targeting on Walls or circular targeting an SpinBot, radar lock on SittingDuck or orbiting movement to show how to circle around SittingDuck and so on. My guess is, it would be some sort of entertaining tutorial, and also leads to the feeling what you need to make a robot. I don't know , maybe i'm wrong on that.

All in all i can say, now that i'm a little more used to the wiki i'm very happy with it and like the way how it bonds the community. I'm keen to help with whatever you need.

Take Care

If you want to make new pages, or edit anything, please just do it. If you want to change the main page to show more prominent links to Recent Changes or some sort of howto for the wiki, go ahead. If we don't like it we'll say. After all, it is easier to get forgiveness than to get permission =) Myself, I hardly ever look at the main page, I just bookmark Recent Changes.

When I first came to robowiki (2005/6 or so, I think), I also didn't see the recent changes page for about a week and was impressed that everybody managed to find my page. Of course, that was on the old wiki, but I think a lot of the same problems are still around.

I agree, what the wiki needs is something to get beginners acquainted with the layout (the talk pages, recent changes) and maybe a glossary of commonly used terms and 1 line explanations of them (VCS, wavesurfing, DC/KNN, flattener, HOT etc) with a link to their page. I'm busy over the next few weeks (off to Mexico for Robocup 2012!!), but feel free to do whatever you feel will make the wiki better. The wiki is a community resource, and as part of the community you are strongly encouraged to do whatever you think will help the most! If you want to update old bot pages, or migrate anything over from the old wiki, just go ahead.

Hi mates. I'm planing to link the wiki pages related to the Robocode terms to the terminology category. I think it would be a good source to browse the robowiki pages. Also can you get a fast look on everything that is interesting i guess. Would that be ok for you?

Is it possible to automate something with wiki commands? I had in mind to make a table on the main page where every new entrant to the paticipant pages is linked. So you can see the latest bots who are updated added and whatnot. Not sure where i should start to bring this to life.

It would be great if some of the native speakers could correct my spelling or rewrite some stuff that sounds weird or not appropriate for the official pages. For me it would be a great opportunity to see where i'm wrong and i would not be offended by that at all.

Anyway Take Care

You can write wiki bots to communicate with MediaWiki via APIs. I do some of this with User:VoidBot, and Nat has also done some. If you start working on any wiki bots, let me know and I can give your bot user the "Bots" permission (if you promise to be careful =)). Darkcanuck's RoboRumble server also has an API you can play with: Darkcanuck/RRServer/Query.

I do some neat auto-tracking of RoboRumble activity (which uses both those APIs), and posts its output to @roborumble on Twitter. I've thought about displaying this somewhere (Main Page or RoboRumble), but I'm not sure how to embed a Twitter feed in the content of a page. It's easy for @robowiki in the sidebar because I can just use regular HTML/CSS/Javascript, but the content of wiki pages is handled differently. I'm sure there's a way, maybe with a custom extension?

Hmm i guess the wiki bots is nothing for me by now. But i could think of using the RoboRumble API or even better would be to embed your twitter feed on the main page to see whats going on in the rumble. A quick goggle search told me there is a widget called "Twitter Search" that can embed Twitter feed in wiki pages. This would need the widget extension for this wiki. Not sure how much trouble it would be to set up these things.

I will have a closer look at the RoboRumble API to and maybe i find something that could make this happen.

Btw. the roborumble twitter is indeed very neat .. well done mate

Hia I've only just started using robocode and I have never coded before doe anyone know any good tutorials out there ? Or could you give me any tips on how to get started. Any advise would be appreciated.

Hi Rigged!

The Tutorials on this wiki are great resources, especially Getting Started, My First Robot and Game Physics.

If you're brand new to programming entirely, I'd suggest that you also immerse yourself in some other avenues to learn programming concepts generally and Java in specific. Greenfoot is a tremendous tool for learning basic programming concepts in a very "object-oriented" way, with some great tutorials available.

There are also several good beginner's tutorials on Java in general.

Hi Rigged, welcome to Robocode. I had about 6 months programming experience at high-school (10th grade) level when I first got involved in Robocode. Although RC is a great way to pick up on programming, I do think it is important to have a tiny bit of knowledge of how the basic concepts etc work before starting. Once you understand what a class is, what a method is, and the basics of mathematics in a Java context (plus a bit of geometry/trig) you should be ready to start. The sample bots are lots of fun to play with, and understanding how they work is a great way to pick up on some of the concepts. Once you get there, just ask us what you should got for next and I'm sure you'll get tons of advice =)

Thanks for the advise :). I've started by building a simple robot and i was wondering how do you change the colour of your robot.

Hi. Lets talk about your questions on your user discussion page :) User_talk:Rigged. I think it would be to much for the main page and you can ask whatever you want there.

take care

Hi

My name is Andrew Kirkland. I am currently writing a dissertation at the university of Abertay in Dundee(Scotland) which involves the use of Genetic algorythms to program robots in Robocode. I came accross Robocode JGAP . I have been testing it out but the webpage does not give me much information. Is their a user manual available for this software. I also need some general information on how it works for example the genome and what each of the 6 numbers represent, the fitness function, etc.

Any help would be much appreciated

Thanks

I don´t think anyone here is using Robocode JGAP. But I know genetic programming algorithms are being used with success in RoboRumble.

Currently, the most successful uses of genetic programming algorithms combine conventional development os robots without it, then using genetic programming algorithms to find optimal constants in statistical methods, like parameters in k-nearest neighbors search, kernel density estimation or histograms.

Hi,

I've read about the differences between a Robot and an 'advanced robot' But there is a basic thing I do not understand : Does an advanced robot has an advantage in the battle field over a similar robot, because it can perform several action in the same tick?

As i understand it, if i call ahead(..) followed by fire(), a regular robot will call ahead (and block until it is done) and then fire, while an advanced robot calling setAhead(..) and setFire() will start moving forward and will fire at the same tick, thus having an advantage over it's fellow regular robot. that sounds weird, though..

Am i wrong?

Thank you very much yoni

No, that's how it works. The only disadvantage I can think of is that Advanced robots can lose energy by hitting the wall. Personally, I find Robots boring and Advanced robots awesome, but maybe there are people who actually liked normal robots. Welcome to the wiki!

Thank you very much for the prompt reply.

So why on earth will someone write a regular robot, if a similar advanced robot will kick his ass? is it just a history thing?

The author of Robocode thought Robot would be an easier starting point for beginners. I'm not really sure it is... And as for fairness, I'm not sure he could foresee how competitive Robocode would eventually become. :-)

As for why still write one? Sometimes people like writing bots under different constraints, even if they're silly. The most popular example would be weight classes based on Code Size (Mini/Micro/NanoBots), which even got their own Rumbles. People have also written Robots, Droids (+20 energy, no radar), and Perceptual Bots (don't store any state, even between ticks). Of course, comparing such bots to DrussGT is unfair =), but that doesn't have to ruin the fun. I recently wrote a Perceptual Bot myself (RetroGirl).

Someone can write a robot just for fun. Why there are races on bicycle, when you could also ride a motorbike. Why we have code-restricted classes. Mind you, the best robot (kawigi.robot.Girl) is not easy to defeat, especially in melee. Most school competitions I know of use Robots, as it probably easier to check and control the code and its behaviour, and to prevent 'lending' code from good bots out here. For me, writing a robot is more difficult than writing an advanced robot, because it is hard to wrap my mind around what to do when and so on.

Hi,

Thanks for he answer. I didn't mean for question to be offensive (as in "why should one bother to write a Robot and not an Advanced one) I just wanted to make sure i understood correctly that the Advanced indeed has more power in the battle field.

Yoni

RoboRumble could have an "extends Robot" category.

Hi mates. Is there an issue with RoboWiki? It is very slow and sometimes it even didn't responds.

Yes, I've also noticed this. I suspect a search engine may have been spidering, or perhaps a database backup was running.

I as looking into this on the server today, and it looks to me like the main thing loading the wiki down is Bing being ridiculously aggressive with it's spidering... :(

I'm not really seeing anything on EverythingRobocode that makes it worth having a prominent link on the front page. I don't want to seem like I have a problem with other sites about Robocode coming into existence, because I think it's great. If at some point it has a ton of original content, by all means we should link to it. But right now, it looks like just a few articles, and this is a pretty elite set of links. Could you just post a link on your user page for now?

I agree, we cannot link every page about robocode on the front page, only the most important/informative of them. Compounded the need to add a description as well, which is a bit needless. I will remove it (the link+desc) for now.

Maybe an External Links page filled links? And then link the Main Page to that page.

Hi everyone, Im new to this group but am hoping you might be able to help me out with a project I am going to be running at my school this term. I am going to be delivering an introduction to programming for some Yr 9 students (13 - 14 year olds) starting out with basic programming ideas and examples and then moving onto a group project where teams of students create their own robots using robocode. They will have regular competition against each other to see what team is making the most progress / come up with the best ideas.

The reason I am telling you all this is that I am looking for some mentors to help out and perhaps give some advice. All this would involve is you perhaps receiving 1 or 2 emails with some code or some questions about how to do something. This kind of interaction is really useful for students as they get to work with real experts and feel like they are being listened to and treated like adults.

The project will run for about 6 weeks and will start mid february, as I said it would only involve a couple of emails or perhaps a Skype session. The classes are all small and the students are really hard working

I would be very grateful if you would consider helping out and if you have any questions please fell free to get in touch with me.

Thanks for your help,

Darren

I'm happy to help. I'll be very busy over the next few months getting my project ready for the international Robocup, but the occasional email should be fine.

I'm ready to help, but i'm afraid, that my english skill can become a problem

Thanks for the quick reply, its great to hear that people are keen to help out! I guess the best way to move forward would be to share some contact details. I will then give these out to the students once we start the robocode part of our project around the middle of february. Perhaps each of you could mentor a couple of teams therefore limiting the number of emails you will be getting.

It would be great if you could perhaps tell some other people about this project and see if they would also like to help our as the more people we have involved the better!

My email address is dsutton@nlcsjeju.kr, please email me from the account you would like students to contact you at so that I can start putting a list together.

Thanks again for your help and I look forward to hearing from you and perhaps some other willing helpers soon.

Darren

I'd also be glad to help. Projects like this are always interesting :)

actually i think that every active robocoder is ready to help. and there are google+ circle for robocode: https://plus.google.com/102023615133629629984/posts?fd=1

Thanks for the great response, I've had quite few replies and am also looking for mentors from other more general programming areas as well. If you think you might like to get involved please contact me and I can tell you all about it.

The students had their first programming lessons this week and are really excited, particularly by the idea of working with robocode and having mentors they will be able to contact and share ideas with.

If you have said you will be involved or would like to be can I ask you to send me a quick Bio about yourself and your experience that I can give to students so they can find out a bit about you. It would also be great if you could supply a picture as well and this could be an avatar if you like, It would be nice if students could put a name to a face!

Thanks again for all your help, if you know of anyone who might be willing and able to help please put them in contact with me.

Darren

Just for the record, the downtime this weekend was my fault. Got the server into a nasty OOM state when trying to optimize performance. It should be working properly now (and still faster).

If anyone is noticing Robowiki being slow, it's because a PHP process is hitting a cpu bottleneck right now.

The logs are showing Bing and Baidu doing some heavy spidering right now so it could be that... but it could be something else, I'm not 100% sure.

Are you using php-fpm or spawn-fcgi? From my test, the former performs better under heavy load (though I am not sure since I tested it with nginx, not lighttpd; tested with apachebench with wordpress installation)

fcgi, however the number of requests per second was fairly modest really, so I doubt that type of overhead was the issue. More likely something on the MediaWiki side was being inefficient on the particular pages being spidered I think.

Yay for speedups! :D

I did some tweaking to the server configuration... according to benchmarks I improved things so that Main_Page went from 5.41 requests/second, all the way up to 80.71 requests/second.

Special:RecentChanges improved less though, going from 2.26 requests/second to 3.44 requests/second.

What's the means of "APS","Survival","ELO Rating","Glicko-2(RD)","Battles","Pairings","PL Score" in the RoboRumble?And how to work out them?

"APS","ELO Rating","Glicko-2(RD)": Darkcanuck/RRServer/Ratings
Premier League: [1]

Survival - it's average percent of rounds where robot survive
Battles - it's count of battles in which robot takes part
Pairings - it's count of another robots with which robot has battles
PL Score - it's count of wins in pairings (score percent > 50) * 2

for example robot A has 2 battles with robot B with score percents (45, 60) and no battles with robot C. In this case APS will be (45 + 60) / 2 = 52.5; battles will be 2; pairings will be 1; PL Score will be 1 * 2 = 2

soga,thank you ^_^