taultunleashed

THIS TOPIC IS FOR REFERENCE ONLY.
SEE RED MOON RISING TOPIC FOR WORKING SCRIPT

What did Red Moon Rising change that broke this script?

1. Options menu added some things and changed the window colors config.

2. Intro movie switches game to full screen. Stays that way every time cache is cleared.

3. Log on/game up detection changed.

4. Game screen was reduced vertically by 50 pixels. Watch closely when logging on and you will see screen shrink. This also has the side effect of making all existing "Y" coordinates off by 50 pixels.

5. Tutorials fixed. You still get them everytime there is a new event but they don't repeat once you unchek the option in options menu.

6. Overview items selection changed to menu/group style. Good improvement.

7. New group of NPC's/ships added to overview menu.


I thinks that's about it. This script is a later version than the one I modded for Red Moon. Abbreviations are used thru out, it has a more elegant mousemove routine, more window error checking, email notification in event of podding, and of course a good beta code for hauler/jetcan.

Buck





*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1013.0500 RC1
2005-10-13 05:00 CST
8221 Lines

Feature Release...

1-Integrated New SendMail Private Data into New MAX-GUI Interface...treated as private data and encrypted...2nd Dialog completely redesigned to accomadate...Be Aware that switch to turn on must be made manually at this time...change it in MAX_COTE.ini if you want to use it...last variable before [PRIVATE]..."SM"("vSM")...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1013.0000 RC1
2005-10-13 00:00 CST
7990 Lines

BugFix Release...

1-Fixed label error in "OverView_Lower_Close" ("OVLC")...recheck goto was "OVLCLST" and should have been "OVLCST"...I made a few of them errors in my haste...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1012.1400 RC0
2005-10-12 14:00 CST
7990 Lines

BugFix Release...

1-Further tweaked WarpTo Button Search upon reflection and reading back on more prior feedback...Range changed from x=428-433 to x=427-432...still a 5 pixel spread...feedback also indicated someone who had posted several triangle coordinates of x=428 and x=432 for centers of triangle...that means an "x" start pixel for triangles of x=427 and x=431, mine being x=430,...just starting one pixel sooner to gain benefit of testing for "tallest" part of triangle, and snipped it one on end to keep 5 pixel spread, because a triangle with a center of x=432, starts at x=431, and x=433 of that triangle is only one pixel tall...a slim target at best for a triangle that should already have been detected earlier in routine...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1012.1100 RC0
2005-10-12 11:00 CST
7990 Lines

BugFix Release...

1-Changed WarpTo Button Search Even tighter to stay optimized...from x=425-435 to x=428-433...Previous feedback had mentioned a 2 pixel to the left difference in menu displays...Triangle is 3 pixels wide...so some are 428-431, mine are 430-433, so 428-433 should cover both spans AND return our code to a tight 5x5 check...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1012.1030 RC0
2005-10-12 10:30 CST
7990 Lines

BugFix Release...

1-Changed WarpTo Button Search changed from x=430-435 to x=425-435...Should cover menu display differences now...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1012.1000 RC0
2005-10-12 10:00 CST
7990 Lines

BugFix Release...

1-Wrote a few new small "Space_Detect", "Station_Detect", "Post_Tutorial_Detect", & Changed Old "Space_Detect" for CargoHold Switches to "Space_Check"...and purged all legacy code I could find...All station/space interops should now be using proper Optimized "WPC's" without extensive use of legacy waits...

2-This has been brewing for a long time in coming...OverView Setup Changed...Lower Resizing only stretched to y=755 (Actual bottom line position is now y=757)...This just clears the CargoHold AND clears the multiple mining laser problem...Still leaves a 30-line OverView check, when Upper is closed...This will have to do, since I'm not ready to make the mining ops even more vulnerable to error and interference by dropping color checks that far down...from what I checked, with multiple laser usage...3+ lines of overview are messed up anyways...just haven't noticed it that much...but we want 100% accuracy...

PS At least until I update my version to a 1600x1200 proper fullscreen mode...which is what the game was really written for anyway...my only problem was and is finding a pixel color/position checker/magnifier that works in full screen mode...haven't found one yet...And that also means a lot of peeps will be left behind who can't push those kinda pixels...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1011.0600 RC0
2005-10-11 06:00 CST
7979 Lines

BugFix Release...

1-Fixed numerous "Dock_&_Dump" Errors in State Detection...May have lost a CargoDetect during Logon procedures...too bad...should have left code the way I had it 3 months ago with 2 cargo checks period...this 17 ways to start a macro bs is a frickin pain in the !@#$%^&*, this was only intended for my debugging purposes, not because everyone else is lazy...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1011.0500 RC0
2005-10-11 05:00 CST
7982 Lines

BugFix Release...

1-Fixed label error in OverView_Upper_Close...had "OVUCLERR" call instead of "OVUCERR" call...

2-Fixed numerous "Dock_&_Dump" Errors in State Detection...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1011.0400 RC0
2005-10-11 04:00 CST
7985 Lines

