Dev Tracker: Discussion (Old)

[Kincard]

Does that actually work? When you trade the assaults ledgers you need to open the chest and wait it to fade before you're allowed to trade it. Always wondered why they made it like that since it wastes like 15 seconds, but maybe it was done specifically to safeguard against tools like that.

[Cairthenn]

I haven't intentionally opened an assault box since (probably) 2009, and I finished both Yagrush and Ryunohige this year. I have absolutely no idea what you are talking about.

[Churchill]

Fun fact, if you are derping in ZR (or others and don't want to waste a farming run going on the wrong side) and hit the wrong porter, ese can allow you to still pop a socket NM or slot assuming you can make it over to that side of the map.

[Kaisha]

Nah, it's clientside to view the post, but actually trading the thing could be an offense... not that anyone would be able to tell (or care) to report you anyways, lol.

Is ASE smart enough to prevent your client from reporting that you're looking at it?

[Asymptotic]

I haven't intentionally opened an assault box since (probably) 2009, and I finished both Yagrush and Ryunohige this year. I have absolutely no idea what you are talking about.

I was wondering why I was having issues trading my journals when we were doing Assaults the other day. I open the boxes just because, I'll trade my journals first from now on.

[Asymptotic]

Is ASE smart enough to prevent your client from reporting that you're looking at it?

The answer is technically "no." I can't really go into specifics, but your current target is reported to the server and therefore it's possible for it to be logged and/or detected.

[Kincard]

I was wondering why I was having issues trading my journals when we were doing Assaults the other day. I open the boxes just because, I'll trade my journals first from now on.

Same here, when I first started I always noticed that the rune never spit my journal back at me until the chest had faded so I just assumed that you had to open it. That's a damn weird glitch/feature though, I can't imagine what kind of spaghetti coding it would take to make one NPC's status make another NPC not function properly.

[Dotsudoku]

I haven't intentionally opened an assault box since (probably) 2009, and I finished both Yagrush and Ryunohige this year. I have absolutely no idea what you are talking about.

That's because I was always the one getting hit with the delay

[Sho]

Is ASE smart enough to prevent your client from reporting that you're looking at it?

It is not. >_>

Just about every action while not in a "maint." mode is logged to the server.

[Obsidian]

Fun fact, if you are derping in ZR (or others and don't want to waste a farming run going on the wrong side) and hit the wrong porter, ese can allow you to still pop a socket NM or slot assuming you can make it over to that side of the map.

I'd be willing to bet anyone using ASE does not have an aversion to clipping through walls. Popping that mob probably wouldn't be too smart though. That's like talking to the invisible moogles in Bastok Mines.

[NynJa]

Implying most GMs these days know how salvage works...

[Obsidian]

I can't help but feel that interacting with something that's been set invisible raises a flag on the server. It would be pretty dumb to never notify yourself when something odd like that happens.

[Byrthnoth]

Given a few weeks with nothing else to do, I'm fairly confident that I could ban many people for TOS violations using only data that's already reported to the server with a minimum of innocent casualties. You could figure out everything from flee hacking to AH botting to shit like this by doing statistics on server requests from individual characters. For instance:
1) You could ban everyone that trades a book to the assault exit in under a minute. Minimum of innocent casualties, and you get the people that cheated. SE's servers are almost certainly involved in that transaction and it's not unreasonable to expect it would be logged.
2) You could do statistics on player position reports when on job combinations without access to Powder Boots/Flee. If someone's mean speed over a reasonable amount of time (say 3 minutes) exceeds what is theoretically possible, ban them.
3) You could do statistics on how quickly players swap equipment. Windower macros and spellcast swap it much faster than vanilla macros because of the forced delay between macro lines in the official client. There, now you've caught 90% of the windower crowd.
4) You could do analysis of AH use frequency/time of day for each character. If you find that a character is active (moving around and issuing different server commands) at pretty much any time that they aren't placing AH bids at a regular interval, ban them for AH botting.
5) Fish botting would be easy enough. Just analyze how selective people are for specific fish in ambiguous cases.

Still, there's no one at SE with this job and it probably wouldn't be a smart business decision to ban everyone like this even if there was, so it doesn't get done.

[Buffy]

Given a few weeks with nothing else to do, I'm fairly confident that I could ban many people for TOS violations using only data that's already reported to the server with a minimum of innocent casualties. You could figure out everything from flee hacking to AH botting to shit like this by doing statistics on server requests from individual characters. For instance:
1) You could ban everyone that trades a book to the assault exit in under a minute. Minimum of innocent casualties, and you get the people that cheated. SE's servers are almost certainly involved in that transaction and it's not unreasonable to expect it would be logged.
2) You could do statistics on player position reports when on job combinations without access to Powder Boots/Flee. If someone's mean speed over a reasonable amount of time (say 3 minutes) exceeds what is theoretically possible, ban them.
3) You could do statistics on how quickly players swap equipment. Windower macros and spellcast swap it much faster than vanilla macros because of the forced delay between macro lines in the official client. There, now you've caught 90% of the windower crowd.
4) You could do analysis of AH use frequency/time of day for each character. If you find that a character is active (moving around and issuing different server commands) at pretty much any time that they aren't placing AH bids at a regular interval, ban them for AH botting.
5) Fish botting would be easy enough. Just analyze how selective people are for specific fish in ambiguous cases.

Still, there's no one at SE with this job and it probably wouldn't be a smart business decision to ban everyone like this even if there was, so it doesn't get done.

The fish botting on in particular is interesting.

I won't say they would never do it, the salvage bans were before my time, but apparently people never thought they would get banned for duping either.

[Cairthenn]

I'm still beyond comprehension of why people feel the need to constantly mention Salvage bans in a manner that it suggests it wasn't a complete anomaly. On top of that, the game is very different than it was in 2009 and SE has a lot more to lose if they were to undergo a similar sweep.

[Churchill]

I'd be willing to bet anyone using ASE does not have an aversion to clipping through walls. Popping that mob probably wouldn't be too smart though. That's like talking to the invisible moogles in Bastok Mines.

Not quite the same, detectable sure, but not the same. I've popped 15 NMs multiple times this way and I'm still around and able to anger a certain recluse.

It's a bit more dangerous than targeting a depopped ??? in abyssea but not much more, I would think. Even running in Ru'lude and targeting that Alex is detectable, but it's not something they focus on.

[fantasticdan]

Why would the targeting abyssea NM ???s be more dangerous exactly? I know a few people that used to spam trade macros on despawned ???s to outpop people back in the day, but afaik none of them were ever banned.

[Churchill]

I didn't say more, I said it was slightly less. The point is that they don't check for that kind of thing, if they did, most of us would be banned.

[Mahoro]

Nice sig Rearden, that was a great scene last week in BE.

[Asymptotic]

They probably don't attempt to detect such things because it's possible for things to get stuck / lag / whatever and be targetable by the client when they're not supposed to be.