There must be some way that it is possible to add a space to a device’s NAME and VALUE in Eagle, right?
I’ve created a footprint for the NES controller socket from Parallax and I want the part’s VALUE to be “NES Controller” and the part’s NAME prefix to be "PLAYER ". This way, as I add NES controllers to the schematic, they are named “PLAYER 1”, “PLAYER 2”, etc. I know that I’m being way too picky, but that’s just how I am. 
BoWingo:
There must be some way that it is possible to add a space to a device’s NAME and VALUE in Eagle, right?
Assume that there isn’t. By now you have probably tried
and likely know it can’t be done.
BoWingo:
I want the part’s VALUE to be “NES Controller” and the part’s NAME prefix to be "PLAYER ".
Perhaps you can settle for an underscore?
PLAYER_1, PLAYER_2, PLAYER_3, etc.
Values - did you try? it works fine for me.
Names - Don’t think so. Use “_” like Big said.
You’re right about VALUE. The library item cannot be named with a space, but it can be changed in the schematic to have a space. I didn’t realize that.
Ideally I would like the ability to assign the library device the value “NES Controller” and a name prefix of "PLAYER " (PLAYER), but I will settle for an underscore. It was late and I didn’t think of that. 
BoWingo:
Ideally I would like the ability to assign the library device the value “NES Controller” and a name prefix of "PLAYER " (PLAYER), but I will settle for and underscore.
It’s your call what you do or don’t do. The industry
has standards for all the appropriate reasons, and
you are now establishing your own “standard” that
may confuse others not trained in your scheme.
Why not use the industry standard names and values,
and place a text string to clarify your specific needs?