ID:2949753
 
Applies to:DM Language
Status: Open

Issue hasn't been assigned a status value.
Can we get a built in Bumped() proc that is called on the object that is bumped into?

I'm sure this has been requested before, but I can't for the life of me find the post on the googles.
One could say that you...

Bumped this feature request.
https://www.byond.com/forum/post/2403072

Nadrew marked it as redundant ¯\_('-')_/¯
Hopefully Lummox sees the light
Bleck, in no way redundant. Reciprocal calls and not relying on softcode and ..() returns is obviously important for an easy to use game engine. We shouldn't be relying on softcode for something so simple, basic and important.

It would be the same logic of, why have Bump, we can just deal with Cross and soft code the bump when it fails in Cross. Problem solved, why bother.

You bother because we also are not making games in assembly, just because you can do it with effort doesnt mean it isnt logical for it to be baked in.
The reason simple reciprocal hooks like this are important just comes down to the community as a whole not constantly having to share a whole base-level override with someone else in order to get a common pattern working.

I've written out code hundreds of times, sharing with other users how to build a Bumped() response into their game, and there are a lot of shitty gotchas that can prevent it from working just because someone somewhere in your code forgot a ..().

Not having common-sense reciprocals like this leads to just poor outcomes and developer frustration.
Agree. Its like when people poo-poo'd official vectors and pixlocs because you can do it in soft-code. The foundation needs to be complete and approachable.