Things I had to do in order to install a minecraft server

[laxla@tech.lgbt]

Things I had to do in order to install a minecraft server:

• Find a DVI-to-HDMI cable for a non-working display
• Accidentally disconnect the display, now it doesn't work
• Realize duplicate works but extend doesn't
• Mess around with primary display settings for an hour
• Get extend to work with 1060p 60.020hz
• Use suspicious software to force windows to use 1080p 60.020hz
• Decide a frame per 10 seconds (the rest is all black) isn't enough
• Accidentally change the screen to 50hz, and having it work
• Launch Minecraft, there are tons of artifacts
• Use the original DVI cable (works perfectly)
• Find a keyboard and a mouse
• Install adrenaline and some other mods, have said other mods not work
• Realize the latest stable adrenaline version is 1.21.1 and the mods I installed are version 1.21.3
• Go back to .1
• It works, 2ms ping time on LAN.

That was five hours.

[laxla@tech.lgbt]

The cursed part is my (linux) laptop is connected directly to the router, but the (windows, btw) server is connected via ethernet to a wireless access point (which expands the router's radius).

Wait, how tf does the computer get internet from the wireless AP? The access point doesn't even have a way to input the password, and the server thinks it's a regular ethernet connection.

How does the server connect to the router without a password? Wtf???

[laxla@tech.lgbt]

(if it wasn't clear, the AP is completely wireless, and has an ethernet out)