Is this a preference or a BS bug on GTKR1.4? When I import something, such as a tank, it changes the names to stuff like t1, t2, t5, etc. I then have to fix it all so the script works. I have half my map made on one save, and half on another. My plan is to import the one half to the other and put it together, but I can’t spend 5 hours checking and changing all the names if it keeps this BS t1, t2 name thing.
Anyone know anything about this?
I dunno if it’s a bug or a feature, but most people probably could do without it. Which is probably why NetRadiant changed the behaviour to how you’d expect :
Clone selection change
“Clone selection” (space) no longer changes targetname/target of entities, so you can clone to create many entities to target one. If you want to change targetname/target when cloning like Radiant did before, use Shift+Space.
(I’m pretty sure that’s what they’re talking about anyway… I haven’t actually tried it)
Yep, that’s what I’m talking about. So it’s a ‘feature’. Oh great. Looks like I’ll have a couple hours of work extra on my hands.
Or you can just press L and open up the Entity list and make the needed changes there. That will save you the hours of work you placed in to renaming them with the previous method. 
This(what radiant calls) handy feature just annoyes almost every mapper
Just copy in notepad and the problems are gone =)
hmm I think 1 of the 2 versions doesn’t do it, 1.5 or 1.4
and netradiant is also not perfect. When you import script_movers they get messed up in my experience.
use netradiant to add the 2 maps as 1 then, and then just save it and load er up in 1.4?
Well from what Stealth says, script_movers will get screwed up, which I have a lot in my map. I’ll simply do what Pegazus said, hopefully it won’t take long 
Aha. I don’t use 1.4, but I opened it and ran preferences. Untick Pref./Editing/Fix targetname collision. That seems to do the trick.