Forum Replies Created
-
Posts
-
To link grids have a common waypoint in each Grid. I have a few setup like this for gathering purposes.
In Grid1 my character flies to waypoint10, grid then changes to Grid2 and has a waypoint20 exactly where Grid1’s waypoint10 was. If you don’t have a common waypoint your character will travel to the nearest waypoint in the new grid, this can lead to unexpected results.
Going between zones can be done using zoneGate(). After you zone-in call the new grid and go to your destination waypoint.
Learning complex scripting can be done by looking at other scenarios that are available. The ? (Question Mark) on the Scenario tab has all of the commands defined. For new scenarios, I find writing out a high level overview helps me keep track of what I want to do. I build and write my scenario based off my notes, I frequently copy repeated strings from other scenarios to prevent reinventing the wheel.
I breakup single goals into multiple chapters such as Traveling/Presets, Gathering/WorkUntil, Maintenance(Desynth, Repair, Reduction), Next Goal/Repeat. This helps keep things tidy and allows resuming scenarios without having to go through a single chapter with 50 steps. I rarely have more than 8 steps in a chapter, if I do they have remarks. Remarks are skipped lines in scenarios, they let you make notes or have alternate configs on standby. Remarks are added by preceding a line with //
-
This reply was modified 3 years, 7 months ago by
PinHead.
Hello! I think I may have discovered a bug with the bot or possibly the gathering/crafting scenario generator. I am a new user so I am not sure if this is intended behavior or not.
I was having the bot farm darksteel ore. Because I needed it for the ingots. I used the scenario generator to build a scenario. I press the button to start. Even though the node had not poped yet the bot teleported to the area and proceeded to sit at the aetheryte spamming actions to find the node that in fact was not there. Eventually at the correct time the node spawns the bot then went and gathered.
Is this intended behavior?
Definitely intended behavior. Having gather() run with Compass enabled in the Gathering Preset will spam until the node pops. This makes you look very suspicious. Using an afkuntil() as Lyfox suggests will solve your spam problem. I suggest you expand your gathering scenario to include gathering other valuables and maybe a little fishing here & there.
Seems to work pretty well, only issue I have is that I use this for points, so having the patience 2 is really not optimal, double hook would give way more points. Is it possible to change that somewhere or how is it determined if patience 2 is used or not?
Also it does not use cordials, so using those would also help very much.nvm I’m just dumb and did not notice the new fishing presets, edited them all good now.
What edits did you perform? I enjoy this scenario very much but it definitely has its limitations due to the Preset configs.
Because the people I shared it with did not change the grids and as luck would have it some of them were on my server. So occasionally I would find myself fishing right on top of them or following the same damn grids. This is why I help with one off requests in the form of lets help you learn Scenario scripting instead of just GIMME GIMME GIMME.
Then I would say it is a grid issue and editing it would probably work for you.
Editing isn’t too difficult. Open the Navigation tab and click the Editor toggle. When you click it your game border will highlight Green/Red and the Grid is illuminated.
In the upper left corner are the Editor instructions. Ctrl on the keyboard controls editor mode Green/Red border of game screen. Green is to add and pickup/drop a waypoint, Red is more for removing, connecting waypoints & lines but also editing lines to add a waypoint or editing waypoint characteristics such as Fly, Foot etc. When in Red mode some your basic keyboard commands will be hindered, this can become frustrating at first.
I suspect the beginning of your grid has waypoints on the ground, or an initial waypoint in the air needs to be switched to the Fly type.
-
This reply was modified 3 years, 8 months ago by PinHead.
I built a Simple Scenario that will walk you through some basics.
First thing is to import the scenario, Scenario tab > Share > Import.
Next, enable “Show On Radar” on the Navigation tab to show you the grids and how they work.Included in the Scenario are:
– 2 Waypoint Grids
– 1 Gathering PresetThis scenario will:
*Chapter 1
– Teleport you to Limsa Lominsa Lower Deck Aetheryte.
– Proceed out the gate to Middle La Noscea.
*Chapter 2
– From there it will change your Job in game and the Gather Preset in Miqo.
– The Gathering Preset will change the Grid and setup your gathering rotation.
– Now it will navigate to a set of low level gathering nodes. I am gathering Fire Shards here.
*Chapter 3
– The scenario will then hit 10 gathering nodes and perform the rotation if enough GP is available.
*Chapter 4
– After 10 nodes have been hit the scenario will now proceed back to Limsa.
– After zoning, the grid is changed and you proceed to the Aetheryte.Second question:
I believe the problem you are experiencing is either you can’t fly in the zone or you haven’t modified your grid to allow flying. One of the most difficult things are creating proper grids that incorporate your own style of gameplay. Some scripts have a Fly and corresponding Foot node to control mount usage. My example doesn’t do that but uses a repeatchapter() with a mount() command in Chapter 3 so my character gets to each node quickly, if flying is necessary I have my Fly nodes stationed to allow that.Like Lyfox said there are many scenarios available that can help you, the problem is you may have to modify them to suit your needs. Since the game changes often some of them are now outdated or are useless except as examples. Examples are good though and will help you.
The best way for you to get what you want is to make it yourself. With that said this request seems like a fairly simple and straightforward scenario. The scenario I created for this is based in Mor Dhona. Find each node, Mining & Botany, and then create a navigation grid to each of them with a centerpoint being the small village. Make a gathering preset and write your scenario.
I would suggest going with the robber balls and ignoring the cordials. Fishing is the most GP efficient activity, when it comes to collectables. If you compare the cost of a cordial to a robber ball you burned trough cordials worth 1000+ baits, which you could have gotten way more than just 300 aethersand from, probably in shorter time too.
I tried the Robber Ball route and I disagree with you, using Versatile Lure + Cordials achieved the exact same results in a 30 minute time period and I didn’t have to buy the bait. Also, obtaining Cordials/Robber Balls is just another scenario so the cost of either is negligible due to Miqo doing the work. Time though; my cost of time is different when I am at the keyboard vs. not at the keyboard. I would never run this while I am at the keyboard due to the slow farm rate, however I would run this on my side desk while I’m working.
I use a Versatile Lure instead of the Robber Ball bait. You will wait twice as long for the bite but will get roughly 3 Bloom every 10 minutes. I used 100+ Hi-Cordial and received over 300 aethersand. This took hours of botting to achieve.
Efficient? I don’t really think so but when the result was 300 more sand than when I had started I stopped wondering.
Here is what I found today, it is a Google Doc. It contains rotations for Collectables & explains the gathering process much better than the game does.
Since most nodes have different stats a static macro will not take advantage. Breaking your macros up into smaller groups may prove more fruitful to you.
-
This reply was modified 3 years, 7 months ago by
