Prevent named hatchlings from being abandoned

[0x08]

Just as named hatchlings cannot be teleported, I think it would be good to keep named hatchling from being abandoned.

 

Below is the Actions page as it looks now, and then a quick mockup of the same page if this feature was implemented.

 

Abandon — Abandon the hatchling to die. others may claim the abandoned hatchling and take it as their own.

🠗

Abandon — You cannot abandon a named hatchling.

 

Please share your thoughts on this suggestion.

[Fuzzbucket]

I thought named hatchies COULD be teleported ? Even so - I  can't see the need for this; it's easy enough to choose what you want to teleport or abandon. What exactly would this achieve ?

Edited October 31, 2021 by Fuzzbucket

[LevelsOfViolence]

You cannot teleport named hatchlings.

 

Spoiler

 

Personally, I am indifferent to the suggestion - though I suppose it would be consistent with Teleport and become yet another fail-safe against abandoning. There are no downsides either, since you have to consciously name a hatchling, which implies that you are probably intending to keep it. Support.

[0x08]

8 minutes ago, Fuzzbucket said:

I thought named hatchies COULD be teleported ?

Nope! I even checked to make sure. The checkbox to select a hatchling to teleport is replaced by the string (Named).

 

8 minutes ago, Fuzzbucket said:

I  can't see the need for this; it's easy enough to choose what you want to teleport or abandon. What exactly would this achieve ?

My motivation is: When one is dealing with a lot of hatchlings at a time, or is in a rush to replace a batch with the next, one may get the hatchlings mixed up with each other and accidentally abandon the wrong ones. This may or may not have happened to me recently. And as LevelsOfViolence pointed out, it would create some consistency which tends to be nice.

Edited October 31, 2021 by 0x08

[MissK.]

I actually thought named hatchlings couldn't be abandoned already, didn't it use to be a method of not getting rid of them by accident? Was something changed at some point? Either that or I dreamt the whole thing up I suppose.

 

Either way, it seems odd to me too. If they can't be teleported it shouldn't be possible to abandon them either, unless you remove the name first of course.

[0x08]

2 minutes ago, MissK. said:

unless you remove the name first of course.

Yeah! When one sees the message "you cannot abandon a named hatchling" then it is understood that the name should be removed to abandon.

Edited October 31, 2021 by 0x08

[MissK.]

Makes sense to me, I legit thought that's how it was until seeing this thread lol.

 

Also for the record, a friend who is also an old player just confirmed that he also remembers naming being a way of not dumping something accidentally, so at least I'm not crazy.

[HeatherMarie]

40 minutes ago, MissK. said:

I actually thought named hatchlings couldn't be abandoned already, didn't it use to be a method of not getting rid of them by accident? Was something changed at some point? Either that or I dreamt the whole thing up I suppose.

 

Either way, it seems odd to me too. If they can't be teleported it shouldn't be possible to abandon them either, unless you remove the name first of course.

 

I could've sworn there was a time when they couldn't be abandoned, because yeah I think I remember using naming as an easy way to stop from accidentally abandoning them. 

 

It does make sense for consistency's sake, if you can't 'abandon' the hatchie to another user if it's named then you shouldn't be able to 'abandon' it to the AP either. 

[DragonLady86]

