ASO Money Maker by Bruno Moscan

9 小時前

Here’s a natural, human-style explanation you can use:

---

The **ASO Pro (Average Sentiment Oscillator)** is a momentum-based indicator designed to measure the balance between buying and selling pressure in the market. It works by analyzing both intrabar price behavior and grouped price movement over a defined period, then smoothing the results to create two lines: a blue line representing bullish strength and a red line representing bearish strength.

When the blue line rises, it indicates increasing buying pressure. When the red line rises, it reflects growing selling pressure. By observing how these two lines behave relative to each other and to predefined overbought (OB) and oversold (OS) zones, traders can better understand shifts in market sentiment and potential turning points.

In addition to showing momentum, this version of the indicator tracks significant extremes. Whenever the bullish line reaches a strong top (overbought condition), the indicator records the closing price of that candle. The same happens when the bearish line reaches its extreme, marking a potential bottom. It then calculates the average of the most recent selected number of these top and bottom prices (for example, the last 5 or 10 occurrences, depending on user preference).

These calculated averages are displayed directly on the indicator panel:

* The average price of recent tops appears in the upper-right corner.
* The average price of recent bottoms appears in the lower-right corner.

This gives traders a dynamic reference of where the market has historically peaked or bottomed according to momentum conditions — helping identify potential support and resistance zones based on real sentiment extremes rather than arbitrary price levels.

In short, the ASO Pro combines momentum analysis with practical price-level tracking, offering both directional insight and actionable reference levels in one tool.

9 小時前

發行說明

Sure — here’s a natural, human-style explanation in English:

---

This script creates a custom oscillator indicator called **“ASO Money Maker”**, designed to measure buying and selling pressure and identify potential market tops and bottoms.

At its core, the indicator calculates two main forces:

* **Bullish pressure (blue line)**
* **Bearish pressure (red line)**

It does this by analyzing both the current candle (intrabar movement) and a group of past candles over a defined period. The user can choose how the calculation works:

* Average of intrabar and group data
* Intrabar only
* Group data only

After calculating raw bullish and bearish strength values, the script smooths them using a simple moving average. This reduces noise and makes the oscillator easier to interpret.

---

### How Tops and Bottoms Are Detected

* A **top** is identified when the bullish line crosses above the upper threshold (default: 80).
This suggests strong buying pressure that may be overextended.

* A **bottom** is identified when the bearish line crosses below the lower threshold (default: 20).
This suggests strong selling pressure that may be exhausted.

When these events occur, the script stores the closing price of those candles in arrays.

---

### What Happens Next

The indicator keeps track of the most recent detected tops and bottoms (based on a user-defined quantity) and calculates:

* The average price of recent tops
* The average price of recent bottoms

These averages are displayed in a table on the chart, giving the trader a reference level for where price tends to peak or bottom out.

---

### What You See on the Chart

* Blue line → Bullish pressure
* Red line → Bearish pressure
* Dashed horizontal lines → Overbought (top zone) and oversold (bottom zone) levels
* A panel showing average top and bottom prices

---

### In Simple Terms

This indicator attempts to:

* Measure internal buying vs. selling strength
* Detect extreme conditions
* Store those extreme price levels
* Provide average reference zones for decision-making

It’s essentially a structured way to quantify momentum extremes and turn them into actionable price reference levels.

9 小時前

發行說明

Here’s a clear, human explanation of what was changed and why:

What Was Wrong Before

Previously, tops and bottoms were detected using crossover() and crossunder() logic. That means the script was looking for the oscillator line to cross a level from one candle to the next.

The problem with that approach is:

It depends on the previous candle.

It can behave inconsistently depending on smoothing and settings.

In some configurations, both conditions could trigger very close together.

It wasn’t truly detecting a “touch” — it was detecting a crossing event.

That’s why you were sometimes seeing the same closing price stored as both a top and a bottom.

What Was Changed

The detection logic was rewritten to follow your exact definition:

A top happens when the blue line reaches the OB level.

A bottom happens when the red line reaches the OB level.

What matters is the candle’s closing price at the moment that level is touched.

Instead of using crossover() or crossunder(), the script now checks:

Whether the value is greater than or equal to OB

And whether the previous candle was below OB

In simple terms:

“If the line just reached or touched OB right now, but wasn’t there before, record this candle.”

This makes the detection:

Objective

Based strictly on contact with the OB level

Independent of crossing behavior

More stable across configurations

Why This Fix Works Better

Now the script:

Detects the exact moment the oscillator touches the dashed OB line.

Records that candle’s close only once.

Avoids repeated triggers while the line remains above OB.

Separates the logic for blue (tops) and red (bottoms) cleanly.

There is no interpretation involved anymore.
It’s purely mechanical: touch OB → record close.

One Important Note

If both lines touch OB on the same candle, both will still be recorded — because mathematically, that event actually happened. At that point, it’s not a bug; it’s just the oscillator behavior under those parameters.

In short:
The script was changed from “detect crossing behavior” to “detect precise contact with OB”, exactly the way you described it.