chumpits2

Forum Replies Created

Viewing 1 post (of 1 total)
  • Author
    Posts
  • in reply to: Tips for smoothing out movement credibility? #38764

    chumpits2
    Participant
    0

    I’ve thought on this quite a bit and have noticed a few major things. I would say the biggest and most important question to ask yourself is, “Does the route look like what I’d actually be doing?” You’re not going to run around like a PacMan demo, you’re going to aim yourself directly at the next spot and auto-run. You’re not going to mount up and fly to a node you can reach in five seconds on foot. The best possible thing you could do is go and gather at a location for a while normally in edit mode, setting up waypoints as you go. Aside from keeping your waypoints different from everyone else’s, this also has the benefit of mirroring your own personal habits. “Do you usually run to the left or the right of that tree that’s in the way”, as an example.

    One of the biggest give-aways is using the compass abilities. Remember, “you’re not a bot”. It’s ridiculous to think you wouldn’t know where the next node is at after a while, even when they spawn far enough away to not be seen on the minimap. Anyone even passingly familiar with bots or the gathering location will know you at a glance if they stick around a bit to watch(and it’s other players narcing on you that cause the majority of investigations). It also leaves a giant time-stamped tell in your logs, should the staff look at them. In short, you should never ever have the compass options enabled. Of course, this is a problem for some nodes since the next one won’t spawn close enough to be loaded into memory where miqo can see it.

    I’ve found a couple workarounds for that. The first, somewhat inelegant one, is to make a large circuitous route with a beacon that miqo can latch onto coming from the out-of-range spot. Depending on your grid and node spots, there may be issues making sure she goes the right direction, doesn’t see a future node and try to go there first, or doesn’t start trying to loop between beacons if you have more than one. Ideally miqo would choose targets based on total grid line travel distance and reevaluate at every waypoint, but that’s not the case, so you have to figure out how best to nudge her for your situation. The other method is to use a scenario for problem locations instead of relying on the basic gathering function. This is more complicated to set up, but offers a superior granularity of control that bypasses potential quirks.

Viewing 1 post (of 1 total)