BugFix Release...

1-Fixed Color Check For "OverView_Lower_Resize_Logon" Module...

2-Fixed OverView Settings Config for OreType if "vHauler=YES"...for now...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1009.0400 RC0
2005-10-09 04:00 CST
7969 Lines

BugFix Release...

1-Added Color Check For Unique Color For OverView Settings ScrollBar movement...to be reused during scrollbar ops...

2-Widened Color Range For Pixel Checks To Find Triangle WarpTo Button...Had To adjust...Yes, we are back to the WarpTo Buttons Again, Since Text Layout changed, and Text overlays vary, text check is not practical anymore...

3-At this point, recommending use of "Zoom" Feature and use of variable "vOVERR=YES" at top of macro for overview window op errors...at least till I readily see that we have a color or pixel issue...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1009.0200 RC0
2005-10-09 02:00 CST
7955 Lines

BugFix Release...

1-Made Mistake adding SendMail Code To EVE-Close Module...It is called before logon to check for open windows...Removed...

2-Added new variable "vSM=[YES/NO]" to switch off SendMail Module for those not wishing to use it...

Sorry about the oversight...had done debugging with in space/in station starts...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1007.0230 RC0
2005-10-07 02:30 CST
7956 Lines

Feature Request Release...

1-Added New Email Notification & Attached Current Date GameLogs...By request for "buckw1"...

Module only triggers for now at "EVE_LogOff", "EVE_Slam", & "EVE_Close"...

Also Variables of Private Data (aka "vRecipients" & "vServer") are now found at top of macro, but at bottom of variable list...Will be moved into Private Data Secure Logon Window if liked...

Also include near the private data variables is one more: "vSendMail_Debug"...If Set to "YES", Will LogOff, and trigger Email Notification to test delivery, and attachments...

Integration into new interface is some major piece of work...will wait a bit to finalize functionality...Can be used as is upon game quit or crash, or integrated into game functions...

Upallnite
*************************************************************
*************************************************************
*************************************************************
New Release:
v5.1006.0600 RC0
2005-10-06 06:00 CST
7930 Lines

Major, Feature, BugFix Release...

Short & Sweet:

1-All New MouseMove Code For Logon Ops...Now with "Elegant" Pathing, Acceleration, and Deacceleration at end of stroke... Tweakable...But defaults ARE optimized...Settings at top of macro if you must fiddle with...Module is "MMT"...Module is used for all Logon ops...HOWEVER...module is switched off and bypassed unless absolutely needed for drag ops, AND ONLY For Logon ops...If "vDebug=NO" Module will spew all sorts of checks for your perusal...Module Variables are "vMMT=[0.000-?.???]" for wait (sec) per individual move in series...Default is 0.010, and optimized..."vMMTP=[0.00-1.00]" is percent of total travel to use as default incrament...Default is 0.10, and optimized...

2-All New Window Search Function...Module: "AI" and supporting SRT's...Incorporated in new window ops...

3-All New Window Ops, Incorporating New Window check functions, and new "AI" routine...No more LogOffs on window op failures...Macro now finds window if lost and readjusts if possible...Function is desired position is checked, then patterned search is started, when found, window op is completed, if possible, or "AI" is called again...Truthfully, This module should never need to be called...but may save a few extreme system problems...The module is NOT meant to correct main game environment alignement problems, only to correct and aid lag issues, logon window op issues...

4-All New Radio Button Check Routines: "Select_Button" & "DeSelect_Button"...Button States Are now detected without fail...

5-All New MASSIVE CODE REWRITE & Code Compression of Mining Functions, Window Ops, Warp Routines...60-80% Reduction in Code Parsing...My "KeepAlive" Mining Timer dropped from a 5 sec cycle to less than 1.5 secs...I Detect RATS in less than 0.500 secs...I Evade in 1-2 Secs...

6-Numerous Bugfixes added or resulting from new code rewrite...

7-Also added New CargoHold Function for firelord, that lets you set percentage of cargohold capacity to check for during CargoHold Detect Module...Variables at top of macro for this module, are: "vCHDPS=[YES/NO]"...(The Switch)..."vCHDP=[0.00-1.00]"...(The setting of percentage of cargohold capacity to check for...)

Notes: Almost 2000 lines of code were purged...Over 3000 new lines of code were added...Over 500 lines of Code was Eliminated During Code Compression, & Optimization...

Also: Debug mode is becoming a more true testing/debugging module...much more wealth of checks and info is given...popups check steps at crucial functions...New "AI" Window Search Function has accompanying MouseMovement during debugging, so you can see what it is doing...

Enjoy...

Upallnite

_____________________________________________________________

System Requirements:
_____________________________________________________________

01)-Windows DeskTop @ 1280 x 1024

02)-ControlPanel/System/Advanced/Performance must be set to "Adjust for best performance". Noncompliance will alter pixel/color detection.

03)-Wallpaper should be set to "None". Macro Code sample backgrounds to test for game crashes. Actually any solid color is fine.

