And the gold star goes to @thefrog !! 
His file was the right one, sorry @xircon but modifying the one you suggested did nothing.
Phew, well things are finally back to normal so thank you so so so so much everyone for your help!!! 
Now I don’t know about you, but I’ve had way more then enough excitement for one day, so I’m just gonna watch a movie then go to bed.
Night everyone, sleep tight, don’t let the penguin bugs bite. 
Xircon’s changes will take effect the next time grub or systemd-boot updates
Oh, good to know, thank you. Well I modified both of them anyway, so I should be set for any scenario I think/hope…
Morning everyone,
So, brand new day, more energy and all that, and in the spirit of:
Would anyone care to take a stab of explaining in a newb friendly manner why all this happened? I mean since I edited fstab correctly from the get go, why did I have to go through all this? 
And even if you have a good explanation for why it happend, why the hell was that resume command for the broken uuid present twice!!!.. 
I googled the terms systemd, dracut and grub and just finished reading the wikis and while I learned some interesting stuff(personally the fact that even in 2024 the sectors for booting are still measured in bytes was a revelation 
) and I understand now what they do, more or less, it still didn’t help to explain why/how this happened.
Thank you.
Your mistake was in reformatting/remaking your swap partition in the first place. When installing other distros (which I assume you did, not scrolling back to see), don’t let it remake swap.
Uuum, no, I didn’t do anything like that.
This all stemmed from the fact that(according to my research) the first thing root does whenever it even looks like it’s running out of resources is to kill easyeffects.
And for example in this new game I started playing Robocop Rogue City every few minutes easyeffects gets killed and I have to alt+tab and open it again, then go back to the game, rinse and repeat until you go crazy. 
So I took a look around and determined that the only resource it could be running out of was the swap, as everything else(cpu, ram, etc.) looked fine to me.
So that is when I deleted my tiny 2GB swap partition that I created when I installed Eos and created a new almost 20GB one. Hopefully that will solve my problem, remains to be seen when I start playing in a couple of hours… 
Ok, then either your mistake was changing your mind about swap space, or not editing in the two places required before rebooting.
I recommend swap files, you don’t have to go through this as you do with swap partitions.
I see, well maybe it’s my fault for using the wrong search terms or something(like I said still new to linux) because what I found on the net nobody mentioned anything about editing those boot files. All they talked about was fstab… 
I seem to recall having gone through something similar myself (and I have always had multiple distros installed, ie reformatted swap) and not found anything about the kernel cmd line stuff (which was your stumbling block). Apparently, it hasn’t gotten any better documented.
Ohhh, that actually makes me feel better that I’m not the only one, thanks. 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.