From: "Jan E." Date: 2012-10-03T05:20:39+09:00 Subject: Re: still learning by doing - connecting rooms in a game Sebastjan H. wrote in post #1078412: > actually, I did get that error:) OK, then you should have told us the exact error message. We don't know what you're doing on your computer, what you've expected to get and what you actually got. So we need specific information. Something like: I tried to set the attribute "name" with zombie.name = 'somename' and got a NoMethodError saying "undefined method `name=' for #". Then we know what's going on and can help fixing the error. But when you say that the code "doesn't work", it tells us pretty much nothing. This could mean anything from a crashed Ruby interpreter to a tiny encoding problem. It's even more difficult when the code *does* work and just doesn't meet your expections (that we don't know). The error message is actually the most important part in debugging, because it tells you exactly *what* went wrong. In this case it's saying that your object doesn't have a method "name=". And that's all you need to know. Even if you knew nothing about Ruby and didn't have any access to other information, you could still fix the error just by doing what the message is telling you (which, of course, isn't really a good approach). -- Posted via http://www.ruby-forum.com/.