04)-Screensaver must be set to "None". Macro wil be interrupted if screen saver is activated.

05)-Power down of Monitor is safe to use...

06)-Eve Online @ Default 1024 x 768 Windowed Mode (Will Be Set By Macro!)

07)-Must Have Station and Asteroid Field Locations Saved in "PEOPLE & PLACES"

08)-Recommended To Have 3 or More Plentiful Asteroid Field Locations Saved To "PEOPLE & PLACES"

09)-Other Bookmarks in People & Places are permitted, as long as:
_____________________________________________________________

A)-None of the listed System BookMarks for mining are listed lower than the 27th line of P&P After Configuration

B)-All of the System Asteroid BookMarks for mining are listed Contiguously

Sample Extreme Setup:

System Station is Listed on #20 Line.
3 Asteroid Fields are listed on Lines #7, #8, & #9.

This setup is just fine. Variable setup would be:

vPPSlot_Station_X=20
vPPSlot_First_System=7
vNumber_Asteroid_Fields=3

Notes: ONLY Asteroid Fields have to be contiguous,although they all can be. Some folks spend a lot of time and effort

renaming Bookmarks. This is not necessary. The macro was designed to work with standard Bookmarks saved in People & Places.
_____________________________________________________________

10)-Must Have Mining Lasers Fitted in High Power Modules starting with #1.

11)-Must Have MWD or AfterBurner Fitted in Medium Power Module #1. AfterBurner is highly recommended. Actually MWD might be faster for docking purposes, but it causes a lot of overshoot/s(t)uckage issues in Asteroid Field.

12)-Must Have ArmorRepair Unit (if used) Fitted in Low Power Module #1.

13)-Recommended to have no programs running, except for AntiVirus/FireWall software. It is further recommended that these or any other running background programs have their auto-update features disabled. You can manually update them, and make sure to turn off the notifications too, or they will interrupt the macro.

14)-a Little spring cleaning goes a long way, use msconfig to check for bastard programs running in background. But be careful not to shut down various functions of your AntiVirus/Firewall Software. Those with Win2000, check google to find a copy of the msconfig program from winxp that runs fine on Win2000.

15)-The EVE install uses a default install of "C:\Program Files\CCP\EVE". While it is not necessary to install EVE to your "C" drive to run the macro, you must have the "\CCP\EVE" Directory Structure intact. The macro wil look for the installation starting in "C:\Program Files\CCP\EVE", then "C:\CCP\EVE", then "D:\CCP\EVE", then "E:\CCP\EVE", etc, all the way to "Z:\CCP\EVE". The macro will not find the game if it is installed in a non-default directory structure.

16)-The macro running program: "Macro Scheduler" must be installed in it's default installation directory of "C:\Program Files\MJT Net Ltd\Macro Scheduler". The latest Stable Release is 7.3.114. The new version 7.4.00? is not considered stable as it has issues such as popping open randomly.

17)-The "MAX_COTE.zip" package must be downloaded and unzipped to the default Macro Scheduler installation directory: "C:\Program Files\MJT Net Ltd\Macro Scheduler" creating the Directory Structure: "C:\Program Files\MJT Net Ltd\Macro Scheduler\MAX_COTE". This is vital to the running of the macro. You can place the "MAX_COTE.zip" file in the default directory of Macro Scheduler and unzip it there, or from an Archive, if you are used to working with zip files. The package includes the main macro itself along with help files, support files, changelog, images for the new interface, a link to the Greenwich Mean Time Web Site, an encryption/decryption program, and registry tweak to optimize the sizing of notepad for optimal viewing of the interface help files.

18)-You must open up "Macro Scheduler" and "import" the macro to use it. You can run it right from where it sits in "C:\Program Files\MJT Net Ltd\Macro Scheduler\MAX_COTE" or put a copy in the Macro Scheduler directory, whichever you prefer. There is also a "BackUp" directory under MAX_COTE, that contains backups, in case of an accident, of the macro and some vital files.

19)-You must assign a hot key to the macro. Just open up Macro Scheduler, and right click on the MAX_COTE macro, and select "Macro Properties". There is also a place to specify logging if you are having trouble with the macro. Best setting is to Select: "Log Progress of Macro", "Empty Log File Before Each Run", & "Log start and completion of each step".
_____________________________________________________________
_____________________________________________________________

*****WARNING*****
*****WARNING*****
*****WARNING*****

BEWARE POSTING OF LOGFILES...

Encryption is used for writing private data to the hard drive in the form of an "INI" config file.

HOWEVER, if logging is used, the log will reflect interpreted variable values, including usernames, passwords, character names, AND the encryption password, which is system specific.

DO NOT POST LogFiles, unless you have coding experience and you are comfortable editting LogFiles, and searching for variables. LogFiles can be extremely long, and data may not seem readily accessible.

*****WARNING*****
*****WARNING*****
*****WARNING*****
_____________________________________________________________
_____________________________________________________________

20)-Kick The Tires & Light The Fires...First Time Run...


Functionality of Standard Initial Run:


