Elvith Ma'for

Former Reddfugee, found a new home on feddit.de. Server errors made me switch to discuss.tchncs.de. Now finally @ home on feddit.org.

Likes music, tech, programming, board games and video games. Oh… and coffee, lots of coffee!

I � Unicode!

  • 14 Posts
  • 1.55K Comments
Joined il y a 2 ans
cake
Cake day: 21 juin 2024

help-circle





  • Hast du schon deine angeschlossen-Fahrkarte, damit du heute Abend mit in den Verein kommen kannst ohne an der Kasse und der Sicherheit ewig anzustehen? Hab gehört, dass dort $Musikgruppe direkt spielt. Die sind gerade voll in Richtung, wenngleich ich die schon etwas zu Hauptstrom finde. Hast du eigentlich heute Mittag die Befähigung von der Formel 1 geschaut? Ich war zu der Zeit ja bei uns auf dem Marktplatz mir die ganzen Veteranen anschauen, die dort ausgestellt waren.



  • My current setup for this:

    I own a domain - say homelab.com - and use it exclusively in my internal network.

    The public DNS records do only resolve to 127.0.0.1 (as my domain holster doesn’t want me to have no A record).

    In my home network I have a pihole running that resolves this domain and it’s subdomains locally (say pihole.homelab.com, proxmox.homelab.com and so on).

    For HTTPs: As this server is not publicly reachable, I use the DNS API of my domain host to get a let’s encrypt certificate with the DNS-01 challenge. That way, the internal systems do not need to be exposed to the internet.

    Edit: Caddy can do DNS-01, but you usually have to compile it yourself to include the plugin for your provider. To circumvent that, I’m just using plain old certbot and told Caddy to use the certs that are already on the machine



  • Bekommst du das einigermaßen flott hin? Egal welche TTL ich einstelle, es dauert über die API immer 15-20 min, bis die Änderung auch wirklich live ist…

    Stört mich bislang nicht wirklich, da mein Haupteinsatzzweck ist, DNS-01 bei Lets encrypt für meinen Home-Server zu machen und der renew eh automatisch läuft, aber der Initiale Deploy dauert halt immer ewig.


  • Then I’m not sure if curl is up to the task in this case - most modern websites are PWAs that dynamically request data from their Backen and display it. Curl just fetches the initial HTML but doesn’t execute the JS and thus might not see the content of the page as it isn’t there yet the moment it gets saved.

    Some PWAs “render” the first page contents in your HTML so that it is included and do not need to be requested.

    Maybe try the alternative frontends if some of them work better? Also remember that feddit.org and many other instances deploy Anubis and might lock you out from making simple requests with curl



  • What about this? This basically forbids you to fork the software if you want to - e.g. because they’re maybe going closed source in a few years?

    You may not use the Software, in whole or in part, to create, distribute, or operate any product, system, or service whose primary function directly overlaps with or replicates the core business purpose of the Product, unless explicitly authorized in writing by fabricators.



  • Elvith Ma'for@feddit.orgtoGames@lemmy.worldBreaking enemy AI?
    link
    fedilink
    English
    arrow-up
    2
    ·
    il y a 8 jours

    For most encounters in the open world that even makes sense. You don’t want enemies chasing players across half of the map. Especially if you can have enemies that are faster than the player. Fence them so that they will eventually give up if a player runs away. This also helps if a player doesn’t want to constantly combat and would have to constantly sneak through the map (or exclusively fast travel).

    But two points to make this less cheeseable:

    1. for bosses - make sure that there are spots that are relatively safe to e.g. craft ammunition, catch a breath, develop a plan, scan its weak spots,… but don’t make it 100% safe. The boss may be able to snipe you from some areas, so you might be moving around some rock to constantly to stay out of line of sight or such. Find an „excuse“ on how to make the whole map accessible to the attacks of the boss and (at least for real bosses) how to lock the player in. Make the auto save before the lock down, not after.

    2. for other enemies: don’t fence them in a specific spot and create an invisible border. Better: define a point on the map as their home. They may chase the player, but randomly decide at which range X±Y% from that point they rather return home. Also randomize the time it takes for them to loose interest in you after loosing LOS. That way it’s not an obvious invisible border you can abuse- more like a zone in which they will probably stop hunting you. Maybe even combine that with other data like- is the player generally sticking around and trying to kite the enemies to some location (and trying to cheese combat/an objective) or is the player just running straight away indicating they stumbled upon the enemy but have no interest in fighting.

    In the end - a game is not realistic but a kind of simulation. Do what looks cool and feels right and is fun. Not what is realistic - if you were to sneak into a camp of the army, they probably won’t stop searching you after a few seconds when you slip around a corner after they saw you…


  • Elvith Ma'for@feddit.orgtoGames@lemmy.worldBreaking enemy AI?
    link
    fedilink
    English
    arrow-up
    3
    ·
    il y a 8 jours

    In Horizon: Zero Dawn you come upon a quarry and a quest asks you to go in and… I can’t remember. Save someone? Check what’s going on? When I stumbled upon this quest, I was severely underpowered and could get that boss down in that quarry.

    But I soon found out that said enemy wasn’t able to pathfind its way to the way leading down to the quarry although it was still considered part of the arena. Also there was much cover there.

    In the end, I stuck to said path, sat behind a rock and just put a fuck ton of arrows onto the boss until all my resources and its healthbar were depleted. Took me way too long, lol.


  • There’s one thing this site gets wrong. And it’s central for their mission to correct that. Because I guess everyone else does get that wrong, too. Very likely including those guys who do the profiling (although their wage probably depends on not realizing that mistake):

    You do not need cookie banners to ask for consent to set a cookie. You are required to ask for consent to process people’s information, to profile them, stalk them, fingerprint them. Cookies are one of the ways to do that. But not the only way.

    This site - as basically every other site using ad providers - did all of this without asking for consent, but was required to ask. At least for visitors from the EU (like me). It didn’t matter that they didn’t use any cookies for it. They need to ask and they need to respect a rejection. It’s also not ok to do it and just say that everyone else does so, too.

    That’s the message that should come across. Not “hey look what we can do without cookies”. It’s “hey, cookies are a scapegoat. We don’t need them. We’d have to ask for consent but since everyone is so preoccupied with cookies, we just didn’t. Like all this ad tech companies spying on you didn’t ask, too. They should be held accountable.”