Pick the theme you use in the app (Settings ▸ Theme). Light or dark follows the switch at the top of this page.

Help

Report a bug

Record one task’s next run into a file you can send to Evonex support.

What it does
Records the next run of one task into a single file for Evonex support: pictures of the game, every step, every tap and every log line.
Where
Instances ▸ open an instance ▸ Duties ▸ the bug button at the right end of the row of jump keys, beside Filter by name
You need
An instance with the task you want recorded. Sending from the app needs a connection to Evonex.
It costs
Nothing in the game. A minute of recording takes about 2.5 MB of disk space.

When a task does something wrong, a short recording tells support far more than a description can. Click the bug button, choose the task, click Start, and let the task run. Evonex records 60 seconds by default and saves the file. The task keeps running afterwards.

The right end of the row of jump keys on Duties: the filter, and the bug button beside it.
  1. 1Filter by name Narrows the page to the duties and tasks whose name holds the words you type.
  2. 2Bug report Opens the recorder. It draws its own state, so you can read it at a glance.

Record a report

  1. Open Duties for the instance where the problem happens.
  2. Click the bug button. The Record a bug report window opens.
  3. Check Task. It starts on the task that holds the screen at the moment, usually the one with the problem. Pick another if you need to.
  4. Leave Record for at 60 seconds, or choose another length.
  5. Write a line or two under What went wrong?. It is optional, but it helps support a lot.
  6. Tick Send it to Evonex support when it’s done only if you want the file sent by itself. It starts unticked.
  7. Click Start. The button turns green: the report is armed. If the task has the screen at that moment, recording starts at once. If not, it starts the next time that task runs, even after you restart Evonex.
  8. Wait. The button shows the seconds left. When they are up, Evonex saves the file.
  9. When the report is saved, click the button again. Press Send to support, or send the file yourself from its folder.
The Record a bug report window. The folder under Save to is only an example.
  1. 1Task Chooses the task to record.
  2. 2Record for Sets how many seconds to record.
  3. 3What went wrong? Takes your notes for support. This box is optional.
  4. 4Send it to Evonex support when it’s done Sends the file by itself when it is saved. It starts unticked.
  5. 5Save to Names the folder that keeps the file.
  6. 6… Opens a folder chooser.
  7. 7Start Arms the recording.

The window

Task
Every plan task comes first, then every duty, with a line between the two groups. A switched-off one is marked (off). A name that exists in both groups gets · tasks or · duties. It starts on the task that holds the screen at the moment.
Record for
How many seconds to record. Range: 10 to 1800, in steps of 10. The window adds or until the task finishes: whichever comes first ends the recording. Default: 60.
What went wrong?
Your notes for support, up to 2,000 characters. The box suggests: What did the task do, and what should it have done? Optional, but it helps support a lot.
Send it to Evonex support when it’s done
Sends the file as soon as it is saved. Default: Off. It starts unticked every time you open the window, including when you click Record again.
Save to
The folder that keeps the file. The … button chooses another. Evonex starts with a Bug Reports folder inside its own data_store folder, which an update leaves alone, and after that remembers the last folder you used.
Start
Arms the recording of the chosen task. It stays grey while the page has nothing to record.
Cancel
Closes the window without arming anything.

What the bug button shows

The button shows its state by shape as well as colour. Click it in any state except Off to see the report’s card with the buttons that fit.

Off
A grey outline of a bug. Click it to open the setup window.
Armed
A green bug inside a solid ring. Hover it for Bug report armed: recording starts when this task runs. The card offers Change… and Turn off.
Recording
A small chip beside the bug counts down the seconds left, for example 42s. A red dot blinks and a light circles the bug. The card offers Mark this moment, so support jumps straight to it, and Stop and save. The button turns amber if Evonex saw a problem. It keeps recording.
Saving
The ring turns while the file is closed and put in your folder.
Sending
The ring fills as parts of the file reach Evonex support. The card offers Stop sending. If Evonex closes meanwhile, it carries on from where it got to next time.
Waiting to send
An amber up-arrow badge. Click to see why. The card offers Try now, Stop sending and Show in folder. Evonex tries again by itself, and the file is safe in its folder meanwhile.
Sent
An up-arrow badge. The card shows a reference such as 7K2Q-9MXD, with Copy reference, Record again and Dismiss. Mention the reference when you write to support.
Couldn’t send
A red ✕ outline. The card offers Try again, Show in folder and Dismiss. You can still send the file from its folder yourself.
Saved, not sent
A badge: a green ✓ means the run went well, a red ! means it failed, a blue ■ means it was stopped. The card offers Send to support, Show in folder, Record again and Dismiss. Dismiss puts the button back to grey.
Couldn’t save
A red ✕ outline. The card offers Choose a folder…, Send to support and Delete it. Evonex keeps the recording safe inside itself until you pick a folder.

How a recording ends

What a report holds

The file name ends in .exbug and the file is sealed. Only Evonex support can open it, and you can’t open it yourself. Support keeps a report you sent for 30 days.
Because the file holds pictures of your game, send it when support asks, or when you want them to look.

Where the file goes

Into the folder under Save to. Files stay there until you delete them. To open the folder, use Show in folder on the report’s card. If Evonex can’t write there, the button shows Couldn’t save and offers Choose a folder….

Send it to Evonex support

Tick Send it to Evonex support when it’s done before you start, or press Send to support on the saved report’s card. Sending needs a connection to Evonex. Evonex sends the file in parts and keeps the speed gentle, so your game connections are not hurt. If the connection drops or you close Evonex, it carries on from the next part.

If it can’t send, it waits and tries again by itself: after 30 seconds, 2 minutes, 10 minutes, 30 minutes, then every hour. The file stays in its folder meanwhile, so you can also send it yourself.

Problems?

The button is green, but nothing records.
It is armed: recording starts when that task next runs. A plan task has to be switched on and due. A duty has to be on and due.
It stopped after a minute, but my task kept going.
That is by design. Your seconds were up, so the recording ended. The task goes on.
It says Waiting to send.
There is no connection, or the server can’t take the report yet. Evonex tries again by itself. Click Try now to go at once. The file is safe in its folder.
It says Couldn’t send.
Evonex gave up on this report. The file may be too big, the connection may have failed for a week, or the file may be gone from its folder. Click Try again, or send the file from its folder yourself. Evonex also sends no more than ten reports a day.
It says Couldn’t save.
Click Choose a folder… and pick another folder. Evonex keeps the recording until you do.
Can I open the file myself?
No. It is sealed for Evonex support.
Can I record two tasks at once?
No. An instance holds one bug report at a time. Starting a new one replaces a saved or armed one. A report that is still being sent carries on in the background.
Does recording slow my instance down?
Not noticeably. Evonex only notes what the task does, and writes the file in the background.