SlaughterHouse

Glad the forums are back up even if it isn't fully function yet but it's good to have a place to come to again :3

Wich is the frezee rate?
(My main language is spanish, so I apologize about my english.)

I believe no one has reported being frozen and you are unlikely to get frozen unless you use insane and impossible refresh times.

For the suggestion - I was thinking about implementing something like that, but all the methods of implementation didn't seem very flexible, would a stop when exp is no longer being gained suffice?

Yeah I think that would make a great addition.

Suggestion:

The training function could be extended to add a feature such as train for x minutes or hours. Train until x level or x levels gained. Suggested this as when I went out today I was going to leave it on for a few levels but I was gone for awhile so it would of ran non-stop so I couldn't run it.

Bug:

1). It occurred for a second time, where the fight is complete but it fails to end fight without picking up with it via the fail safe. Script was running for longer than 4 minutes after it beating the mobs and failing to end fight without picking it up. This only seems to occur for me when running move scripts. (EDIT: 1 Further Occurrence)
2). I opened the AP and went into settings after altering most settings and exiting from it I went to start a move script. AP crashes with an "unbound error". Occurred after retrying it again on opening the AP. But when I opened the AP a third time and never went to the settings the AP worked as normal. (EDIT: Another Occurrence of this, it appears it has nothing to do with settings but rather if you run a move script and the first move it encounters a mob or set of mobs. This was the case also with the previous two cases I reported this happening.)
3). Unsure if this is a bug or not or intended but the AP does not output who the fight is with when encountering it. It did do this before updating to 0.7.

Overall:

It's running much more smoothly than it was in version 0.6 and as far as I can see so far those are the only bugs I have picked up on.

Wouldn't that kind of make it redundant to have it as a setting? Glad to know I don't have to fix anything. And unless I say it's necessary in the release notes you probably don't need to update the config.

A way around it then could be as soon as you log in detect if one of the characters you have has a setting needing configured if it does request it to be set?
Or have a hidden value if settings are defaults and prompt at first login to configure them and if they decide to leave as defaults then remove it next login.

It's just I think more people will make the same mistake as me as I did trying to get it to work.


EDIT:

Just as I posted this bug came up. It won a fight outputted it in the log and continued looping out seconds as if it was working. I am running a move script. So I thought it was just moving. Script finishes running and I log in to check it and it got stuck at an end fight screen.