• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle








  • BleakBluets@lemmy.worldtoPatient Gamers@sh.itjust.worksOn Fast-Travel in video games
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    5 months ago

    I would rarely choose to fast travel if I had engaging and interesting means of travel like bunny hopping and strafe jumping in Quake, or wall-riding like Lucio in Overwatch. This assumes the world was built to facilitate this kind of movement and there were challenging obsticles, enemies, treasures, secrets, and other points of interest scattered among a variety of paths for the player to choose. Obviously much easier said than done; Super Mario Oddessy and Sonic Frontiers tried to do something like this on a smaller scale (relative to the large open worlds of other games) with varying levels of success.

    Exploration was fun in the BotW and TotK Zelda games, but I found myself relying on fast travel by the midpoint of each of those entries because the enemy camps and treasures just weren’t worth the time nor effort. Dashing on horses wasn’t mechanically deep enough and Ultra Handing vehicles was either too inconvient or resulted in “path of least resistance” designs that led me to hoverbike to new locations very cheaply and easily.




  • I thought decompiling with Ghidra was okay too, I may have just misunderstood the wiki article when I double checked post-commenting and crossed out my comment. I’m not entirely sure what comprises “proprietary techniques”. But I’m pretty sure that documentation needs to be provided in order to keep it on the legal side. Hopefully this project can come back and recieve continued support ala similar decomp projects.


  • I think the binary they distributed still included the art and sound assets; the users didn’t have to provide their own. And “clean-room” design is more than just providing source code. You need to provide a “paper trial” / commit history and documentation of how the final code was derived from the original code. My mistake, clean room is when you recreate the project without reading the original/compiled code at all. Specifications are written based on observed behaviors of the original user-facing program and new code is written according to that.


  • Maybe I’m wrong, but wasn’t there a way to release this while avoiding the issue of copyright? My understanding is that publishing “clean-room” reverse engineered code is legal. The graphics and sound can’t be redistributed, but you can distribute a tool to rip those assests from a ROM and let the users provide a ROM they own. This is what Ship of Harkinian does no?