SSG, did you guys not enable the Year+ name "overtaking" feature of World Transfers?

[ChromiteSwiftpaw]

I copied a character with a name I know has been idle/never logged in for years (character was made, is sitting at Character select and never logged in). My Bombadil copy to that server did NOT get the name and instead got a -1 added.

Cordovan/any other dev can you please comment on whether it's properly working or not before I waste my copies? And is there any way to get the name I wanted for that one that didn't work?

[RiverBirch]

0

What's the Estimated wait time for a ticket?

The top of the ticket window tells you the est wait time.

[Druidsfire]

Back when they restored transfers after the months-long removal, I transferred one alt from Crick to Landy and a second alt from Ark to Landy... and I'd added the original Landy characters to my friends' list, which you can sort by last login and use relative dating principles to figure out whether the name is more than a year idle. I took screenshots of that friends list before and after... and my characters got the -1 despite proof that I should have gotten the name without the -1 both times. I had to put in a ticket to get it fixed. I tried both in-game and website tickets. The in-game ticket was for the Ark character and simply gave me the name. The website ticket was 'we unlocked your names, go get 'em!'... which meant ANYONE could have ganked the names until I quickly logged in and reclaimed the name on the Crick character since the Ark character was already forced to be the right name. To this day, I still keep getting a 'rename your character' alert on the character originally from Ark, which I cheerfully ignore.

All I can recommend is putting in a ticket, and picking whichever one you feel will work better for you. Both times, I made sure to cite the CURRENT transfer policy (I believe Cord removed the old/out-of-date transfer pages dating back to the 2014/2015 consolidations) - which specifically details what is SUPPOSED to happen during naming conflicts. If you have proof that the name you're transferring in from Bombadil is >1 year idle, then the policy is clear in that you should get that name.

Good luck!

[Echoweaver]

All I can recommend is putting in a ticket, and picking whichever one you feel will work better for you. Both times, I made sure to cite the CURRENT transfer policy (I believe Cord removed the old/out-of-date transfer pages dating back to the 2014/2015 consolidations) - which specifically details what is SUPPOSED to happen during naming conflicts. If you have proof that the name you're transferring in from Bombadil is >1 year idle, then the policy is clear in that you should get that name.

Stupid question time -- how do I see the date, including year, that a character last logged in?

[Arnenna]

If we end up with a -1 name, do we get a rename token? Anyone know?

Iirc (which I may not, because it was a long time ago), didn't we get a rename token when world consolidation transfers took place, if we ended up with a -1 name?

[ChromiteSwiftpaw]

If we end up with a -1 name, do we get a rename token?

Yes.

[Thurallor]

Both times, I made sure to cite the CURRENT transfer policy (I believe Cord removed the old/out-of-date transfer pages dating back to the 2014/2015 consolidations) - which specifically details what is SUPPOSED to happen during naming conflicts. If you have proof that the name you're transferring in from Bombadil is >1 year idle, then the policy is clear in that you should get that name.

How does one go about finding the current transfer policy?

[Stechmucke]

Well, all the names I transferred hadn't been on in well over a year. Yet, I got -1s. The names I was tracking (my names I originally had but lost after server transfers) updated their last locations, dates and even levels to my Bombadil characters info when I logged the day before Bombadil closed. I sent in a pic of the friend's list but hadn't heard back. Here is the screenshot I sent to in with my ticket.

https://imgur.com/N9byy1o

[Arnenna]

Yes.

Thanks.

[Druidsfire]

Well, all the names I transferred hadn't been on in well over a year. Yet, I got -1s. The names I was tracking (my names I originally had but lost after server transfers) updated their last locations, dates and even levels to my Bombadil characters info when I logged the day before Bombadil closed. I sent in a pic of the friend's list but hadn't heard back. Here is the screenshot I sent to in with my ticket.

https://imgur.com/N9byy1o

Yep, if you transfer in, the friends list gets updated with YOUR character's last login until somehow the database shakes the info around at some point. You can try removing the name and re-adding and it *should* theoretically update with the correct information, but as when they resumed transfers after them being down for months, the only thing you can do to *prove* the time is to take a screenie before you transfer in.

