Jump to content

Spaceguy911

Beta Tester
  • Content count

    115
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Spaceguy911

  • Rank
    Silver III

Recent Profile Visitors

450 profile views
  1. Any opinions on this? I feel it's very important, personally...
  2. Running acts, yeah. not mapping. if nothing in inventory, and chaos recipe activated, it will go straight to stash at login. and from tp (at end of runs), it will run straight from TP to WP. so suspicious. Then it stands there for the same amount of time (every time) as it selects the zone. Would prefer it does /hideout, anytime it's in town, then does what it needs to do. Go to WP from /hideout.
  3. There are many instances where on loading (e.g. if I need to manually restart due to a patch, update offsets, download a new EB version, or simply just if my PoE crashes and the game restarts), where the bot will load into town, and then run right to the stash, then go to the waypoint and select destination (this is true for non-map runs). What I believe is happening is a system check, and this happens when nothing is in the inventory to sell. The bot will go to /hideout if it needs to sell (and possibly even stash). So as of now, the will (I'm assuming) check if items in inv to sell/stash, then go to stash to check chaos tab (if selected), then run back to the waypoint and select zone. I don't want this, this is sketchy as f***. I don't think the bot should be running in town EVER, under any conditions, if you have "/hideout" option selected. First thing it should do when it goes to town (either from TP or Login) is "/hideout". The bot needs to get out of the eye of the public, IMMEDIATELY. I want the bot to first check "is hideout selected" EVERY time it enters town (TP or Login). If it's selected, the FIRST thing the bot does is "/hideout". Seriously. This is important. I'm watching the bot right now too. If again, it doesn't have anything to sell or stash, and the run ends, he will TP to town, and runs to the waypoint, and select a new zone to run (if someone's sitting in town and sees this happen a few times over and over, they will report it). I don't like this. I want him to go "/hideout" AS SOON AS he enters town. The bot running around town is a surefire way to get banned! The bot's movement in town is sooo suspicious. And people are onto it now. If there's a Dev in the town, it's likely an instant ban. If there's a relatively experienced player in town (and by now there's a lot of them), they WILL report you. Especially with all of the reddit posts coming out about bots, and the videos of them too. Especially if you're running multiple, and ESPECIALLY if they have the same gearsets/unique items that are recognizable. People notice this pretty obviously... Please consider this change. Thank you. It's just stupid added risk, and seems like it could be fixed by prioritizing /hideout.
  4. Did Discord server crash?

    It's back up.
  5. Did Discord server crash?

    My Discord is working (other channels), but I'm no longer in the EB Discord. Tried clicking the Invitation Link from e-b.net website, but it wouldn't load to server.
  6. Title kind of speaks for itself. I was watching the bot a second ago and he found a Unique Strongbox. (now I don't open strongboxes just because they're too RIPPY sometimes - but I'd like to go do the Strongbox on my main. Hell, it could be a Kaom's Heart!).
  7. Does this mean that it's something in your queue to work on, or are you indicating that GGG would need to incorporate more/specific detail on their side about the "real name" before you could even consider adding this feature? Just trying to understand expectations. Thank you.
  8. I love that GGG keeps adding uniques, but it gets the \\UNIQUE\\ section of the pickit VERY messy. You run the risk of a) missing really good items, or b) picking up a bunch of trash! I'd like, if possible, for the incorporation of a [Name] syntax. This might have to come after the item has been "#" identified. [Type] == "Occultist's Vestment" && [Rarity] == "Unique" # [Name] == "Shavronne's Wrappings" && [StashItem] = "true" // Shavronne's Wrappings Saves Shavronne's Wrappings and sells any other Unique Occultists Vestment (e.g. Infernal Mantle). I think this would be HUGE, mainly because with GGG adding so many new uniques every league, it's very difficult for us to separate from same-type items!! To do this, you need to find a parameter to separate the particular item. And you never really feel comfortable that you have the right parameter to separate, plus it's a LOT of time and work. Examples!!!! Here are examples of parameters you would need to look up and learn/know if you wanted to save a particular unique: [cannot_be_stunned] >= "1" [all_attributes_+%] > "10" [movement_velocity_+%_while_ignited] >= "10" [local_unique_jewel_nearby_disconnected_passives_can_be_allocated] >= "1" [damage_over_time_+%] >= "10" [base_maximum_mana] >= "1" [cold_damage_+%] >= "1" It's very cumbersome in its current state. With each unique you want to save that has more than 1 Type (or even if GGG might add another unique type in the future), you need to (a) look up all same-type uniques, and identify how your saved-unique is different from an affix/parameter perspective, then (b) search and find that parameter, and (c) code it into your pickit, and then (d) monitor all of your saved uniques and cross reference them with each introduction of a new unique to ensure you're still saving the proper uniques. To take it a step further, (e), when GGG rebalances uniques, in the current state of how pickit works, you would need to go back and check to make sure any of your saved-uniques were not changed by the balance, and if they were changed, go back to step (a)... This needs to happen for every unique item you want to save. Conversely, [ForceSellItem] worked at one point and was great, but now there are just too many uniques, [ForceSellItem] is almost more work than [StashItem] at this point - because again, you need to follow the above (a) - (e) steps for every single unique item you want saved... Including a [Name] feature would fix this problem in a second. Can I get a yes/no on if this is possible from the meta data of the identified item? Thank you.
  9. Bot Alerter - Custom Field

    Redirected from my thread to here. Yes I like this. We'll see, hopefully we can get it. My examples were: "Add alerts for Scorn, Envy, Misery, Dread"
  10. Have bot buy Elreon rings daily from Elreon?

    Agreed. Ty. Edit: Just thought I would float the idea, in case it was like a super easy implementation. But I agree, probably not much demand for this feature. Thx.
  11. 3 bots banned simultaneously

    All I can say is that GGG has done something new in teh past 3-4 weeks. I run a handful of bots, and only 1 was banned about a week ago. This account was about 2-3 years old, is the weird part.
  12. Is this possible without too much investment of time? If hideout, if Elreon is in hideout, if Daily Mission available: Launch daily mission. Type /abandondaily, interact with Elreon, find: ring/amulet, must have "Elreon's" prefix. Purchase. Don't check elreon for ~12 hours, or if bot has an internal clock: until next reset time.
  13. Thanks. still think this would be good
  14. These 4 Essences are quite rare, but when the Remnant of Corruption item is used on them, they have a chance of rolling the T1 Essences, which can only be obtained through this method. These item prices range in value from 15-50c. I realize that Alk and the Dev team works very hard and is staying busy, but I just wanted to add this suggestion to the list, for future added features. Thanks.
  15. Edit: This might be nit-picky, but the "Character Slot #" option has given me issue for quite some time. Maybe I'm in the minority, but I've been botting for quite some time now, and some of my accounts have many characters. If the character I want to bot with is far down in my character list, it can get buggy, in addition to taking up additional time on relogs/crash restarts. I try to fix this by always having the new character's name starting with a letter earlier in the alphabet, since the char list is sorted alphabetically. This ensures that my newest char (for the new league) is always at the top, in position 1. But if "League Select" was an option, the bot could select the league, and then the character position in that league. Likely only 1 position, but could be a couple I suppose, for the average player. For example, my current character is in character position 12. Getting to 12 can be buggy. But he's my only character in "Standard Harbinger" league. So I'd like to have the bot choose "Standard Harbinger", and then Character Position 1.
×