Jump to content

yamamushi

Alpha Team Vanguard
  • Posts

    1560
  • Joined

  • Last visited

Everything posted by yamamushi

  1. "Death" isn't implemented yet, so nobody really knows. From previous NQ comments, it sounds like anything in your inventory would be dropped when you die, but your constructs aren't going to simply disappear because you die. Perhaps there might be a "safe space" in your inventory, a small section of inventory that doesn't get dropped when you die, but I don't think anything has been said about that so it's just a guess at this point. Constructs are always in the world though, even when you log out. They're probably not going to vanish because you die, but you'll still have to make your way back to them (unless you have a respawn node on them or nearby). If I had to bet on it, I don't think you'll lose money when you die either. As far as skills go, that's anyone's guess at this point.
  2. When you find the solution to something that has underpinned all conversations online since the dawn of the internet please let us know.
  3. Yes, you will get the full game. The pledges come with "DAC's" which can be used to pay for the subscription after release (There is no subscription fee during Alpha/Beta). The game will be "free" with a monthly subscription fee. The roadmap for releases can be seen here: https://www.dualthegame.com/en/news/2018/08/08/release-roadmap-alpha-launch-announcement/ Though there are no exact dates given.
  4. Not everyone is getting day 1 alpha 1 access. Instead, access is being opened slowly by backer tier. On the 29th (today) Sponsor Supporters will get access, it is likely (but not guaranteed) that on the 6th of December that Silver founders will get access, but that also depends on when you bought your Kickstarter pack. Were you backer #100 or backer #5000, basically. So there is no download link available right now for you, but you will be getting an email probably in the next 1-3 weeks notifying you that your access is ready. Don't worry, it will be here before you know it.
  5. I put together the audio fx and this video to create a rough version of my idea of what a sandstorm in Dual Universe at a spaceport in the desert would be like, alarms blaring for people to take cover, departures and landings restricted by the port authority, visibility extremely limited...
  6. Contact support @ https://support.dualthegame.com/hc/en-us , and include all of the relevant info. They usually respond within a day. If you pledged with gold or higher, I don't doubt they'll have you ready for the next testing session.
  7. I think it would be very useful to have a way of attaching descriptions and stats to blueprints.
  8. I don't think very many games are going to win over the die-hard Eve vets, even Dual Universe. While they share similarities in design philosophy, the gameplay of both games is drastically different. There will be plenty of ex-Eve players coming into DU, but on the flipside, many of those vets will stay with Eve till the bitter end.
  9. I honestly don't know what else I could add to this topic other than making a video describing every line of the bot source code one by one. The same thing is being rehashed over and over here to the point where it's obvious that no matter what is said that people are going to take issue with it. If you want links to the source code: https://github.com/yamamushi/du-discordbot/blob/master/backer.go https://github.com/yamamushi/du-discordbot/blob/master/backer_handler.go Otherwise, I really don't know what else I can add to this conversation. I've explained what the bot does, I've explained why it does it, there's simply nothing else for me to cover. The bot has been working for quite some time now and nobody ever complained about it before, it's just that when Discord went official that people started to freak out about it. It's not new, it's been serving its purpose quite well. If you want NQ to run it, I'm not sure what that is going to change because the bot is still going to be running off the same source code that I wrote, you're effectively just asking NQ to put even more work on themselves to support it going forward. I'm sure they'd do it if enough people demanded it, but it really wouldn't change much other than who owns the server the container runs on. As for the bot collecting data, the bot doesn't collect anything that you don't specifically allow it to. It's not going to go automatically scraping user accounts on Discord, you have to manually run the command and specifically give it your forum profile to gather your backer status (or pre-alpha status if you have that disabled). Anyone can disable their backer public status, the only thing the bot needs to verify is whether or not you have pre-alpha status, which is something that you can't edit on your profile. The bot isn't just scraping the forums randomly looking for accounts to link up, you have to manually run the verification process, by which you implicitly agree to the collection of your publicly available information in the first place.
  10. The information the bot gathers is already public on your profile, you are already sharing all of it, and there is even more info on your public profile available that the bot isn't gathering. You don't need to share any of it, you can disable displaying your backer role even and the auth will still work. Using the auth is not a requirement to use Discord, it's a requirement to use the NDA channels. If you don't want to participate in them, nobody is making you. The irony here is that there are probably services already collecting and aggregating yours and everyone else's profile information and aren't being transparent about it at all.
  11. I also want to clarify, there are things that I (and others on the Discord Staff) have been aware of in the works that we simply aren't allowed to discuss. Ie, for the Discord server, the process of making it official and handing it over to NQ has been going on for several months, it wasn't an overnight quick decision by any means. We couldn't publicly announce that for many reasons. There were many questions about the auth process that I could have answered with "Well an NQ API is in the works" to assuage some fears, but I didn't want to break any confidentiality by saying that either. I know there are many in the community that really don't like me at all, but I would not be where I am in my career if I made a habit of collecting data for illicit purposes or breaking confidentiality agreements openly. I'm never going to win those people over, but at least I can try to be as transparent as possible to the rest of you to show that I'm acting in good faith here with my contributions.
  12. Of course, that is always a possibility, we have to take that into account as well. It would mean losing a lot of content to just remove the channels. Plus what's under NDA is always going to be under NDA. As long as nobody gets too upset about the view that it's a special club or anything I don't see why we'd need to remove it completely. We need to clarify from NQ whether Alpha members should have access to those channels or not as well, but will likely happen is a shuffling of channel names for consistency.
  13. When the NDA drops then there won't really be a need to authenticate with it, we can close (or archive) the NDA channels, and nobody will have to use it. If they want to get backer roles for cosmetic purposes they'll still be able to, but otherwise, there won't be a need for it. As for the data, that is going to stay in the database because it is what ties backer roles to users. Even for non-NDA purposes, such as Iron / Bronze / etc backers, or supporter pack purchasers (non-patron packs), or ATV. The database stores: Discord user ID Forum profile link Backer Status (Gold/Silver/Ruby/Whatever) ATV member (true or false) Pre-Alpha Access (true or false) Validated successfully (true or false) - This is used to track whether a user has completed the auth process or not When the API becomes available, I will adjust the database to only keep the data that the API provides. You don't need to have your backer status made public to be validated either, as many didn't want to have to do that. The forums will show if you have pre-alpha access without needing to display what backer level you have. There are many in Discord who have access to the NDA channels while also hiding their backer level. The bot is used for other things besides authentication, it provides utilities for NDA members which will be useful after the NDA drops too, it provides a live forum feed, a Reddit feed, a news feed for Dual Universe content (Youtube, Twitter, DevBlog, etc), it provides reactions (the Nyzaltar, Nomad, JC, etc reactions), it provides a server status utility and many more things. I don't see a good reason to remove it completely when the NDA drops.
  14. Roles don't stay with users when they leave a Discord, and it doesn't actually store users so if they come back they'd need to re-auth. It won't give them roles automatically just for re-joining ?. One of the things I am adding tonight is to adjust the counting mechanism when a user leaves, but that's just an int value that gets increased when a user auths or decreased when they have their auth reset. The authbot is different from the dual universe discord bot, which does store user Discord ID's to sync them (many Discord bots do this), but even for that there is a mechanism to remove user roles from the DB when they leave automatically, and that is only applicable for the DU Discord. I guess I should clarify because there is a bit of confusion going around about what Authbot provides... - Authbot doesn't provide a mechanism for users to link their accounts, that is only done through the official Discord so that NQ can moderate if necessary. - Authbot doesn't apply or remove roles automatically, that is still a manual process that is initiated by running the auth or reset commands. - Authbot doesn't create channels or assign permissions, Discord owners/moderators still need to set those up for their own application. - All Authbot does is synchronize the role names that users have from the official Discord into other Discords, none of the permissions are applied, only the role names themselves. Discords still have to actually assign unique permissions as they see fit to their own needs. - Authbot is not storing user details, it's pulling them from DU-DiscordBot. Hence why the actual linking of accounts is done through the official Discord, to give NQ the ability to revoke permissions if necessary (perhaps if someone were removed from the pre-alpha for breaking the NDA, or something along those lines). As for giving API access to the data, I considered it, but I figured it would make people too uneasy if those details were accessible. None of this will be necessary once the NDA drops anyways, all it would be good for is to give people backer roles, which I really doubt people are going to care about once the NDA drops. tl;dr - Authbot looks up a Discord user ID in the database and reads what backer level they have, that's all.
  15. Is everyone who isn't going to use it going to post about it? ? Meanwhile, almost 500 people (a quarter of the official Discord) are using the auth system now without issue, and it is in use on several Discord servers: I am pushing out some feature updates for Discord owners tonight as well. Chances are they won't roll out until the late AM central US time, so keep an eye out on Github for the changelog ?
  16. I don't know why paypal is having issues for you, but I'm guessing the reason you had login issues was that the usernames on the homepage are case-sensitive compared to the forums
  17. You can ignore them, but you can't block them on the forums: https://board.dualthegame.com/index.php?/ignore/
  18. It doesn't hurt my feelings if people don't want to use the auth system, it's just more conversations they are excluding themselves from in the Official Discord at this point.
  19. I will let the NQ news speak for itself: https://www.dualthegame.com/en/news/2018/09/10/dual-universe-official-discord-server/
  20. The operation of the official discord server was approved before being handed over, it was done with the agreement that nothing would be changing about the day to day operation or the functionality of the bots or auth process. As I said in a previous comment, it would soon become apparent why this is the most trusted authorization process for Discord. It's not like this stuff is closed source, and I have always been willing to let people contribute to it, just nobody has ever taken the initiative to submit code for it, and up till now, it has only been me working on the bots.
×
×
  • Create New...