A)-Hot Key Trigger the macro...Wait about 10-30 secs, depending on system specs...

-MAX-COTE runs install check to find EVE install

-MAX-COTE runs "Variables" Subroutine to check for existance of MAX_COTE.ini File.

-MAX_COTE Loads default Variable Values, Writes "Default.ini" for possible interface reset.

-MAX_COTE opens the default background for the new interface

-MAX_COTE opens the new MAX-GUI Interface

B)-First Interface Menu - General Variables:

-MAX-COTE displays several coloumns of variable data:
"Variable Label, Variable Value, Variable Current, Variable Change, & Variable Help"

-First, you can use the "Help" buttons by each Variable to learn about each variable.

-Next you can make choices in the Column Marked: "CHANGE".
The drop down values eliminate errant/unsupported choices.

-The Macro Will Only Update it's memory values if you hit the "Update Current" button after you make choices.
The column "CURRENT" will show memory values updated in realtime.

-Next You should save your values to a NON-Default "INI" File ("MAX_COTE.ini" File).
By pressing the "Write Current" button, a NON-default "INI" file ("MAX_COTE.ini" File) is written.
A popup will verify this, and show you it's contents.

-You may press "CHANGE", "Update Current", or "Write Current" as many times as you like.

-If you press "CANCEL", you will be dropped out of the Configuration without further changes.

-If you press "RESET DEFAULT" values, default values will be loaded.

-If you press "Next", and MAX_COTE will update your changes, write the "INI" file, and continue the configuration.

C)-Second Interface Menu - Secure Logon Window:

-Here You must enter your private data.
Functionality is similar to First window, but with secure enhancements.

-UserName,PassWord, and Character Name are entered in a secure masked input box, by pressing each's button.

-Pressing "Update Current" Button, encrypts and loads private data.
Success Status is displayed in "CURRENT" Window.
Failure prompts an error message.

-Pressing "Write Current" Button encrypts and loads data, then writes encrypted data to the "MAX_COTE,ini" file.

-Pressing "Next" Button encrypts, loads, and writes the encrypted private data to the "MAX_COTE,ini" file.

-Succes will be verified by a popup displaying "MAX_COTE.ini" File contents & Secured data encryption.

-Error Will be indicated by message popup describing problem.

Notes:Basically you can change values, and either press the "Update Current" & "Write Current" Buttons or, press the "Next" Button which does both. The 1st choice was designed for reassurance of the process.

D)-After Pressing "Next" on the 2nd Window (Secure Logon), macro will prepare and start EVE.

-This may take a short while as MAX-COTE must also reload the newly finished "MAX_COTE.ini File"
_____________________________________________________________

Notes: The MAX-COTE Miner Macro will set up your game environment and game windows as they need to be during the running of the macro. Please remember to leave the default setting of "VClear_Cache=YES" for initial macro setup. On subsequent startups, you can edit the "MAX-COTE.ini" File and Change to NO, or delete the MAX_COTE.ini File and recreate a new one using the new interface, but with "vClear_Cache=NO" to preserve your settings. The initial setup of the macro can be very time consuming (5-10 mins), as many checks and rechecks occur to ensure stable running of the macro.

You will need to take some time and read the help files concerning all the variables available in the macro. PLEASE READ THEM. They are your 1st line of support. This is an extermely complex and all inclusive macro, that does require some savvy and skills with regard to setting program options, setting, running, and reading logs, and pretty decent windows system skills to ensure optimum running of your machine. If you are already having problems running EVE or other programs, or your system runs sluggishly and problematically, chances are the macro will only increase your troubles. EVE itself, is quite a resource hog, and some might find that while they are able to get by running EVE fairly decently, that the additional resource draw of the macro slugs their systems down to the point of graphic lag/buffer errors/cursor hourglasses/game crashes, etc...

On a higher note, I will say that I myself run this macro on a plethoria of systems, from a Intel 3.4EE, SCSI Raid, ATI 850XT PE AGP, 2 GB DDR, all the way down to a Dual 1 GHz, IDE, NVidia 5700 Ultra, 256 MB PC 133. I use both WinXP Pro and Win2000 Pro, Basic Power User Settings, No exceptional tweaks, just eye candy turned off, only AntiVirus/FireWall running.
_____________________________________________________________

ISSUES:
_____________________________________________________________

Now For the Nitty Gritty: (For People With Pixel Placement Problems)

Game Mode at 1024 x 768 is not perfectly centered on screen...

Upper Left Corner of Utmost Corner Pixel of "EVE" Windows Widget (MS Windows App Box) is exactly 128,128.

However, Because of the Size of the Title Bar, and Borders, EVE Game Window, Upper Left Corner is 131,150.

Game Window is indeed 1024 x 768 but is offset 3 Pixels Right and 22 Pixels Down from Frame.

Here Are My Exact Coordinates:

*************************************************************

Window Frame:

Upper Left: 128,128

Lower Left: 128.920-Darker Line

Upper Right: 1157,128-Darker Line

Lower Right: 1157,128-Darker Line

