Does my table violate normalization rules? I am developing an emulator for a game.  My item table looks like this:

-- ----------------------------
-- Table structure for `items`
-- ----------------------------
DROP TABLE IF EXISTS `items`;
CREATE TABLE `items` (
  `guid` int(11) NOT NULL,
  `template` int(11) NOT NULL,
  `quantity` int(11) NOT NULL,
  `position` int(11) NOT NULL,
  `stats` text NOT NULL,
  UNIQUE KEY `guid` (`guid`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;


so some rows look like this (row is wrapped for readability): 

'110', '6797', '1', '6', 
     'b6#1#0#0#0d0+1,3ca#2412#0#0#0d0+9234,3cb#1#0#0#0d0+1,3cc#1#0#0#0d0+1,
      3cd#a#0#0#0d0+10,3ce#1#0#0#0d0+1'


As you can see the long mess at the end is only one column - they are stats.  I think this field could be divided into individual stats in more columns.  Would that violate normalization rules? Should columns hold only indivisible attributes?
don't add more stat columns unless you are absolutely sure the required # of columns wont grow, tables tend to get unmanageable that way.

if you need to work with the individual stats in your comma separated text field, you probably should break them off into their own table where each row has 1 stat, make  guid+statid your primary key and then you can make the stat column something more reasonable like a varchar (20). This might take up a little more diskspace but it should be faster working with individual stats...