• #1653

      Firetron == Burning away the chaos one work day at a time.

    • #1647

      Thanks, easy share, knew many would find handy, more very soon, if you want to test, see something else, just DM me.

    • #1620

      bunka’s import was a Firefox thing, somehow it included white space, all should be fine now

    • #1615

      KABOOM! great!

    • #1114

      So Is this one still doing well guys? (yes chose for a stock commands bot so everything would work and it would not need six or more custom commands…cool stuff but then you better ask or also find my server on discord where I can post everything in one gist or channel . And help you through the many imports of commands and script…

      (my Ichi pretty much always did the job on it’s own, only added overcome fees and there be profits….)
      -I might give this another go myself and see where it takes me..

      Are you guys bored / hungry for inspiration…

      I might need to publish something else?? ^_^

      By the way Id advise you guys to try grow and shrink mods for ProfitTrailer, grow and 1 or 2 rebounds can be great for long uptrends…..shrink to do the opposite

      But it’s really good to know how the growing (and shrinking calculation works as it is related to both trailStartPrc and trailDistPrc.

      Using a trailStartPrc of 12 (half of my standard 24%)and a trailDistPrc of 5 (never mind if you use stuff in front of it that drops it into trailing at 40% and it can drop down to 12…(or start trailing if its a reduced * 0.5 TP)
      yes yes TLDR:
      I wasn’t getting any 200% ROI closes anymore ?? WHY????
      this is why:

      trailMode == “grow”
      multiplier = trailDistPrc / trailStartPrc. my settings: trailDistPrc: 5 / trailStartPrc: 12 = multiplier is 41.67…
      newDist = multiplier * highestRoi newDist= highestROI lets assume my ROI just dropped down to 120% and have rebounds on, (each rebound records previous high and uses new Dist…
      trailStop = 120 – 41.67. (new)trailStop = 78.33% ! on a 120% profit position…!!! Why\oO/_u NOOOOoooo……! wonder I was not closing the 180-230%_ers anymore… and only 40-60%….
      trailStop = highestRoi – newDist

      trailMode == “shrink”
      multiplier = trailDistPrc * trailStartPrc
      newDist = multiplier / highestRoi
      trailStop = highestRoi – newDist. So now have my start at 16 and distance at 2% and gives a multiplier of 0.125 which on a 120(%ROI( gives a new trailStop of 15%… much better……..

      Happy Trailing…
      (P.s.ssst: you could just modify the trail stop calculation so you don’t need a big startperc ( by adding a (0.3 * trailDistPrc) to the calculation in Script Editor where you can edit ProfitTrailer..and get the same multiplier and result)

      • This reply was modified 8 months, 2 weeks ago by Kobalt.
      • This reply was modified 8 months, 2 weeks ago by Kobalt.
      • This reply was modified 8 months, 2 weeks ago by Kobalt.
    • #1041

      chart and backtest..

      • This reply was modified 9 months, 3 weeks ago by Kobalt.
      • This reply was modified 9 months, 3 weeks ago by Kobalt.
    • #2012

      Ok just to drain the regular folks talk out of you | show how little I know | try to bridge the gap between:

      what is obvious to you and is still very vague territory to many…
      Would using this instead for every Input make sense?
      In the sense: Can’t hurt to always use SuperInput vs regular Input.

       if SuperInput "only makes things faster never slower" then
      Upgrade the default Input command: to enhanced (super)Input.
      return Input
      If super is not always better then
      Log [array content}

      Please list some Inputs everyone uses: [categorise or label as I, Input or SI, SuperInput]
      So users who are not the king, tron or the wizard.
      Get a still not set in stone but better idea which “stuff” calculates and whatever magics..
      And may or may not qualify for using SuperInput over regular Input.

      • This reply was modified 2 months ago by Kobalt.
    • #2011

      It doesn’t??

    • #1704

      Is there a way to check if a CC or calculation in some part of your script is slowing down execution or resources used per command dependency.
      To find things SuperInputs would improve, or to avoid in general or any other way avoid sluggish execution?

      Maybe there are common bad practices an optimisation check script could detect.
      [These are more inspirational than straight questions. I assume something like this doesn’t yet exist. Unless I’m over complicating this and theres a check list or simple way to do this..:)]

      Your example makes me curious what might benefit here, can you give an obvious/notorious example? (Interval, VWAP reset loopback those kind of things?)
      And SuperInput works in running HaasBots so can maybe help people running 50+ scripts?

      • This reply was modified 4 months, 3 weeks ago by Kobalt.
    • #947

      Oh cool,
      SAR is high on my list…
      Did you use the extended version of SAR?

      Looking at this bot two things stand out to me:
      This bot is a stripped of all custom commands version of an original setup by Seaside420:
      And a variation on this he shared with me using 2 double delayed HMA crossings

      Hull MA is missing here entirely as it’s also a CC_, but due to them not being there it makes for interesting inspiration when I look at this again..
      Curious when looking at VolRSI and CCI how one of his recent creations would fair:
      Or a RSI+ROC+CMO type blend…..

      I would love to see what you made from this. (DM me on Discord and will send you cc versions)

Viewing 5 reply threads

Unlock your crypto trading potential

Create a free account and enjoy everything we have to offer.

Join for Free