Jump to content

Nashlake

Member
  • Posts

    6
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Nashlake reacted to Spotty in Small rant re: Linus vs NFT's   
    That doesn't make any sense. When you buy DLC or skins it's made specifically for that game. What good would my oblivion horse armour be in payday 2? Or my pubg schoolgirl outfit in civilization VI? There's no way for me to use it in that game. Even with skins like outfits where it might make sense to transfer them over it would still require developers of other games to create that skin/outfit in their game to support it so that it renders on screen in game, which is additional work for which they're not going to be paid for since it was originally purchased for a different game.
    You mention using WoW gold in FFIV... Who would want that? It wouldn't be good for either games economy and games like MMOs wouldn't be fun if you just transferred assets over from a different game.
     
    You don't need NFTs to do this. Steam marketplace already allows selling skins and items to other players. They could make it so you can transfer/sell your games to different people if they really want to, but there's zero incentive for publishers to allow that (they'd rather get a new sale) and honestly I wouldn't want it to be possible to transfer all the games in my library to another account, that would be a wet dream for account hijackers who could empty out steam accounts of all the games in the library.
  2. Agree
    Nashlake reacted to quantum- in This is NOT going Well… Linux Gaming Challenge Pt.2   
    The UX is terrible for the average end-user, but GitHub is not designed to be a way for the average end-user to download software from. Tutorials that claim to be "new-user friendly" need to either stop relying on getting users to download things from GitHub or give a doorstop explanation of git/shell scripts/file permissions. Heck, if enough people want one, I'll write it myself so they can just link to/copy it.
     
    Apparently they fixed this in a recent update.
×