*************************************************************

Game Environment:

Upper Left: 131,150

Lower Left: 131,917

Upper Right: 1154,150

Lower Right: 1154,917

*************************************************************

This SHOULD NOT be a problem. It is very easy however during debugging, to accidently move the Game Window.

If this happens, or you suspect Pixel Misalignment, Game must be restarted, and Macro allowed to Clear Cache, and reset the Game Windows.

_____________________________________________________________

Eve-Online Patch Compliancy: "Cold War Edition"
_____________________________________________________________

MAXimum Conservation Of Time & Energy...
_____________________________________________________________

01) ALL NEW User Interface Configuration Screens for User Configurable Variables
02) Capacity and Rotation of up to 25 Asteroid Fields in one system
03) Stacking of Ore(Back Again!)
04) Non-saving of UserNames and PassWords unless using 24/7 AUTO Logon Feature
05) Ability to restart Macro at various points without resetting/docking
06) Optimized Code Eliminating most user variables.
07) AUTO Logon
08) AUTO Cache Deletion for Stability and Commonality
09) AUTO GUI Configuration
10) AUTO Detects Logon Lag
11) AUTO Detects Place in System at Logon and Starts Macro Accordingly
12) AUTO Detects Dead Droids
13) AUTO Detects Different Ore Densities & Chooses Optimized Ore Availability(Veldspar, Scordite, Plagioclase, Omber, Jaspet, & Hemorphite Only!)
14) AUTO Detects & Evades Rats/Pirates/LowLife's - Yes, you heard right...The first of it's kind (Being Implemented NOW!)
15) AUTO Detects Lagged Mining Lasers Not Firing
16) AUTO Detects Full CargoHold Eliminating Mining Duration Configuration Entirely...
17) AUTO Detects Time to Warp To Asteroid Field & Time to Dock with Station
18) AUTO Detects Time To Dock, Approach To Asteroid, Targeting, and Laser Firing
*****At This Point, All Major "Waits" Are Obsolete, All Timings Are Auto-Configured!*****
19) AUTO Detects Server Information Windows...(AKA, Maintenance Window Warning Pop-Ups)
20) AUTO Detects Ship Destroyed And Docks At Station And Logs Off
21) AUTO Detects CRASHES
22) Optional Stealth LogOffs And LogOns
23) Optimized Computer System Dependent Wait States - Configurable At Logon...
24) Further Optimized Wait States/Functions/Evasion For Fast Systems - AKA "NINJA MODE"
25) Even Further Optimized Wait States/Functions/Evasion For Those with Cray Supercomputers - AKA "NINJA MODE ULTRA"
26) Much Effort Has Been Made By The Community To Ascertain And OverCome NVidia Video Issues...
27) JetCan Mining & Hauling...
28) Tutorial Bug Detect & WorkAround...
29) ANTI-ANTI-MACRO CODE...
30) Randomized LogOns/LogOffs For Stealth...

Just some additional Notes:

Sure to be asked:

What do I mean by "Elegant" Pathing in MouseMove? I mean mathematically correct mousemovement....

My mouse jitters, what's up? You have low system specs, or system lag issues, either with default settings of macro or "tweaked" mouse settings...

My mouse doesn't move erratically in windows, what's up? Your mouse movement in windows is faster...any major slowdown of a mouse path will reveal erratic movement. The mouse cursor NEVER moves a partial pixel, it just moves fast enough normally, that you don't see it...

The new mouse move is too fast...No it isn't, it is optimized to be slower than any normal mousemovement, AND it has natural DEacceleration at the end of stroke to further enhance accuracy...and it is tweakeable if you insist...

The new window ops still don't work...We are getting to the end of the line for options for severely impacted systems...Macro is now super intelligent, it seeks windows, checks windows, searches for windows, adjusts windows, readjusts windows, and notifies upon total failure...

What are my options now if window ops for logon do not run? With new Window Op "AI" comes a new agenda for debugging...The code is already optimized for minimum lag, the code already searches for windows upon window op failure...Recommendations will be to try and get through logon setup ops, with Debugging turned on...This will slow macro down even more than CPU settings, and give some valueable information at each step...It may help severely impacted systems to finish setup...

Debugging indicates my mouse moved to correct positions but my windows/scroll bar never do...You have a severely impacted system, macro DOES NOT, AND CANNOT release anything during a drag op, unless interefered with, or interrupted. You are probably suffering from background app interruptions (AKA hourglass cursor if you are lucky enough to see it)...

If according to you, I have a severely impacted system, what are my options? I do not lightly recommend reformatting and reinstall of operating systems...If you are a system tweaker, you must be aware that systems can be overtweaked, and no system speedup, or power tweak comes without a price...I always make a ghost image, of my systems just after default installs, and drivers, and support apps, BEFORE tweaking to allow me to return to a pretweaked state if necessary...Sidenote: While Norton's apps are resource hogs...the app they bought PowerQuest to obtain (aka V2i Protector) is now Norton Ghost 9.0/Live State Recovery 3.0...Best backup on Planet...100% ACCURATE FAST LIVE BACKUP...nuff said...Macro IS working and running on a variety of systems with fairly basic default settings for Windows 2000 Pro and Windows XP Pro...

