trading
/
PTMagic
mirror of https://github.com/PTMagicians/PTMagic.git
2
0
Fork 0
Code Issues Releases Wiki Activity

Changed trigger Letter to Tag

This commit is contained in:
HojouFotytu 2024-01-29 18:50:32 +09:00
parent a54f819182
commit f54109a3b3
4 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Core/DataObjects/PTMagicData.cs
View File

@ -201,7 +201,7 @@ namespace Core.Main.DataObjects.PTMagicData
public class Trigger
{
[DefaultValue("")]
public string Letter { get; set; } = "";
public string Tag { get; set; } = "";
[DefaultValue("")]
public string MarketTrendName { get; set; } = "";
@ -228,7 +228,7 @@ namespace Core.Main.DataObjects.PTMagicData
public class OffTrigger
{
[DefaultValue("")]
public string Letter { get; set; } = "";
public string Tag { get; set; } = "";
[DefaultValue("")]
public string MarketTrendName { get; set; } = "";

2
Core/Main/PTMagic.cs
View File

@ -1344,7 +1344,7 @@ namespace Core.Main
{
double averageMarketTrendChange = this.AverageMarketTrendChanges[marketTrend.Name];
bool isTriggered = averageMarketTrendChange >= trigger.MinChange && averageMarketTrendChange < trigger.MaxChange;
triggerResults[trigger.Letter] = isTriggered;
triggerResults[trigger.Tag] = isTriggered;
if (isTriggered)
{

14
PTMagic/_defaults/_default_settings_PT_2.x/settings.analyzer.json
View File

@ -71,20 +71,20 @@
{
"SettingName": "EndOfTheWorld", // ANY UNIQUE name of your setting
"TriggerConnection": "AND", // Define if triggers will be connected by AND or OR.
//If you give each trigger a letter, then you can use more robust boolean logic, such as: (A && B) || (B && C)
//If you give each trigger a Tag, then you can use more robust boolean logic, such as: (A && B) || (B && C)
"Triggers": [ // Your triggers for this setting. You can use any of your defined trends from above
{
"Letter": "A", // OPTIONAL: Give your triggers letters, so you can use more robust boolean logic, such as: (A && B) || (C && D)
"Tag": "A", // OPTIONAL: Give your triggers Tags, so you can use more robust boolean logic, such as: (A && B) || (C && D)
"MarketTrendName": "1h", // Reference to the market trend specified above
"MaxChange": 0 // The maximum value for this trigger. (Any value below "0" will trigger this)
},
{
"Letter": "B",
"Tag": "B",
"MarketTrendName": "12h",
"MaxChange": -2
},
{
"Letter": "C",
"Tag": "C",
"MarketTrendName": "24h",
"MaxChange": -5
}
@ -276,7 +276,7 @@
"TriggerConnection": "A || B || C",
"Triggers": [
{
"Letter": "A",
"Tag": "A",
"MarketTrendName": "1h",
"MarketTrendRelation": "Relative", // The relation of the single market trend. Relative = The trend of the coin market
// is compared to the average trend of all other coins in the market market.
@ -284,13 +284,13 @@
"MinChange": 8
},
{
"Letter": "B",
"Tag": "B",
"MarketTrendName": "12h",
"MarketTrendRelation": "Relative",
"MinChange": 10
},
{
"Letter": "C",
"Tag": "C",
"MarketTrendName": "24h",
"MarketTrendRelation": "Relative",
"MinChange": 12

14
_Development/DevSettings/settings.analyzer.json
View File

@ -71,20 +71,20 @@
{
"SettingName": "EndOfTheWorld", // ANY UNIQUE name of your setting
"TriggerConnection": "AND", // Define if triggers will be connected by AND or OR.
//If you give each trigger a letter, then you can use more robust boolean logic, such as: (A && B) || (B && C)
//If you give each trigger a Tag, then you can use more robust boolean logic, such as: (A && B) || (B && C)
"Triggers": [ // Your triggers for this setting. You can use any of your defined trends from above
{
"Letter": "A", // OPTIONAL: Give your triggers letters, so you can use more robust boolean logic, such as: (A && B) || (C && D)
"Tag": "A", // OPTIONAL: Give your triggers Tags, so you can use more robust boolean logic, such as: (A && B) || (C && D)
"MarketTrendName": "1h", // Reference to the market trend specified above
"MaxChange": 0 // The maximum value for this trigger. (Any value below "0" will trigger this)
},
{
"Letter": "B",
"Tag": "B",
"MarketTrendName": "12h",
"MaxChange": -2
},
{
"Letter": "C",
"Tag": "C",
"MarketTrendName": "24h",
"MaxChange": -5
}
@ -276,7 +276,7 @@
"TriggerConnection": "A || B || C",
"Triggers": [
{
"Letter": "A",
"Tag": "A",
"MarketTrendName": "1h",
"MarketTrendRelation": "Relative", // The relation of the single market trend. Relative = The trend of the coin market
// is compared to the average trend of all other coins in the market market.
@ -284,13 +284,13 @@
"MinChange": 8
},
{
"Letter": "B",
"Tag": "B",
"MarketTrendName": "12h",
"MarketTrendRelation": "Relative",
"MinChange": 10
},
{
"Letter": "C",
"Tag": "C",
"MarketTrendName": "24h",
"MarketTrendRelation": "Relative",
"MinChange": 12