Loading...
  OR  Zero-K Name:    Password:   

A Rose By Any Other Name

66 posts, 1892 views
Post comment
Filter:    Player:  
Page of 4 (66 records)
sort


8 years ago
They're at it again: https://github.com/ZeroK-RTS/Zero-K/pull/1339

Someone please make them stop.
+2 / -0
8 years ago

You know. You all know exactly who I am.
Say my name.
+4 / -0

8 years ago
armwar.png?
+4 / -0


8 years ago
+2 / -0


8 years ago
Cross-posting from GitHub:

While I kinda like the themed name idea, the options don't work:

http://classic.battle.net/war3/undead/units/ghoul.shtml is a ghoul
http://classic.battle.net/war3/nightelf/units/wisp.shtml is a wisp

Since WarCraft 3 is getting a bit of recent publicity due to a patch announcement, I'm pretty sure that's the first thing people are going to think when they hear "ghoul" or "wisp". I do think Warrior is a bit generic, though I like Tick because they are sneaky and disabling units is a neat reference to Lyme disease.

I think the bigger issue with themed names is "why?" Now, from an out-of-fiction dev perspective and to have a sense of factory name consistency it makes sense to theme names, but from a player perspective it's just a bunch of random words. There's no underlying theme or flavour behind the names (an issue shared with OTA), which means anything more elaborate and specific than one short word name is so out of place as to not fit at all, but just having random one-word names makes it harder to create a sense of identity as a game.

I realize that ZK's units are primarily OTA units remodeled, renamed, and regrouped, so it might come off as pretentious to do this, but having some kind of in-fiction justification for the names and themed names would help sell the theming. Maybe each factory was once a product of a specific human faction or corporation, and the robots just managed to get access to all the blueprints by the time of the game, so these random names are actually model/brand names, which tend to be a bit random, cf. car model names.
+2 / -0


8 years ago
Thanks for commenting. I'll respond here, not there.

I get what you're suggesting, and it's not a bad idea. It would, however, require a complete renaming of almost everything AFTER someone clever and creative comes up with a good in-fiction concept behind the entire panoply of units.

As it is, what we have today is piecemeal work. That's the nature of Zero-K development. We can't get someone to design 150 units from scratch with a consistent art style and theming and concept, so we just hope we can get someone to at least do an entire factory. Similarly, but for different reasons, we can't do a complete overhaul of, well, anything, so we make small changes here and there. Like renaming all the aircraft after birds.

With names, these piecemeal changes have ended up bringing us towards a bland homegenization, which is terrible for several reasons we've covered elsewhere. One of the driving forces has been this notion of getting rid of all the OTA content, which is certainly right for artwork but not necessarily right for names. The best way to fulfil that driving force would be to do something like you're talking about here - take a big step back and rework the entire thematic concept of the game, and then use THAT to drive the development of the units' character. But we're stuck in piecemeal hell so that's not likely to happen anytime soon, or honestly probably ever.

So instead of coming up with a vibrant theme / trope / melieu (I hesitate to call it a "backstory" because game fiction is terrible)... you know, the kind of thing that you can see in the three (or four) factions in SupCom, or the three (plus) factions in StarCraft, or even the two factions in OTA...

We just have a game.

Which is fine, because it's a GREAT game. But if we aren't going to give the unit ensemble some kind of character as a whole, then we should at least make the names work well as a game if not as fiction. The current trend of simplifying and choosing laundry lists of bland synonyms is a terrible approach. We can do much better. In fact, we'd do much better just by leaving them as they are right now.
+4 / -0


8 years ago
I guess that's the other way to look at my point. Since we probably aren't going to write up a world-building document to prop up the names, then basing it off function at least keeps things grounded. I'm kinda surprised I never noticed until the Warrior -> Ghoul suggestion, but there you go.
+0 / -0

8 years ago
I think names should be as iconic as possible while:

a) not transgressing on already over-tilled soil

and

b) evoking the function of the piece in question