Upallnite
*************************************************************

In Reference To New Mouse Movement Coding:

The problem with getting...

-------------------------------------------
Invalid parameters to Round
-------------------------------------------

-------------------------------------------
Cannot read String as Float.
-------------------------------------------

Go to Start-->Settings-->Regional and Language Options.
There you should select English(United States)

Because the problem lies in the use of , or . to separate decimal numbers.

Make sure you are running the keyboard settings as English US or UK, or else the Set name on the Jetisioned can will cause problems.

gmaras (thx greatly for the contribution)
*************************************************************

_____________________________________________________________

Contributors:
_____________________________________________________________

"buckw1" for ALL OS/Background Suggestion in CRASH_Detect Module (100% Solution To Variable Systems CRASH Detection)

"buckw1" for StripMine/Mine-All Suggestion in Ore Selection Modules (Options To Limited Optimized Mining)

"buckw1" for Character Name/ClipBoard Suggestion in Character_Select Module (100% Solution To Random Shuffling of Characters)

"buckw1" for Enhanced Character Page / Introduction Detection Code (100% Solution To Random Lag During Heavy Usage)

"buckw1" for Enhanced Tutorial Module Detection Code

"buckw1" for Patience, Testing & Input

"firelord1973" for Much Hard Work Helping in Forums and Testing Game Environments

"firelord1973" for Patience, Testing & Input

"pbelanger" for Nailing The Elusive Lethal Targeting Error

"pbelanger" for Patience, Testing & Input

"gmaras" for Solution to Macro Math Errors

"gmaras" for Patience, Testing & Input

PlaceHolder...

PlaceHolder...

Comments, Queries, now Welcome...

I would also like to request Admin delete old thread in "Confirmed Scripts" Forum as 99% of info is legacy and obsolete. Thread has been purged of my messages, except for old original thread I started under different user name...

Upallnite

I've been attempting to use this macro but the lag involved is incredible.

I've tracked the problem down to the tooltip that Macro Scheduler shows in the top right of the screen when a macro is running. The problem isn't isolated to just Eve, as any game I play windowed will lag to a crawl if any tooltip, ballon (new hardware in winxp), or popup comes into focus while playing, such as when you place your cursor over shortcuts on the quicklaunch, mail notifications, etc.

Is there any way to turn the tooltip from macro scheduler off?

_____________________________________________________________
Answer: Register the program. Get rid of the pop up but no idea if it solves the lag.

Buck

crashergs...

On an initial start, after undocking, the macro opens the overview settings window, and sets the filters for mining...Any time the macro tries to relog, it is because of a window operation failure. The macro is programed to exit EVE, log off, and relogon to make another attempt to reset everything. If the mouse is jumps around at this point, and fails to close EVE also, then that just verifies that your whole game environment is out of alignment, that the macro is unable to close the game out before relogging.

As far as using the wrong username/password/charactername...the ONLY time this occurs, is if the variable "vAUTO_Logon=NO", then after the first use of username,password,charactername, the macro reloads the default values which are unusable for logging. Did you accidently forget to set the value for the variable "vAUTO_Logon=YES" during configuration? The default is "NO"

synmonger...

I've been using Macro Scheduler for over a year, and I've never seen any tooltip on the screen or desktop...It is possible that this might be just characteristic of the demo version...but I am not aware of it...I did use the demo version for about a month before I purchased it over a year ago, and never had a tooltip come up on my screen or desktop...That may have changed...

Notes:

This macro runs surprisingly well if game environments and menu popups, and windows open where they should. But we have found through extensive testing that there are some issues with some flat screens and scaling, and some video cards/drivers and menu text positioning, and system lag issues and erratic mouse behavior...It's a crying shame that hardware vendors seem to have lost the interest in meeting standards anymore...Between the buggy python code of the game and the differences of problematic display drivers, unfortunately, there are some who may never be able to run this macro. This was not the case just a few short years ago...This macro is exceedingly complex, and must have accuracy to the exact pixel...In some cases, we were able to recode a few small routines for some menu issues with NVidia cards, but it is not possible to recode the macro to work with displays that vary text display, window/menu opening several pixels out of position.

This macro requires a decent amount of CPU power. Some of it's features require constant monitoring. The macro is never idle, even though it might seem at times so...It is checking for crashes, server side popups, RATS when mining, it doublechecks all window operations, hence the attempted logoffs...While frustrating, it is deliberately coded that way to prevent loss to your account or character...if window ops do not complete correctly, the macro will not run...If the macro logs off or attempts to...it is because it has tested it's own actions, found a failure with your system setup, and decided the macro will not run correctly...Whether you think several items may have worked, those items may have worked by sheer coincidence, because of the large size of some buttons for example...but the functions used by the macro during mining require pixel perfect accuracy, or the macro will not run...