Yeah it used to the case and a lot of people complained about "why can't I abandon this hatchling?" (because it didn't say it was because it was named the action was just grayed out) so TJ changed it.

[Ruffledfeathers]

Maybe if it was clear in the text like

 

‘you cannot abandon a named hatchling. Please remove the name first.’ 

 

This was such a good way of making sure keepers arent misclicked and dropped. Its extremely easy to do, especially with new things like finger auth which take seconds!

[Fuzzbucket]

Surely - just don't name anything you might want to abandon ? Then if it's named - you know not to do that.

[Shadowdrake]

48 minutes ago, Fuzzbucket said:

Surely - just don't name anything you might want to abandon ? Then if it's named - you know not to do that.

The problem is there's no differentiation between this action link and that action link on many skins. It's the same problem as teleport links before TJ made a format adjustment; naming doesn't help if it's hard to determine which action link belongs to which dragon.

 

It's also a minimal change to help prevent mistakes on pressing the wrong action and submitting the autofilled action.

Edited November 3, 2021 by Shadowdrake

[Fuzzbucket]

I have NO idea what you mean - can you put up a screenie. I get:

 

 

What's to miss ? This suggests to me that there is an issue for some people and others of us have no idea what that issue is !

 

Maybe when you go for abandon, the name rather than just the code could show on the confirm page ? (NOT testing right now...)

 

 

Edited November 3, 2021 by Fuzzbucket

[dragongrrl]

I find it disappointing that this was ever changed. It was the best protection against abandoning hatchlings we want to keep, and please bring it back.

 

Why would anyone ever want to abandon a named hatchling?

 

Total support.

[MissK.]

Yeah, if the reasoning behind the change was that people didn't know why they couldn't abandon something, surely the obvious solution is to simply explain in the text. That way we would have the security of not abandoning named hatchlings, without it being confusing to people who don't know about that mechanism.

[HeatherMarie]

2 hours ago, MissK. said:

Yeah, if the reasoning behind the change was that people didn't know why they couldn't abandon something, surely the obvious solution is to simply explain in the text. That way we would have the security of not abandoning named hatchlings, without it being confusing to people who don't know about that mechanism.

 

This. It does seem strange that the reaction to 'people don't understand why they can't abandon this thing' was 'change it so they can abandon that thing' rather than 'give an explanation of why they can't'.  Imo it makes more sense to *not* be able to abandon named hatchies (again, consistency, we can't trade them!), and if the only reason that was changed was because of people not understanding 'named' as the reason behind not being abandonable, surely a few simple words to show that you can't abandon named hatchlings would fix that issue? 

[Charu]

This isn’t a mistake I’ve made, but for consistency’s sake, I think this is a solid change. 
 

Curious what happens to the name on a named hatchie if it is abandoned though. Does the name become available again or lost in limbo?

[0x08]

6 hours ago, Charu said:

Curious what happens to the name on a named hatchie if it is abandoned though. Does the name become available again or lost in limbo?

The hatchling becomes unnamed and the name is available again.

[Moriaty]

I didn't know it was ever changed so that you can abandon named hatchlings now! I vaguely think when I started that was a thing....Total support for bringing it back, if you can't teleport named hatchlings there's no reason you can abandon them

 

And I just checked the teleport page - if a blue hover box that explains you need to remove the name first before teleporting can be put over the "Named" text that replaces the checkbox (and thus preventing the player from selecting the hatchi), there's no reason why we can't use the exact same setup for the greyed out abandon text too.

[BringsTheSnow]

On 11/4/2021 at 4:05 AM, Moriaty said:

I didn't know it was ever changed so that you can abandon named hatchlings now! I vaguely think when I started that was a thing....Total support for bringing it back, if you can't teleport named hatchlings there's no reason you can abandon them

 

And I just checked the teleport page - if a blue hover box that explains you need to remove the name first before teleporting can be put over the "Named" text that replaces the checkbox (and thus preventing the player from selecting the hatchi), there's no reason why we can't use the exact same setup for the greyed out abandon text too.

Complete support. Moriarty's suggestion for how to indicate/explain this change is one I would support as well and would make the site more consistent!

 

I was juggling MANY hatchies this past Halloween (at one point I had 24 of them) and definitely abandoned a couple named ones by accident. It was a sad day.

[Ruffledfeathers]

On 11/19/2021 at 10:07 PM, BringsTheSnow said:

I was juggling MANY hatchies this past Halloween (at one point I had 24 of them) and definitely abandoned a couple named ones by accident. It was a sad day.

Its extremely easy to do when you go into ‘hatch catch toss back’ mode. Especially for commons. My support for this continues   

[Shadowdrake]

As someone who did similar I usually hid or put in transfers to avoid that. Doesn't really help when they're all being hatched at the same time though.

Edited November 21, 2021 by Shadowdrake

[camelia2]

Full suport!

It only makes sense ('so attached to this that you named it? Can't trade! Oh, but you can just tie it to a tree right there' tf?)

And support due to personal exp. Last Halloween I accidentally abandoned a Desipis I wanted... granted, shouldn't have perfomed the action at 4am half asleep but....

Let's not forget that devices don't allways function properly or even your finger can slip to another hatchi... you notice the mistake way too late

[Kiyoura]

I'm with everyone else - I thought you couldn't abandon named hatchlings. Why did it change? I agree that named hatchlings should not be abandon-able, just as they are not trade-able.

Edited December 3, 2021 by Kiyoura
typo

[0x08]

A bump, if that's appropriate.