For example, many of the hurt-er units feel misnamed. All of the robots hurt shit.
- The scorcher doesn't actually use fire.
- Slasher doesn't slash, it prods like a pool cue.
- Pillager sieges and never gets near the spoils of war. Often sits at home while its friends are out raiding.
- Reaper is less about reaping and more about out-surviving.
- Banisher is a supportish tricksy name, on a riot.

Other thematic stumbles include:
- Rogue is a gaming class that plays entirely unlike how zk rogue operates.
- Roach evokes expendability and survivability, not suicide.
- The felon is not antisocial. It's a play-together synergy hug bear. Team work guys!
- Funnel web doesn't ambush. It's the inverse of its namesake.
- Scalpels dealing explosive damage (imprecise).
- Halberd being named after a weapon that doesn't assist in defense.
- Scallop doesn't have any defensive ability. Also it's got insane dps. Perhaps halberd and scallop should swap?
- Ducks don't float.
- Archer doesn't shoot projectiles.
- Phoenix is fragile and dies all the frkn time in enemy territory where is can't be reborn.
- Raven is more like a raptor than a scavenger. It swoops in and kills something.
- Defenders are not as good at defending as lotus. Which is a flower.
- Wolverine is a fragile piss-ant that tickles people from afar with its magical explosive claws.
+1 / -0


8 years ago
"Evoking the function" is a bad game to play. Nouns can evoke dozens of characteristics; most of them won't fit the unit in question, and probably at least one will, for someone.

It's also a good way to get bland, boring, homogenized names.

Names should first and foremost be interesting, second-most be distinctive, and third-most avoid being ugly or awkward. The name should also fit the unit in some fashion - which is what I think you had in mind - but evoking it's function is not necessarily the only way to go. For example, Roach is a fine name, because it's a small crawling robot, and is similar to the Tick and the Flea which are also small crawling robots. The three of them make a great set. Yes, there's a risk of getting the names confused, and that's bad... but the character of the names and how well they match the character of the bots and how well they work together as a (small) set make up for it.

If the names are interesting and distinctive enough, the players will learn which ones go with which units, and will build their own associations. We don't have to strive to be clever. "Oh, this is a shielded airplane, so let's call it the Eagle, because eagles fly and are often depicted with shields in American iconography." That's just trying too hard, and it makes for uncreative names.
+1 / -0
There's nothing worth preserving in the names Warrior and Tick, except the getting-usedness and convenience of the current small playerbase.

Warrior is as generically boring as it gets, and it's OTA too.

Tick is a parallel to shieldbots' Roach. Both are crawly things, an insect and an arachnid. The comparison is cute, but not necessary to preserve.

In general, I support the spooky theme for the factory, as long as the names aren't too cliche and fit the units well. Ghoul and Wisp are spot on.
+2 / -0

8 years ago
Function might be the wrong word. We don't want every fac having a unit called 'raider'. "Fitting the unit in some fashion" is closer to the mark, yes.

With the tick/flea/roach line, I think flea is perfectly named, but tick and roach not so much. Infiltrator feels more like a tick to me. I don't agree about the 'set' thing, since a set that lines multiple factories is wasted association. Ticks and roaches are constantly mistaken for one another.

People do learn to distinguish, but it should be as easy for them as possible. Scorcher and slasher are highly distinct, but I still get them mixed up due to the 'sxxxher' they share.
+1 / -0
I really like Ghoul. Contamination with BlizzardCraft is irrelevant: we also have Banshees, Vultures, Roaches, you name it.

Ghoul fits the unit also on two unmentioned aspects: it regenerates, and it's considered repulsive/ugly in current meta.

AUrankSnuggleBass: archer fish catches insect by shooting them with water. Scorcher uses a heat weapon.
+4 / -0
8 years ago
But we should never forget wubrior!
+2 / -0

8 years ago
quote:
bland boring names, theme is a list of synonyms

