Name changing is needed

Warhammer 40,000: Darktide Gameplay Feedback
1

I just wanted to reiterate how important it is that we get this feature. The game already lets you change your FS account name, so arguments about “accountability” are moot. Most importantly, someone pointed out to me why it’s so important that we get this feature as soon as possible,

Ogryn Name Puns.

Really think about it. How many great puns are we missing out on because we have to consider the hassle of recreating a character from scratch, just to update these? Even if you’re one of those unfortunate people who are unable to appreciate puns for some medical reason beyond your control, letting people change names means a pun can be removed once it has completed its work.

Alternatively, let us keep class specific inventory across the account. It would be somewhat bearable if we only had to regrind levels. But to have to deal with all the RNG of re-acquiring equipment, it’s just not worth it at this point.

In the end, it is the greater community as a whole that is punished by being denied fresh new Ogryn puns and having to stare at a “Joe” name for the Nth time in a row.

10 Likes
2

While I’m not against name change as a feature, in the grand scheme of things, I think it’d be fairly low priority

I had intended to post my thoughts to the other name change thread (before it got derailed and locked), but how many people have

  • requested a name change, or
  • had a name change applied (voluntarily or otherwise)

Unless there’s a sizable demand for it, I can’t see it being seen as worth the engineering time to build (versus Support periodically responding to the occasional request/forced rename).

1 Like
3

I would argue that it wouldn’t be a hard a feature to add as they already let us change our Fat Shark account names through the game.

4

That feature had to be added for crossplay to work IIRC (I think it explained it in the crossplay FAQ?)

I’m not suggesting that it’s hard to implement (I’m not going to speculate on how easy/difficult it is either, since I’ve got no idea what FS tools and processes look like), just that it wouldn’t be worth the time in the absence of demand

EDIT: Ah, it was a “may be needed to change your username”

1 Like
5

Joe Rogryn

6

I dunno, I kind of like dropping with three harkens…

:wink:

7

Ogryn puns are needed :pray:

8

Insult1
Insult1799×704 152 KB

1 Like
9

i swear to god, if i see another “joe ogryn”…

10

Realistically how long would it take a coder to implement a name change feature? I’m no expert but that couldn’t be more than a days work.

11

Cousin Ogry

12

I wouldn’t expect it to be very complicated, no. The process itself would probably be more time consuming.

Are there any additional requirements that need to be covered? If Support force a name change, do they just assign a random name that you can update afterwards, or do you have to select a new name before you can proceed to log in, for example? Does there need to be additional rules added for offensive names - if Support force a name change, what’s stopping you changing it back? Are there additional scenarios to be covered?

Then you’ve got to think about where does it go ingame, what does it look like? Since it’s not part of a multi-step process like character creation, it’ll probably look different.

We know what we need to implement and what it should look like, so we can proceed to implement, and write tests to verify that the individual pieces of the system work as we expect. Strictly speaking, the core logic already exists (character creation), although if the code was not designed for reusability, there’s some work there. Any additional requirements that character creation did not cover will need to be implemented.

Now, we can look at testing the system as a whole. Does it function as per the stated requirements? Is there ways to break it? If it breaks, it may go back up to implementation (depending on how easy it is to break, and how badly it breaks)

If we’re satisfied with the above, let’s bring it to stakeholders to make sure they’re satisfied with what’s been implemented - if there’s any feedback, we may need to go back to previous steps to address it (and work our way back down)

Once the stakeholders are satisfied, then we can get it into the main build for a future release. We’ll want some documentation for the patch notes - nothing crazy, but we want people to know it’s there when it’s released

That’s just a rough guess at what the process might look like.

relevant xkcd

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.