The window ops check IS the system test for the macro...Either because of lag or positioning, the macro will not run...

We can try to figure out why positioning is out, but we can't guarantee why any one person's hardware does not display as the majority's...

Nor can we guarantee, why some one's system might lag more than others. We have also seen 1 GHz systems able to run the macro, yet also seen 2.0 GHz+ systems, that can't run the macro and the game at the same time...

There is a section at the bottom of the system requirements on page one of this thread, that describes the necessary window placement to the pixel.
I would suggest you check Google for a magnifying tool, called "Screen Loupe 2000 v5.7", it is a magnifier software package (shareware, but free for 30 days or so) that has a crosshair for the magnifier that "NAILS" the cursor picked pixel. While you CAN use windows magnifier, most of you will not be able to accurately use the cursor, since the cursor is encased in a one-pixel thick outline that makes the pointer inaccurate.

If your game environment is found to be out of alignment, there are several possibilities or causes...maybe a proprietary toolbar or control center on the desktop, that moves the center of desktop out of normal position...maybe the use of the "LUNA" theme in WinXP that also throws the center of screen off...Office Toolbar would be another...

If you notice that during general pregame environment logon procedures, that the mouse movement is erratic, you may have a lag issue...You can delete the MAX_COTE.ini file and use the new interface to recreate the file, but try setting the variable "vComputer_Speed" to another setting..."1" is for fast computers, "2" is for slightly slower computers, and "3" is for even slightly slower computers. If you still experience lag beyond these limits, you probably will not be able to run the macro. The logon procedure is already as slow and sluggish as I will make it.

This macro was never intended to run on all hardware. Just because I am able to run this macro on my machine that is 1 GHz, 20GB IDE, NVidia 5700 Ultra, 256 MB PC 133, does not mean that I support such a setup...This macro is very CPU dependent. It runs noticeably slower on my 3.0 GHz than my 3.4 GHz machine...

On another note:

As far as ship support or addon features...I just added 2000 lines of code with bug testing within the last week to satisfy those requesting JetCanning/Hauler support...This in itself, was an amazing feat...anyone can make a simple routine that mines to a can, this is not the same...You can't even begin to imagine all that there is under the hood of this macro. In six months time, few or none of you will ever use all of it's features... Getting back to the point of ship types...Ship types WAS going to be more exclusive...but at the present state, ship type controls one and only one feature...and that is whether the macro approaches an asteroid by orbitting for large ships, or approaching straight on for frigates. For god's sake, if you have a large unsupported ship, just choose an industrial, if you have a small ship, just choose a frigate, or whatever...

Notes on instadock support:

Maybe...but low on my list...I still have yet to give JetCanning/Hauling my 100% perfected seal of approval...and I have numerous projects just to update the help system...

Notes on Barge/StripMiner Support:

Maybe, but also low on my list...I have weeks to go yet before I even reach the skill level to use the equipment...Why...because I'm so buried in code that I haven't even had the chance to play for almost 3 weeks, outside of a few bugtests...I seriously haven't even had time to log in on characters and check their skills...

Basically, if I have to spend 40+ hours a week in this forum trying to guess why someone's rocking hardware lags out and can't run a macro that has already been tested successfully on numerous system configurations, then it is unlikely that new features are going to be developed...

Note to self:

Been here too long already, back to coding...

Upallnite

I just want to let you guys know, the creators of this script are pioneers of the eve empire. I finally got it to work and the script and the game itself works flawlessly, no lag, no bs. I dont know why you guys recieve lag my setup is the following if you guys are curious and maybe will put $$$ just to get this script going, its definatley well worth it, made millions last night after 1pm here.

4000+ amd 64
1 gig low latency corsair pro
2 6800 ultra oc pci-x on SLI
1 raptor 10,000rpm hd


I do notice that it takes up cpu power, i have a waterchill cooling system and when it loads, i hear the cpu give out extreme amounts of hot energy through the water. but my cpu manages to be under 110F. Good luck you guys and get the script working it f0kin kicks !@#$%^&*

On a lighter note...

I am familiar with using "relative" window mouse settings, if that was what you were inferring...I originally started macro rewrite for Cold War Edition using relatives, but hit a snag with python code not being recognized at times by windows as a proper windows op...Window calls were failing...Sometimes, window existances were reported by windows after windows had ben closed also...I was forced to incorporate different levels of window logon op checks/crash detects that put me in and out of relative settings, I was almost forced to write 2 sets of code, one if window was there, one if window wasn't...again...with all the alpha channel stuff, and moving animated backgrounds, detecting logon windows was not as easy as it looks...I decided to give up on using relatives, but DID incorporate X_OffSet, Y_OffSet code so entire macro can be moved accordingly...The X_Y_OffSet Module does exactly the same as running relatives, but it still does not run on all systems...We have yet to see any problem system, where a simple game environment move solved all the window issues...

