The Spire Option

[weltvagabund]

Have some Code, that reflects following behaviour:
a) Spire on

1. On hitting the Spire go to Map Lvl 200 and get all Equipment
2. Enforce 30 Sec Breeding timer and run the 10 Stacks of Trimps

b) Spire off
Run over the Spire like normal

c) Spire Manual

1. On hitting the Spire go to Map Lvl 200 and get all Equipment and then continue farming and buying Equip /Warpstations/ Tributes/Gyms until user interaction. This is if you want to babysit the script through the Spire to make sure you reach a desired perk.

These optionns would make it a lot easier to run the Spire with more success and catching the script, before it does a Spire Dagger Run :)

[genbtc]

Sorry I am slow on this but it is coming.

[Sciencefreak]

There is a better behaviour which can be implemented.

For a)
run once you can defeat cell 20 for giga upgrade (useful in case you cannot double hit maps)
run bionic wonderland maps to get it to lvl 200 (gives double loot compared to standard map, but less equipment, hence maybe extra option for that)
maybe even run lvl 215 bionic wonderland to get next prestige upgrades
while farming maps, increase breeding timer to expected (might be a user input to make it easy for you) farming time (this gives huge HP boost for spire)

b)if you want to skip it fast (usally best for He/h), decrease breeding time after you died, because with 10 attempts you cannot really go further but you would have to wait 10 times breeding time

c) run Bionic Wonderland lvl 200 or 215 after getting all equipment while waiting

I would like to add a d) which is something between a) and c)

add option for cell aimed (I go up for heirloom each run (cell 70), 60 nullifium (cell 60) would be good if you are lower or 5 bones (cell 90) if you are stronger)
start spire if you are strong enough to defeat the desired cell (similar system to void)

[dklempner]

My opinion here: automating fancy techniques for beating the spire the first time isn't very more useful than automating one time challenges. I'd consider "stop at the spire" (and maybe start running 197-200 maps) and "skip the spire" (firing geneticists) options to be the highest priority items on that front.

The big thing I'm interested in for farming is the impact of the helium bonus on farming for equipment levels. At this point the optimal strategy for multi-billion He players is to dagger climb until dagger climbing peters out, at which point prestiging other equipment up from tier 2 to tier 50ish takes too long to justify.

On the other hand, there's a substantial helium bonus for beating Spire. That bonus might be enough to justify prestiging at least some other equipment up, which would then probably make it make sense to run another couple of zones at the end because of better equipment.

[deusnoctum]

The "skip spire" option could make use of the "skip spire" button that will appear in a few days in 3.5.1:
https://www.reddit.com/r/Trimps/comments/4rlvfz/351_test_server/

[genbtc]

Saw this development

[Jonathonathon]

Wanted to chime in as well. I'm really struggling with the Void Difficulty Check option and finding a number that is a good balance between farm time and time spent on Voids. For option c mentioned above, it'd be really fantastic if we could specify what PrC to farm through for one piece of equipment / level. Then when it hits that upgrade, it starts the Spire. Same with Void Maps. Just wanted to kick in an idea for a different style of implementation, thanks to everyone working on the project.

[Jonathonathon]

One strange thing I've been noticing lately with the "Minutes to Farm Before Spire" option is that after every single completion of a map, auto trimps seems to keep repeat off so it exits into the map screen then goes back into the same map to continue farming. This, of course, resets titimp and wastes a bit of the farming time. Any idea what the cause is?

I just noticed it today and I recently picked up Map Reducer. Not sure if it's related but I figured I'd mention it. Thanks!

[genbtc]

OK, i can tell you are running firefox then, because there was a firefox only bug that I fixed, but in the process, I see now that on line 2191 there is a hardcoded check for making level 200 maps, means that map reducer will be making level 199 maps, and invalidating the logic there. Fixed: genbtc@0c6564b