A list of performance-enhancing mods for 1.18.x forge/fabric versions.
Any suggestions/complaints?
Join our discord or use the gist comments.
A list of performance-enhancing mods for 1.18.x forge/fabric versions.
Any suggestions/complaints?
Join our discord or use the gist comments.
#!/usr/bin/bash -xe | |
cat <<EOF > "${HOME}/.config/systemd/user/zoom.slice" | |
[Slice] | |
AllowedCPUs=0-4 | |
MemoryHigh=6G | |
EOF | |
cat /usr/share/applications/Zoom.desktop | sed -E 's#^(Exec=).*$#Exec=/usr/bin/systemd-run --user --slice=zoom.slice /opt/zoom/ZoomLauncher#' > "${HOME}/.local/share/applications/Zoom.desktop" |
agent_publickey = 3059301306072a8648ce3d020106082a8648ce3d03010703420004f2b81b1902a771c8c24f09c6bd8be647d33bd139269856418a42c5a78343d943a03ac2173529a816f797a803563de6ecdd25572ce09af8c081c02303bac0c4d3 | |
agent_publickey_hash = 525f76180e55012341ffe12bcfb5587adad1b920 | |
agent_publickey_hash_result = not found | |
agent_publickey_hash_type = web:ecdsa | |
agent_type = browser_computer | |
alert_id = 9598 | |
api_call_datetime = 2019-12-16 15:24:42.595 | |
api_key = fioxxxxxxxxxx370 | |
api_site_id = api101.qa2.sac. | |
api_type = session-query |
from shodan import Shodan | |
api = Shodan('API-KEY') | |
results = api.search('isp:"ThreatMetrix Inc." port:443 Bad Request') | |
for banner in results['matches']: | |
# Only care about services that use SSL | |
if 'ssl' in banner: | |
print(banner['ssl']['cert']['subject']['CN']) |
Fabric is the "modern" Minecraft modding software that is very modular.
We use Fabric in this guide so install it by going to https://fabricmc.net/use/ Download the .jar or .exe and run it.
Below is a list of performance and utility mods to make your Minecraft experience better and most importantly smooth.
The list is in order of most importance and they all work together including what they do with why to use them.
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
#!/bin/bash | |
tunservers="Hong_Kong,_HK:216.218.221.6 Singapore,_SG:216.218.221.42 Tokyo,_JP:74.82.46.6 Amsterdam,_NL:216.66.84.46 Berlin,_DE:216.66.86.114 Budapest,_HU:216.66.87.14 Frankfurt,_DE:216.66.80.30 London,_UK:216.66.80.26 Paris,_FR:216.66.84.42 Prague,_CZ:216.66.86.122 Stockholm,_SE:216.66.80.90 Warsaw,_PL:216.66.80.162 Zurich,_CH:216.66.80.98 Ashburn,_VA,_US:216.66.22.2 Chicago,_IL,_US:184.105.253.14 Dallas,_TX,_US:184.105.253.10 Denver,_CO,_US:184.105.250.46 Fremont,_CA,_US:72.52.104.74 Fremont,_CA,_US:64.62.134.130 Kansas_City,_MO,_US:216.66.77.230 Los_Angeles,_CA,_US:66.220.18.42 Miami,_FL,_US:209.51.161.58 New_York,_NY,_US:209.51.161.14 Seattle,_WA,_US:216.218.226.238 Toronto,_ON,_CA:216.66.38.58 Winnipeg,_MB,_CA:184.105.255.26" | |
tunserver_array=($tunservers) | |
tunserver_count=${#tunserver_array[@]} | |
i=1 | |
( | |
echo -e "Location\tIP\tmin\tavg\tmax\tmdev" | |
( |