Requires 2 XXB or XBX ports, obviously Equ makes the most money.
SSM: Sell-Steal-Move
1. Port and Sell Equ/Org
2. Port and Steal Equ/Org
3. Move to 2nd Port
4. Port and Sell Equ/Org
5. Port and Steal Equ/Org
6. Move to 1st Port
Repeat until busted or out of turns.
* Requires 2 XXB or XBX ports, obviously Equ makes the most money.
However the first thing we will need is Equ or Org in holds initally...
Then we should be able till you get busted (which takes holds, inventory, and some exp)
However the first thing we will need is Equ or Org in holds initally...
Then we should be able till you get busted (which takes holds, inventory, and some exp)
Ok in [949c2e90d5] we now can handle if the user doesn't have Equ in holds then move to the nearest port and grab Equ... (Also handles if the user other things in holds, or doesn't have all the holds with Equ)
Still need to get nearest port pairs that are XXB to XXB in order to "evilTrade" with them.
Ok in [949c2e90d5] we now can handle if the user doesn't have Equ in holds then move to the nearest port and grab Equ... (Also handles if the user other things in holds, or doesn't have all the holds with Equ)
Still need to get nearest port pairs that are XXB to XXB in order to "evilTrade" with them.
I need to grab what a bust looks like, so we can at any time we see that, stop going to that port... possibly look into adding it to galaxy.py so it can add them to avoided ports/ports not to go to.
I need to grab what a bust looks like, so we can at any time we see that, stop going to that port... possibly look into adding it to galaxy.py so it can add them to avoided ports/ports not to go to.
In [7ba939c1f1] we have changed galaxy.py so we don't give ports that are in the bust list.
Still left to do is the find_nearest_evilpair() and find_next_evilpair().
In [7ba939c1f1] we have changed galaxy.py so we don't give ports that are in the bust list.
Still left to do is the find_nearest_evilpair() and find_next_evilpair().
[7b3084031a] adds automatic detection of a bust... so we add it to the bust list.
Up next... changing the bust list to a dict so we can track when the
bust occurred, so we can process what busts need to be cleared out.
(And yes still need to get find_nearest_evilpair() and find_next_evilpair() for the real trading)
(Also need to figure out how to keep track of when busts were cleared)
[7b3084031a] adds automatic detection of a bust... so we add it to the bust list.
Up next... changing the bust list to a dict so we can track when the
bust occurred, so we can process what busts need to be cleared out.
(And yes still need to get find_nearest_evilpair() and find_next_evilpair() for the real trading)
(Also need to figure out how to keep track of when busts were cleared)
Because we sell our equipment in our holds then steal it back... unless we are stealing credits then who cares what the port class/type is so long as it has credits to steal.
So the difference is normally you want:
```
XSB to XBS
```
But the evilpair is:
```
XXB to XXB or XXB to XBB
```
Because we sell our equipment in our holds then steal it back... unless we are stealing credits then who cares what the port class/type is so long as it has credits to steal.
My problem is I am using essentially Terror... we do a successful trade then we move on to completely different set of ports... so it's horribly inefficient. (They suggest continuing to sell and steal back until a bust then move onto a different pair, of course you have too then... since if you go to the other one it too will give you a bust)
My problem is I am using essentially Terror... we do a successful trade then we move on to completely different set of ports... so it's horribly inefficient. ([They](http://wiki.classictw.com/index.php?title=Gypsy%27s_Big_Dummy%27s_Guide_to_TradeWars_Text#Playing_.22EVIL.22) suggest continuing to sell and steal back until a bust then move onto a different pair, of course you have too then... since if you go to the other one it too will give you a bust)
Ok, find_nearest_evilpairs looks ok. But I'd probably return both sectors. This isn't quite as easy as Terror/Trading, where once you're in one sector, we can mostly automatically find the matching pair.
Ok, find_nearest_evilpairs looks ok. But I'd probably return both sectors. This isn't quite as easy as Terror/Trading, where once you're in one sector, we can mostly automatically find the matching pair.
SSM: Sell-Steal-Move
Repeat until busted or out of turns.
However the first thing we will need is Equ or Org in holds initally...
Then we should be able till you get busted (which takes holds, inventory, and some exp)
Ok in [
949c2e90d5] we now can handle if the user doesn't have Equ in holds then move to the nearest port and grab Equ... (Also handles if the user other things in holds, or doesn't have all the holds with Equ)Still need to get nearest port pairs that are XXB to XXB in order to "evilTrade" with them.
I need to grab what a bust looks like, so we can at any time we see that, stop going to that port... possibly look into adding it to galaxy.py so it can add them to avoided ports/ports not to go to.
In [
7ba939c1f1] we have changed galaxy.py so we don't give ports that are in the bust list.Still left to do is the find_nearest_evilpair() and find_next_evilpair().
[
7b3084031a] adds automatic detection of a bust... so we add it to the bust list.Up next... changing the bust list to a dict so we can track when the bust occurred, so we can process what busts need to be cleared out.
(And yes still need to get find_nearest_evilpair() and find_next_evilpair() for the real trading)
(Also need to figure out how to keep track of when busts were cleared)
What does evilpair look like? How is it different then tradepair?
So the difference is normally you want:
But the evilpair is:
Because we sell our equipment in our holds then steal it back... unless we are stealing credits then who cares what the port class/type is so long as it has credits to steal.
My problem is I am using essentially Terror... we do a successful trade then we move on to completely different set of ports... so it's horribly inefficient. (They suggest continuing to sell and steal back until a bust then move onto a different pair, of course you have too then... since if you go to the other one it too will give you a bust)
Ok, find_nearest_evilpairs looks ok. But I'd probably return both sectors. This isn't quite as easy as Terror/Trading, where once you're in one sector, we can mostly automatically find the matching pair.