44
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jan 2024
44 points (100.0% liked)
PC Gaming
8505 readers
529 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 1 year ago
MODERATORS
I'll consider the possibility that the engine is blameless when I see two Unreal Engine games that do it well, hinting that it's not unreasonably difficult. Sometimes a tool just doesn't work well for certain uses. That could be due to a design that tries and fails, or one that doesn't try at all and lacks a good foothold for a custom approach.
In any case, my comment is not about one specific issue. Thus the words "for example". The point is that what GGP said was obvious is in fact not obvious. Blizzard might very well have passed on that engine because of limitations they found, regardless of whether they detailed them publicly.
It doesn't matter if you see it in games, it's not a part of the engine. There's no built in functionality for ledge grabbing and climbing, that is 100% game logic built on top of the engine.