@ZealHunter@ghekor@daiyuwu Yes, two different "devs" making plugins. CS+ dev Icarus has vibed it to hell and back not subtlely. Proteus is all vibed, again, would not trust it near mods considering it already has basic issues with gobbling ram and leaking.
@ghekor@ZealHunter@daiyuwu The last update he pretty much went mask off and put the vibe coded stuff front and center. Even the layout is based on the "new" features ai coding can do with "translating" html dummy files. But it's well known in the plugin dev scene it was always vibed.
@ghekor@ZealHunter@daiyuwu It’s both this and Proteus that are vibed to bell and back unfortunately. CS+ creator even hid an issue with somebody breaking it down to try to hide it.
@Lunarianlight@roegamaniac That’s not complete, quite literally people who make punish plugins (who do test boundaries of what gets accounts screwed) can verify the tons of safety checks for movement in HoH and similar. No idea what you’re posting a paragraph for when you’re unsure yourself.
@Lunarianlight@roegamaniac For whatever reason, HoH has some much more severe movement checks for going out of bounds. It's unclear why they don't apply this elsewhere other than fear of people with extreme ping triggering it (they won't).
@Lunarianlight@roegamaniac Was talking about your saying weird shit about worshipping SE when i pointed out what they will/won't do. Didn't say I wanted nothing, said moderation is what's feasible here since anti-cheat won't fix it + cause problems. They need moderation + same thing HoH has for movement.
@Scrxtchy@roegamaniac Yeah that's not main repo. Again, as mentioned above it's mmo-minion or cheat engine. Point stands regardless moderation's the only thing they're willing to do since anti-cheat basically kills your linux/mac client base, suck to deal with on consoles on top of that.
@Lunarianlight@roegamaniac Not the kind for pvp botting that's easily findable/searchable. idk what your deal is but anti-cheat is something they've gone on record not saying they'd implement. So the only option they're willing to do is moderation.
@solona_xiv You can stop making AI slop any time. Yours came out a few days after another credit started updating their same years old tooling too that they’re posting everywhere, just by chance? https://t.co/9f2eis1bP1 While this author makes questionable decisions it’s not ai slop so far.
@aokatabito@Dubsys@MiniatureMoosey You can read right? It’s not my job to point out what the vibe coded should fix, be patient instead of eating the ai boot.
@aokatabito@wuppyog@MiniatureMoosey Read the current C+ build where it says it’s not using that saving system. Mounts are fucked in that version of C+ and at this point you’re just fishing for shit the vibe coder to fix, why the fuck would anyone help with that moron?
@aokatabito@wuppyog@MiniatureMoosey You also taking the vibe coder guy running it through Claude as any indication of safety is the dumbest thing so far.
@aokatabito@wuppyog@MiniatureMoosey Sorry you don’t know how plugins work or how to read the source. Saving system it has is different but writes to the same file, it doesn’t touch the right things for players in client structs, will fuck up mount scaling. And again, vibe coded by somebody who can’t fucking pull.
@Dubsys@MiniatureMoosey Yes I can see the source, and it fucks up profiles because they didn’t do ANY of the changes required in client structs. Fucks up mount scaling, doesn’t touch the character correctly, uses a saving system different than c+ is going to use which will in fact fuck it up.
@Dubsys@MiniatureMoosey Way to expose yourself as somebody who doesn't know what access you give plugins. Plus this C+ update from the vibe coder will fuck with profiles, aka your actual saves in C+. Risking that over waiting for updates is pretty stupid.