• 0 Posts
  • 17 Comments
Joined 5 months ago
cake
Cake day: October 16th, 2025

help-circle


  • I’m guessing you’re referring to Starfinder: Afterlight. I’ll look into it once it’s released.

    As for the action point system, DnD’s action system was one of my favorite parts about it. Most action point based systems I’ve seen so far have balancing issues that seem difficult to get rid of.

    For example in Fallout going from 9 AP to 10 AP effectively doubles your damage output, because it lets you attack twice per turn, so anything less than 10 agility is just bad. In Divinity I always felt bad about having to waste AP on movement on melee characters, whereas ranged characters can spend almost all their AP on attacking.

    DnD’s system on the other hand is less flexible, but more consistent in that I rarely get into a situation where I can’t do anything meaningful on my turn, because I had to spend all my AP on movement.


  • I appreciate the detailed response.

    I agree that individual classes in BG3 could offer more options. A lot of levelups are just “you have this passive now, period”, but I found multiclassing to fix that, by offering more interesting choices. Finding the right breakpoints for how much to invest into each class to get the most benefit was fun for me. I generally enjoy the min-maxing aspect of RPGs more than the roleplaying.

    Most of your criticism seems to come from comparing it to other TTRPGs and I get that not enjoying DnD in TT will affect your enjoyment of a game like BG3, but I’m looking at this from a CRPG players perspective.

    My comparisons are classic Fallout, Divinity, Rogue Trader, VtM - Bloodlines, Cyberpunk, etc. Compared to those games I enjoyed DnD as a system the most, but I will probably give Owlcats Pathfinder games a chance.


  • I keep seeing this sentiment and I just don’t get it. From the perspective of someone who has never played a TTRPG and whose only experience with 5e is BG3, it is an incredible system compared to other CRPGs I’ve played.

    It is simple enough to get into quickly and complex enough to remain interesting for hundreds of hours. Small numbers + simple math + transparent formulas make it very easy to understand what is happening why and how build decisions influence combat.

    Meanwhile in Rogue Trader, I barely understand what any of the stats actually do or how damage is calculated. How much more damage am I going to do by putting point into offensive stats? How do defensive stats influence the damage received? On top of that every levelup presents you with dozens of options for traits for every single character in your party. How am i supposed to make an informed decision here? Just reading through them all would probably take an hour. I ended up just using build guides and getting bored because just picking the options someone else tells you to is not very exciting. The Pathfinder games are much the same in complexity from what I’ve seen.

    If someone has some tips to get into those systems I’d appreciate it. I’d like to get into Pathfinder/Rogue Trader, but it just looks like way to much work until you get to the fun part.






  • From PLMs GitHub:

    Plasma Login is in a prototype state and is not considered ready for real-world usage.

    I just tried it out anyway, because SDDM sucks. PLM no longer uses the lowest common resolution for all displays and HDR works about as well as it does in plasma (sometimes I get a black screen and have to turn the display off and on). Still better than SDDM. It also integrates with KDEs system settings so it’s easy to setup.

    Auto-login does not work however, so I’ll be sticking with SDDM for now, but I’m looking forward to the stable release.




  • I’ve never used bcachefs so no help from me there.

    /boot/efi is no longer considered an appropriate mount point

    It’s not typical, but it should still work. systemd-boot even looks for the ESP there by default among /boot and /efi
    Personally I use /efi.

    just create a EFI partition and mount it /efi and let the OS put /boot inside the root partition if it needs it., then throw a UKI on /boot/efi/EFI/Linux

    If I’m reading this correctly you mounted the ESP to /efi and then put the UKI in /boot/efi anyway. It needs to be on the ESP.
    My /etc/mkinitcpio.d/linux.preset looks like this, if it helps. If you were to use /boot/efi for the ESP you would have to change the paths here.

    /etc/mkinitcpio.d/linux.preset
    # mkinitcpio preset file for the 'linux' package
    
    #ALL_config="/etc/mkinitcpio.conf"
    ALL_kver="/boot/vmlinuz-linux"
    
    PRESETS=('default' 'fallback')
    
    #default_config="/etc/mkinitcpio.conf"
    #default_image="/boot/initramfs-linux.img"
    default_uki="/efi/EFI/Linux/arch-linux.efi"
    #default_options="--splash /usr/share/systemd/bootctl/splash-arch.bmp"
    
    #fallback_config="/etc/mkinitcpio.conf"
    #fallback_image="/boot/initramfs-linux-fallback.img"
    fallback_uki="/efi/EFI/Linux/arch-linux-fallback.efi"
    fallback_options="-S autodetect"
    

    its possible that UKI, systemd-boot, bcachefs, and the /efi mountpoint are not a great mix

    I don’t see the point of systemd-boot with UKIs. All it does is chain-load the EFI boot stub in the UKI anyway. I just used efibootmgr to create an entry in the UEFI which boots the UKI directly.