Because Warrior is an interesting, unique name and is not at all utterly generic. Yeah.

I'd be willing to agree that a few of our existing themes are lists of synonyms but evil magic is not one of them. It could have been made terrible, it contains a lot of synonym groups, eg:
  • Spectre, Ghost, Wight, and Wraith.
  • Ghoul, Zombie, and Thrall.
  • Demon, Fiend.
If you picked names mostly from a single group you'd indeed get a bunch of synonyms. This is a problem in Shield and the vehicle facs. But note how existing plus proposed names for Cloaky are all from distinct groups.

I'd say most of the problems you have with themes is that the themes we have are misused. For example:
  • a glaive is a long-reach two-handed weapon which you can't swing fast with. Sounds like Rocko.
  • a scalpel is a precision cutting tool, like a laser, while a mace is a blunt bashing tool, like an explosive rocket.

quote:
"Evoking the function" is a bad game to play. Nouns can evoke dozens of characteristics; most of them won't fit the unit in question, and probably at least one will, for someone.

Not unless your choice of nouns is terrible. The trick is to pick a noun which evokes the right characteristic most of the time. I have no idea how anyone could associate "Ghoul" with anything else than mauling stuff.
+4 / -0


8 years ago
Well, for starters, a ghoul is a carrion-eater; a loathsome scavenger, not a killer. Go look it up. If anything, "ghoul" is an appropriate name for the constructor (because of reclaim).

This is the danger of trying to make names that "work". The associations that you have with some word are often going to be different from those that someone else has.
+1 / -0


8 years ago
quote:
I don't agree about the 'set' thing, since a set that lines multiple factories is wasted association.


On the contrary. Compare Thug/Rogue/Felon to Tick/Roach/Flea. In the first case, you know they're all shieldbots; in the second case, you know they're all small robots. In both cases you still have no idea which bot is which.

The difference is that with the shieldbots you have to learn which is which across Thug/Rogue/Felon/Bandit/Outlaw/Vandal/Racketeer/Gangster (wait, is that last one a unit or am I getting them mixed up again?) whereas with the insectbots you only have to learn to distinguish between Tick/Roach/Flee. That's why I say that a set of three is actually a helpful thematic naming whereas a set of seven (or worse) is a harmful theming.

Distinctive names are good. Names that can be tied to the unit are good. Sets of names that can be tied to each other are good. Large collections of essentially identical names are bad.
+0 / -0
quote:
whereas with the insectbots you only have to learn to distinguish between Tick/Roach/Flee

quote:
That's why I say that a set of three is actually a helpful thematic naming whereas a set of seven (or worse) is a harmful theming.

Tick and Flea are (commonly known as) parasites, while Roach is an omnivore. Whereas, Tick and Roach are kamikaze units and Flea is a scout/raider.

ZK contains at least 7 more insect-like (arachnid) names [?]

[Spoiler]

Are you sure you want to use this as an argument?
+0 / -0

8 years ago
quote:
a ghoul is a carrion-eater; a loathsome scavenger

No, a ghoul (غول) and sometimes used in the feminine form (غولة) is an evil demon who preys upon desert travellers etc.
(trivia: in present times it is used as slang for an unattractive person).
The carrion-eater theme is silly western culture.
Contrast djinn (or genie) which can also be good (Aladdin's for instance).
+0 / -0
8 years ago
quote:
There's nothing worth preserving in the names Warrior and Tick, except the getting-usedness and convenience of the current small playerbase.
In this case 'getting-usedness and convenience of the current small playerbase' means not constantly breaking:
- forum posts
- videos with commentary
- the brains of people
- tutorials / missions (yes, very few exist but some mention unit names to player)
- manual/forum texts about how to play
-...
+0 / -0


8 years ago
The shieldbot names aren't always the most distinct but Bandit, Rogue and Thug all have partly or really obvious connotations that fit their unit[?], and Racketeer is an obvious pun that connects to its weapon[*].
+3 / -0
Page of 4 (66 records)