Jump to content

Yoarii

Member
  • Posts

    272
  • Joined

  • Last visited

Posts posted by Yoarii

  1. On 8/25/2023 at 8:53 PM, Wolfram said:

    I like the concept of DU, the way things are mostly seamless, specially regarding to flight (atmospheric and space), they do have good tech, made by really talented people here.
    The big mistake (that still happens), at least in my point of view, is that while the game was created with the intention of everything being player-made or player-driven, they still keep adding arbitrary limitations to the game, which goes completely against the sandbox concept (sometimes, even the concept of a game, which is being fun).

     

    For example, limitations regarding what's allowed via scripting or building hurt quite a lot, but timers also hurt as well. Plus, some things that would have made the whole experience much nicer haven't been implemented until today.
    Player markets could've been so nice, like, if we could add a Market Pod ourselves to a Container Hub and have a centralized place where we could add buy/sell orders in our construct, with that the number of districts and overall markets could be reduced per planet, which would give players a reason to make connections to get better offers. That's the kind of mechanic that is kind of implemented already, but is restricted and can't be implemented by players in any way. It gets even worse when we don't have reverse dispensers that buy stuff or don't have even the basic QoL to dispensers, which would be allowing to increase number of batch sizes at buy time...

     

    The game idea is good, and I'm sure there's lots of talented people working on it, but sadly, whoever is in charge of making decisions doesn't seem to understand that for emergent gameplay to properly flourish you need to offer players freedom and tools for that...

    This. Absolutely this. ^^

  2. Now that this has been posted to the forum too, I'll just link my original question above, and add this: Please, provide an out-of-game codex. Until such a time that the in-game code editor can measure up to VSCode with Lua plugins, and use of du-luac, most larger projects will be coded outside the game while not even having DU running. You have a perfect place for this - your GitHub repository. You've made a good start with the API mockup, but it needs more work and up-to-date annotations, like in this PR that's been waiting review/approval since Sept 8, 2022.

  3. Just read the devblog in the launcher on changes coming to 1.4. Awesome news, all of it.

     

    Just a small ask, @NQ-Ligo, please document the exact changes to the API so that we can determine what we need to change.

    > We've added a compatibility patch to prevent your existing scripts from breaking.

     

    Could you please elaborate on this a it?

     

    We're all dying to know more about the getInstructionCount and getInstructionLimit functions, could you please let us know more about those too and how they are intended to be used?

     

    Br,

     

    Yoarii

  4. On 3/26/2023 at 3:41 AM, Sethioz said:

    get your software signed by microsoft

    This factually incorrect. Microsoft will never sign your software.

     

    The procedure is to get a Code Signing Certificate from a trusted vendor, then use that to sign your own software. This will make Windows see that there's a valid certificate chain to a common trusted Certificate Authority. It will then show the blue prompt instead of the yellow one when launching the executable.

     

    Even a virus creator can do this, though their certificate would (hopefully) be revoked pretty quick so Windows would once again show the yellow alert, or perhaps something else when it sees the certificate is revoked.

     

    There's no cost to do the actual signing once you have the certificate.

     

    And just to be clear on this point - a digital signature only establishes who signed it (i.e. put their stamp of approval on it), not that it is virus free.

  5. The maintenance unit is not a replacement for the hand-tool. That said, the times are a bit too long and they should really be based on the actual amount that is to be repaired or deconstructed, not on core size imho.

     

    And yes, the "set schematics container" menu needs to be moved from its current place.

  6. Not an actual bug, but some general feedback. The time it takes to repair a ship seems based on core size with a time of 3h for an M-core. That seems very steep. I get it, it is not a replacement for the repair tool, but still. imho the time it takes to repair should be based on the amount of damage that it needs to repair, not a fixed time.

     

    Also, are repair talents taken into consideration when using the maintenance unit to repair a ship?

  7. 6 hours ago, Owl_Superb said:

    Its simply lazy for developers to NOT program everything into the software they are developing

     

    Poor devs, always gets the blame. I'd like to point out that it often isn't up to the devs to prioritize what goes into the game.

    I do agree that the game itself should enforce rules when it is possible.

×
×
  • Create New...