Thus, if someone's entire game environment is off by 2 pixels right and 2 down, macro CAN be set to run fine...but that is not the crux of the problems we face...We are faced with menus that pop up out of normal position for equal game environments(aka WarpTo Menus), we are faced with text display in different windows being displayed at different font sizes (aka Tutorial Problems), we are faced with EVE interface text overlay issues, where text is overlaid in different positions for different computers...(aka Warping text in ship console)...

Obviously it is possible to write a simpler macro that will mine...but MAX-COTE is not a simple macro...If I were to strip it of INFO checks, CRASH Detects, Random Wait adjustments, AUTO Logon, Stealth time checks, Pirate Detection, Ore Detection, State Checks for AfterBurner, ArmorRepair, POD Detection, Shield State Detection, Armor State Detection, etc, etc, etc, then yes the macro would probably run smoother on lesser hardware...

But it would not be an AUTO Logger, it would fail at anyone of hundreds of snafus in the game, you would lose your ships, and it would not run without monitoring for even one day...without ship loss...This WAS intended and designed so that a new pilot with a starter frigate can mine in 0.5 space effectively. It was designed so that someone with an Apoc/8 lasers and a occator cann JetCan/Haul Mine effectively in any space...

Believe it or not, this macro did start simple, every addition was made for a good reason. I did and do not expect to fullfill everyone's wishes...Obviously someone wanted to merely solo mine in 0.9 space is going to be carrying a bit of extra baggage in the macro to fullfill other agenda's...This was already stated openly...

Basically, this macro was and is designed for me...this is not a "Public Service" and I am not a "Public Servant". I do not gain anything from Tault, for this, not even membership...

I didn't write the JetCanner Code because of public Outcry for JetCanning, I wrote it because I make more ISK that way...

I had trouble with the first incarnation of this macro for over a month, of constant ship loss, loop stuckage, macro stops, crashes...all due to unexpected game interference because of a shortcoming in the design of the game, not because of the failure of the macro code...After I wrote the last workaround, the macro ran over a month, non-stop...

Not that I was truly that interested in a non-stop macro, since you do have to stop it once in a while to train skills...(thought about it...nah...we have enough already...), but I did want one that overcame all interference from the game...If I wanted to run the macro for most of a day to make up for a lost ship, I wanted the macro to run non-stop...

Most of my use is as an aid anyways...I never run the JetCanning Code unattended...Not that the code isn't good, it's just young,...and now we have new interference problems from griefers, and such...

Even the JetCanner Code is complex...Yes, you can code a simple macro procedure to spit a can, and go manually with a hauler and pick it up...but this macro can JetCan a System for hours...and will operate a Hauler in AUTO, who will sweep the system, and cleanup all the cans in the system ONLY from your JetCanner...

This macro gives you the choice to mine ore simply by ore type, or by ore density...for the more common ores...to optimize the mining for those starting out, or with smaller CargoHolds...

ETc, etc, etc,...

Upallnite

hey bud... it works. it went through 1 successfull undock, mine, dock. One question for you. After veldspar, if I want to switch to kernite or some other source, in which manner is it best to configure the script you have made. Edit through the script edit utlity in the macro scheduler or using the gui interface on your max cote? Im thinking about mining kernite. Also do types of ships matter?


BTw... your teachings and the future to see a awesome mod for eve inspires me, I appreciate all your responses and it really opens ones eyes how this can be done. I read down your script youve made over and over again and each action your script makes in the game I overview it in the script to see the commands you inputted, quite interesting.


Ah yes one more thing... to stop the script to make those adujustments... I press the preset stop command which is "shift-esc" is that preffered, or does your script have anomolies when that command is used?

crashergs...

Technically, every monitor is different, CRT's seem to be the most stable, but LCD's the most accurate...but since all lcd's have such varying default resolutions, and non-default resolutions cause the monitors to "scale" pixel location differently...it is possible to have small scaling issues...We have not had a wealth of info to sort into preferred monitor types, or problem brands, etc...Monitor drivers as such are not really drivers as much as simple spec files...most features are handled by DDC nowadays...

SHIFT_ESC is what I use, without issues...only works if you start macro with shortcut key though.

Upallnite

crashergs...

Yes, there is code in the warp detect module, that also checks for the speed indicator to hit full speed, if not within say 90 secs, it times out and logs, to free up ship and continue...(So as to not have your ship destroyed in case of evasion attempt...)

We try to use Orbitting Approach for the larger craft, to break out of the "plane" of the asteroid field...In case you haven't notice, as big and expansive as EVE is, it's 3D galaxy or universe is quite planar...We stop the ships, to try to avoid diving too deep back into the asteroid field "plane"...That's why we don't recommend MWD's...just a little too much power in the Fields...got stuck more often...

Once we officially deal with barges, we will also deal with speed issues for them separately...

Remember that while you should have vClear_Cache=YES for your first startup, as long as the startup seemed ok, you can then quit...edit the MAX_COTE.ini file and change vClear_Cache=YES to =NO...This will save you resetting on every relog...In times past...we kinda pressed for clearing cache more often to stabilize and insure non-corruption of window setups from game interference, but it has improved tremendously...

Upallnite