TACO

From Goon Wiki
Jump to: navigation, search
TACO Reloaded.png


T.A.C.O is a mostly abandoned project that works by reading the chat logs of your client. This is completely legal, and allowed under the CCP EULA, and this has been confirmed by them many times.

TACO works by reading your intel channels, and once properly configured, reporting to you where hostiles are in relation to you. It can also alert you when Faction or Capital spawns are shooting you.



Prerequisites

  • You must have chat logging enabled:
Chat Logging Enabled.png
  • You must install .NET 4.5.2 or above (.NET 4.6 is recommended)

https://www.microsoft.com/en-us/download/details.aspx?id=48130

Installation

  • Download the file
  • Extract the zip file and run taco.exe
  • Click the "Start Watching Logs" button
  • Configure it to work properly

Configuration

Once TACO is open, you will be met with a few options.

  • Go to the "Config" tab, and then open the "Alerts" tab.
  • Select each trigger individually, press "Edit Selected" and change them to look like this:
Alerts.png
  • There are other settings you can modify, but this alert setup should get you ready to go.

Using TACO

Once you are ready to go, make sure you have joined the appropriate intel channel for the region you are in.

  • Delve: delve.imperium
  • Querious: Querious.imperium
  • Period Basis: period.imperium
  • Fountain: ftn.imperium (if you are in fountain, you need to cheat a little and check the box for tribute, and change it https://i.imgur.com/klIG5fa.png ... if this doesn't work, please contact ratknight1 on jabber and let me know)

If you are ratting on a border system with another region, it is a good idea to have that intel channel open as well.

  • On TACO, press "Start Watching Logs"

It should show your character in the system it is in (it reads this from the local chat log), and if you go to the "All" Tab at the top, you should see log information from your client showing up there. If you do not, restart your EVE client, and stop watching logs, and restart watching logs once you confirm that logging is enabled. Make sure something has actually been reported in intel since you turned on the logging.

Links and Sources