Forum Replies Created
-
Posts
-
I think alot of people already said what I’ve been thinking about MSQ support, so I’ll just address the other portions.
Fates and material grinding are iffy. Unlike gathering, killing monsters would definitely directly impact legit players and would lead to more outcry against bots. There are many ways to make gil and level up with Miqo, in addition to the amount of work the developers have to add to Miqo like trusts, I don’t think we really need these features.
I think its definitely a good thing that the Miqo devs are thinking about protecting its users and botting as a whole. Its a miracle that Square Enix don’t detect and punish bots as severely (as long as its not RMT) as other games like Runescape. Most Miqo users enjoy the game but don’t want to deal with the more grindy stuff, and I’d like to think we want to keep the current status quo by keeping our impact to a minimum to legit players.
If Miqo devs wants to proceeds with material hunting, I’m ok with restrictions like single instance only as long as my privacy is maintained. If people want to figure out a way to abuse Miqo for RMT, they would probably figure out a way even with monitoring and there isn’t much you can do to deter them.
I had this problem as well.
What I did was add koCheckpoint() to the beginning of the chapter for whatever I want to gather for the day. When Miqo dies, she’ll restart from the beginning of the chapter. It only allows for a maximum of 3 KOs before exiting the scenario, but I think you could probably refresh the KO count if you put repeatChapter(x) at the end (haven’t tested it).
Its not quite the same as what you’re asking for, but you could make multiple chapters with koCheckpoint() on each one and set gather(x) low enough so Miqo can rotate between them if she doesn’t get killed.
