I find that fix useful, but stupidly coded.
If I'm not wrong that game was coded in JAVA. Why not simply add an attribute to the player's code that stores the last map instance he visited (depth, gate, players in, or maybe even if each group has his own instance of each map he visits the memory adress of the map, or whatever main attribute qualifies it) and just add a function that checks the map he wants to join or get invited in isn't the same instance as the map he's visited right before.

"I find that fix useful, but stupidly coded.
If I'm not wrong that game was coded in JAVA. Why not simply add an attribute to the player's code that stores the last map instance he visited (depth, gate, players in, or maybe even if each group has his own instance of each map he visits the memory adress of the map, or whatever main attribute qualifies it) and just add a function that checks the map he wants to join or get invited in isn't the same instance as the map he's visited right before."

No. It would be too easy to just do a random floor and then rejoin.

I doubt much people would bother doing one floor then go back to their looping stuffs over and over..another solution could have been to allow the same player to join the same group ONCE only, that's even more logical.

Wait, what's the issue exactly? The you can't invite people at all after soloing, or you can invite once you descend one depth? The first poster seemed to imply the latter, which isn't that bad at all.

Not from what I can tell in his first or second posts, but even then it isn't really clear.

From what I understand, people aren't getting upset that looping is fixed, but rather OOO decided to fix looping by making players unable to join at clockwork terminals.

Which I'm not cool with TBH

Can someone explain what has been changed exactly? Since they decided not to mention this in the update announcement....

They silent update like crazy.

I had an experience where I joined a random party, I was at the terminal, I could see everybody listed in my upper left, but I was alone on the terminal and the lift was already gone...

Does this reduce my chances of joining a random pub at terminal?

It's not hard to chill out at the entrance of FSC and invite friends who already geared up...
However, it is useful to change equipment based on what others have, and this would have to be done on guild chat or mediated through one person... bleh.

Wooooow, talk about a half thought out solution. Anyone who says this is reasonable obviously doesn't know what they're talking about, this is good for looping but incredibly horrible if you need help AT ALL.

Bad solution OOO, bad solution.

Thats the price you pay for abusing the system.

Yes...people exploiting the systems leads to workarounds to prevent them from doing so that screw over everyone else.

This is why heat and coins now expire like hearts--people would loop back to the start of a level and repeatedly collect everything. To prevent that cheat, we're all inconvenienced.

Level looping in general was clearly spelled out as being against the ToS multiple times, but people did it anyway. Here's the solution, and again we're all inconvenienced.

The solution? Play the game as intended, not "the game" in a meta sense that exploits features or bugs, otherwise we'll keep getting these half-assed "fixes" that make life difficult for everyone else.

(Note that I do not consider the practice of getting to D23 in FSC with a PUG and going solo to form a guild/friend team an exploit...this would seem to be using the system in one of the ways intended.)

To all those who not only looped, but argued strongly that it wasn't an exploit. Gee, thanks. This is why we can't have nice things.

Surely there is another way to do this that doesn't make me not be able to invite after I get kicked. Thats just horrible, I've been in terrible partys who have kicked me for no real reason, and to not be able to rebuild.... thats just crap.