[Druidsfire]

How does one go about finding the current transfer policy?

https://lotro.com/en/worldtransfer, published when they resumed transfers.

[Druidsfire]

Stupid question time -- how do I see the date, including year, that a character last logged in?

There is no way to know the year for sure... the best you can do is have someone on your friends list who is more than a year idle (look in your kin list if you don't have one already in your friends list), and sort your friends list by last login. Watch how the months/days cycle around. There's someone in my friends list who logs in once a year for a specific event, so I use their character as my yardstick.

[Stechmucke]

Yep, if you transfer in, the friends list gets updated with YOUR character's last login until somehow the database shakes the info around at some point. You can try removing the name and re-adding and it *should* theoretically update with the correct information, but as when they resumed transfers after them being down for months, the only thing you can do to *prove* the time is to take a screenie before you transfer in.

BUt it's updating the non-existent cloned characters. I would have done screenshots if I'd have known they were going to screw it up.

[Stechmucke]

There is no way to know the year for sure... the best you can do is have someone on your friends list who is more than a year idle (look in your kin list if you don't have one already in your friends list), and sort your friends list by last login. Watch how the months/days cycle around. There's someone in my friends list who logs in once a year for a specific event, so I use their character as my yardstick.

Wonderful. They closed my ticket with an automated message. It's apparent that they didn't read my ticket or look at the screenshots. I don't know how you got them to help you but it's apparent customer service is NOT going to address this. I've played since the beta days. Thirteen years but this may be a deal-breaker. I'll drop from the game. A name issue may sound trivial but I hate having this obvious bug being ignored.

[Stechmucke]

This is their response:

Greetings. Players are able to use the /changename command to change their name to the one of their choosing. Players that received the naming priority were recently logged in to their accounts in the last year. We are unable to free any names for players to use if the player has recently logged in to their account. This is automated within the transfer process and has worked as intended. In-Game Support cannot make names available for character transfers. Thank you for contacting support.

It clearly does not work as intended. I would like to know who that person was that logged in.

[Braer]

We have tried to inform SSG that the transfer mechanic hasn't worked when intro characters are holding a name but hidden from player view. We tried to get some work done on transfers so it wasn't an all or nothing thing especially when it became a paid service. We try to warn of the impending ticket load switching on transfers will entail, players unnecessarily loosing their names and getting the brush off and the AWOL curator when people have a bunch of figments incoming; and it falls on deaf ears.

[Braer]

Quick fix:

Rename all characters in the intro over a year old with a -x and issue a rename token. Switch off transfers until it's done.

Then address the mechanic before the closed servers come to transfers.

[-x1,-x2 etc]

[Thurallor]

We have tried to inform SSG that the transfer mechanic hasn't worked when intro characters are holding a name but hidden from player view. We tried to get some work done on transfers so it wasn't an all or nothing thing especially when it became a paid service. We try to warn of the impending ticket load switching on transfers will entail, players unnecessarily loosing their names and getting the brush off and the AWOL curator when people have a bunch of figments incoming; and it falls on deaf ears.

It isn't just players in the intro. It happened to me today, and the inactive character is level 11.

[Elhiril]

This happened to me too. Like everyone else, I've tracked the name for years and I'm confident I should have priority. The character now updated to a clone of mine and I got name-1. Ticket submitted, so hopefully it'll get looked at. I'm hesitant to trasnfer any more characters until I know it works as intended, which is especially an issue with Bombadil given the limited time we can transfer off.

[Braer]

It isn't just players in the intro. It happened to me today, and the inactive character is level 11.

But can you tell how long it's been inactive? Did it exist before you transferred? And are you a different level and class?

If there is a hidden char in the intro (we assume this is the case because it's the more likely beyond even more flaws in the mechanic and people have tested it out) then you can friend a char with your name and one will be displayed generated at the time of the transfer with your level class and location. If that hidden char progressed out of the intro then the "friend" would update to this char.

Was your char level 11 and the same class? Not sure if the anon status would also be retained making a location hidden. This behavior has been seen by many of us.

But there will be many who legitimately get a -1 so easy assumption that all the -1 names are as intended. Druidsfire detailed her prep for over a year to get her name and fell foul but had CS fix it by changing the blocking char's name. They seem to be unwilling to do that any more given the closed tickets above.

You can imagine that Cord has talked to the people with the code and been told it's working as intended. But did it involve a code review or a brush off?

[MerryCav]

This happened to me too. Like everyone else, I've tracked the name for years and I'm confident I should have priority. The character now updated to a clone of mine and I got name-1. Ticket submitted, so hopefully it'll get looked at. I'm hesitant to trasnfer any more characters until I know it works as intended, which is especially an issue with Bombadil given the limited time we can transfer off.

yep same with mine. trying to take over a 4-5 plus year dead name. Yet, when i transferred from Bombadil today I was given -1 (and the dead name in my friends list was updated with my characters level, crafting, etc) This was the ONLY reason I played Bombadil! I'm hoping beyond hope it is a minor glitch. I'm soo so so so bummed right now..just don't even want to log into the game.

[Braer]

yep same with mine. trying to take over a 4-5 plus year dead name yet. when i transfered from Bombadil today I was given -1 (and the dead name in my friends list was updated with my characters level, crafting, etc0 This was ONLY reason I played Bombadil! I'm hoping beyond hop it is a minor glitch. I'm soo so so so bummed right now..just don't even want to log into the game.

So at some stage it's seeing the dormant char as having a lesser priority, generating this phantom copy of yours with your name but then giving you the -1. Is there a -2 attached to the old dormant char now and why you got the updated?

It's looking like it's just stumbling dealing with the conflict. It would help if there's anyone who has usurped a name successfully knowing their target's history?

And how many are playing with a second choice name believing themselves unlucky not a victim of a bug.

[maartena]

I'm pretty sure that doesn't work anymore.

I actually created two toons on Bombadil and got them to level 5 with the SOLE PURPOSE for transferring them to Arkenstone later to grab an old name. The name I want is someone that has left the game almost 3 years ago, and I am 100% certain that character has not logged in since then, and the last login date (although obviously no year is listed) is exactly the same.

So that was a bust. Both characters actually got a -2 behind them, meaning a -1 already exists as well.

That all said: I know this was a thing with the 2015 server consolidation, but I cannot remember whether that would be permanent or not..... They had to re-code the transfer system when they changed database software, and I bet ya anything this feature was just not included. Maybe it turned out to be too consuming to re-program.....

[MerryCav]

So at some stage it's seeing the dormant char as having a lesser priority, generating this phantom copy of yours with your name but then giving you the -1. Is there a -2 attached to the old dormant char now and why you got the "upsted"?

It's looking like it's just stumbling dealing with the conflict. It would help if there's anyone who has usurped a name successfully knowing their target's history?

And how many are playing with a second choice name believing themselves unlucky not a victim of a bug.

sorry, went back and fixed a few typos (damn wine). 'Upsted' should have been 'updated' in my original post (my target's history was at the very least several years unplayed, at level 4, in archet..just idle)

[MerryCav]

sorry, went back and fixed a few typos (damn wine). 'Upsted' should have been 'updated' in my original post (my target's history was at the very least several years unplayed, at level 4, in archet..just idle)

Bombadil was stated to use "standard restrictions and procedures apply when transferring from Bombadil" ...and those standards for transferring names is:

If there is a naming conflict, the transfer process will grant the name to to the incoming character only if the existing character on the world has not been active for more than one year. The less active character will have a -1 added to their name, and a rename token will be granted to the character. The character whose name has been changed can be renamed by the player by typing the following command into the game chat window: /changename <new name>.

It was clear to me (and others it seems), that if we transferred a toon from Bombadil with a name that was dormant over a year on our home server...we'd be granted that name.

Reeeeeally hoping this is a glitch.