PC 1st Horde Night, first time in v2.0...

WarMongerian

Refugee
Hi, just wanted to stop by and give a "State of the Union" kinda thing.

My friend and I got v2.0 friday night, and started our current game then.

Right now we have reached day 7, 2103 hrs.

Neither of us has died (yet), but that will soon end.

The way Armor books drop has changed, and we are both wearing primitive armor for Horde night. If I had not spent day 7 scouting, we would not have a cement mixer, but as it is, we just have one Forge, one Workbench, and (just now) a pair of cement mixers. No cement upgrades have been made as of yet, so Cobblestone is all we have.

I hate new rules, and I hate new maps, and I especially hate both coming back to back. This Horde Night makes me want to just start a new game, where we at least know a bit about how v2.0 works, and where things are at on the map, so that we can make a better shot at a proper Horde Night.

Some things:
Spawn near a friend seems broken (badly). Used it for the first time this game, and it spawned me 1.2 kilometers away from my friend. So much for spawning near a friend. Back pre- v1.0, I had the husband and wife team join me in Navezone, they spawned in within about 2 hundred meters of each other, I spawned in over two kilometers away, far to the East. Result, they both died, repeatedly, before I could get to them.

The next game we played, I deleted all but one spawn point from that map, and problems were solved! Going forward, spawn points will be edited to just "One Ring to rule them all" kinda thing, and we no longer have to pay homage to the scatter them to the 4 winds algorithm.

v2.0 broke the trees?
I have always preferred to work in the shade, but the only way I could make that happen, on those painfully bright daytimes, was to plant trees in a block of topsoil, atop a pillar, and voila, an instant ability to "Fight in the shade" was born. In v2.0, here is where I tried this, and twice I had to remove the trees. Didn't think about taking a screen shot with the misplaced trees in it, but will do so if my friend and I continue this playthrough. Here is where 2 of them had been planted (twice), and they grew wrong both times.1st v2.0 Horde Night.jpg
Trader Rekt-tum can be seen in the background, and the trees used to be able to grow on a single block of topsoil, seen at the top of the pillars. Did this change recently/in v2.0? As late as last friday morning, back in v1.4, this was indeed working. Bug or change?
 
Ok, I didn't get my friend to agree to just restart, but instead, he offered to turn Horde Night off, until we get a chance to re-learn the game with all that v2.0 has changed

Hence, nothing happened, and nothing to report... :)
 
So, I went and died. While it was technically a Dire Wolf that killed m, it was the *(%*(%^^ left windows key that immobilized me so I couldn't move. How do I permanently disable that 🤬🤬🤬🤬 windows key, so this can never happen again?

Thanks in advance for any help with this issue.
 
How do I permanently disable that 🤬🤬🤬🤬 windows key, so this can never happen again?
Just pull it out.

While that sounds trollish, it actually works. Remove the keycap, leave the key itself functional. A whole lot less misclicks, as it'll be deeper than the others around it and a completely different feel. Given your keyboard is of the type where it'll still function fine without the cap ofc ;)
 
So, I went and died. While it was technically a Dire Wolf that killed m, it was the *(%*(%^^ left windows key that immobilized me so I couldn't move. How do I permanently disable that 🤬🤬🤬🤬 windows key, so this can never happen again?

Thanks in advance for any help with this issue.

Just pull it out.

While that sounds trollish, it actually works. Remove the keycap, leave the key itself functional. A whole lot less misclicks, as it'll be deeper than the others around it and a completely different feel. Given your keyboard is of the type where it'll still function fine without the cap ofc ;)
Pulling it out was my first thought, but then glue came quickly after. 😁

There are probably key mapping utilities as well that you could use to disable that key entirely if you don't want to remove it. Some keyboards aren't designed to let you remove keys.
 
I remember something called "winkey assassin", but don't remember if I previously used that program on this or an earlier computer. Thanks everyone for the help. Hope I can solve this without open keyboard surgery, although, it did kill me, again....
 
Ok, two things now:
Rage quit.jpg
Ever since I rage quit because of the 🤬🤬🤬🤬 win-blows key killing me, my friends game has blocked me three times. First time I just tried again, second time I quit and exited 7DTD, third time I restarted my computer, and the above is what I got.

Second thing, is there a way, somewhere in the keybindings, where I can have 7DTD just disable the win-blows key, while the game program is running? That would allow me to solve the issue, without having to rip the physical key off my keyboard.
 
Second thing, is there a way, somewhere in the keybindings, where I can have 7DTD just disable the win-blows key, while the game program is running? That would allow me to solve the issue, without having to rip the physical key off my keyboard.
No. It is a Windows function so isn't a have keybinding. As theFlu said, you will need another utility to change it.
 
Back
Top