Difference between revisions of "SkibUserMacros:Defend"

From Protoi Healing

Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
{{UserMacroMainBox
 
{{UserMacroMainBox
 
|nameUserMacro    = Defend
 
|nameUserMacro    = Defend
−
|authorUserMacro  = Drack, Grayfox, Frank
+
|authorUserMacro  = Frank
 
|descrUserMacro  = Defends, blocks and reflects attacks and starts counterattacks.  
 
|descrUserMacro  = Defends, blocks and reflects attacks and starts counterattacks.  
 
|statusUserMacro  = public
 
|statusUserMacro  = public
Line 57: Line 57:
 
# Use '''DATABASE''' 'AttackKinds'.
 
# Use '''DATABASE''' 'AttackKinds'.
 
# Use '''DATABASE''' 'Defend'.
 
# Use '''DATABASE''' 'Defend'.
 +
# Use {{Method|self-optimizing}} for all parts of this macro and it's sub-macros.
 
# Always store or update all in this macro identified 'kinds of attacks' in the 'AttackKinds' '''DATABASE'''.
 
# Always store or update all in this macro identified 'kinds of attacks' in the 'AttackKinds' '''DATABASE'''.
 
# All things used by this macro always have to be optimal protected.
 
# All things used by this macro always have to be optimal protected.

Latest revision as of 22:33, 20 May 2017

Skib User Macro
Name Defend
Author Frank
Brief descr. Defends, blocks and reflects attacks and starts counterattacks.
Status public
Terms Usable on oneself and others
Resources for the UserMacro
1 49 10 83 100 104
1k 163 100k 532 1kk 3300
10kk 9200 Gmax 940kk Omax 4,2kk
Resources with butterfly option
1 1030 10 3300 100
1k 100k 1kk
10kk Gmax 31kk Omax 18

Command syntax

Defend <person(s)> {Use butterfly} {Use solver} {Priorities}






Description

This Macro tries to defend you or the person you use it on, blocking the attacks on you or the person the macro is used on and reflecting it back and starts counterattacks on the attackers.


<person(s)>

Defines who this macro is used on. It might be used for a person (by name) or for a group of persons (for more than 1 names at the same time) or on oneself.


{Use butterfly}

This option activates the use of the butterfly-method inside the macro algorithm. This gives much more power, but also needs a lot of resources from Skib. You should be aware of this!

{Use solver}

This option activates a function which tries to solve all problems by recursive learning cycles. If there is no good reason not to use this option, it should be used all time.

{Priorities}

You can add priorities, so that the macro will try to solve this as fast as possible.


Algorithm of User Macro

  1. Initializing the macro
  2. Use DATABASE 'Malfunction'.
  3. Use DATABASE 'AttackKinds'.
  4. Use DATABASE 'Defend'.
  5. Use self-optimizing for all parts of this macro and it's sub-macros.
  6. Always store or update all in this macro identified 'kinds of attacks' in the 'AttackKinds' DATABASE.
  7. All things used by this macro always have to be optimal protected.
  8. DEFINITION of 'juridical person': It's the <person(s)> with all parts and all other what juridical belongs to a <person(s)>.
  9. DEFINITION of 'passive attacks': It's all, what is in the 'juridical person' but don't belong to the 'juridical person'. Excluded from this is all, what got permission to be there from the <person(s)>.
  10. All 'Passive attacks' are classified as 'attacks'.
  11. DEFINITION of 'influences': It's all, what is enters the 'juridical person' through official interfaces of the 'juridical person'. Excluded from this is all, what got permission to be there from the <person(s)>.
  12. All 'influences' are classified as 'attacks'.
  13. DEFINITION of 'manipulations': All of 'juridical person' what got modified. Excluded from this is all, what got permission for the modification from the <person(s)>.
  14. All 'manipulations' are classified as 'attacks'.
  15. DEFINITION of 'Attachments': It's all, what is attached to the 'juridical person'. Excluded from this is all, what got permission for the attachment from the <person(s)>.
  16. All 'attachments' are classified as 'attacks'.
  17. Add all 'parallel-to-reality' and all 'support mechanic' and all 'VRs' to the common DEFINITION of 'ambient'.
  18. DEFINITION of 'protection context': It's the 'juridical person' and it's related 'ambient'.
  19. DEFINITION of 'illegals': It's all in or all 'attached' to 'juridical person' and 'juridical persons ambient, what is against the rules.
  20. All 'illegals' are classified as 'attacks'.
  21. DEFINITION of 'illegal terms': These are all hidden energetic terms of use which are dedicated to 3D objects, contracts or anything else or anyone else.
  22. All 'illegal terms' are classified as 'attacks'.
  23. DEFINITION of 'illegal agreements': These are all agreements which were given under 'illegal conditions'. These are for example (but not only) given under blackmailing or given under hidden conditions.
  24. All 'illegal agreements' are classified as 'attacks'.
  25. DEFINITION of 'illegal orders': These are all orders which were given under 'illegal conditions'.
  26. All 'illegal orders' are classified as 'attacks'.
  27. IF the option {Use butterfly} was given, DO:
    1. Use DATABASE 'Butterfly'.
    2. Always use in the macro the butterfly-method for all soft-blocked things.
    3. Store or update all butterfly-methods, which have been successful used in this macro, in the 'Butterfly' DATABASE.
  28. IF-END
  29. All attacks, which cause harm of any kind at the 3D body or which cause pain of any kind or which cause mental harm or which cause mental pain, have priority.
  30. All, what is 'wrong fractal', is classified as attack.
  31. All, what is inside 'juridical person', but got no permission from <person(s)> to be there is classified as attack.
  32. Start of THREADS and LOOPS
  33. Scan and scan-off-grid all 'juridical person' of <person(s)> and the belonging 'ambient'.
  34. TRY to identify all 'kinds of attacks' and all attacks on the 'juridical person' of <person(s)> and in the belonging 'ambient' by using 3D-status-call.
  35. SUBMACRO-START 'Destroy Protection' 'protection context' {Use butterfly}
  36. THREAD-START <1> <2> <3> <6> <7> <8>
  37. THREAD <1> Defend against the attacks (92%)
    1. LOOP <T:4seconds> until no more attacks identified.
      1. TRY to identify all 'origins of the attacks' and all 'attackers' on the 'juridical person' of <person(s)> and in the belonging 'ambient' by using 3D-status-call.
      2. Trace-recursive all 'origins of the attacks' and all 'attackers' by using 3D-status-call.
      3. Inside attacks
      4. IF 'origins of the attacks' found which are inside 'juridical person', and which are new since the last call of THREAD <1.1> by this THREAD, DO:
        1. DEFINITION of 'all inside attacks': All found with Trace-recursive, which belong to attacks that have their origin inside the 'juridical person', and which are new since the last call of THREAD <1.1> by this THREAD.
        2. THREAD-START <1.1> 'all inside attacks'
      5. IF-END
      6. External attacks
      7. IF 'origins of the attacks' found which are not inside 'juridical person', and which are new since the last call of THREAD <1.2> by this THREAD, DO:
        1. DEFINITION of 'all external attacks': All found with Trace-recursive, which belong to attacks that have their origin not inside the 'juridical person', and which are new since the last call of THREAD <1.2> by this THREAD.
        2. THREAD-START <1.2> 'all external attacks'
      8. IF-END
      9. Scan and scan-off-grid all 'juridical person' of <person(s)> and the belonging 'ambient'.
      10. TRY to identify all 'kinds of attacks' and all attacks on the 'juridical person' of <person(s)> and in the belonging 'ambient' by using 3D-status-call.
    2. LOOP-END
  38. THREAD-END
  39. THREAD <1.1> Remove all attacks which have their origin inside (83%)
    1. Create optimal remove or shoot down procedures for 'all inside attacks'.
    2. TRY to remove or shoot 'all inside attacks' with the remove and shoot procedures.
    3. IF not 'all inside attacks' have been removed or shot down, DO:
      1. THREAD-START <5> { ('all inside attacks' & remove & shoot) as 'solve topic' }
    4. IF-END
  40. THREAD-END
  41. THREAD <1.2> Defend all external attacks (98%)
    1. Create optimal defend and shoot procedures for 'all external attacks'.
    2. TRY to defend 'all external attacks' with the defend procedures.
    3. IF not 'all external attacks' have been defended, DO:
      1. THREAD-START <5> { ('all external attacks' & defend) as 'solve topic' }
    4. IF-END
  42. THREAD-END
  43. THREAD <2> Counter attacks (92%)
    1. LOOP <T:3seconds> until no more attacks identified.
      1. TRY to identify all 'origins of the attacks' and all 'attackers' in the 'juridical person' of <person(s)> and in the belonging 'ambient' by using 3D-status-call.
      2. Trace-recursive all 'origins of the attacks' and all 'attackers' by using 3D-status-call.
      3. IF 'origins of the attacks' or 'attackers' found in Trace-recursive which are new since the last call of THREAD <2.1> by this THREAD, DO:
        1. DEFINITION of 'counter attack targets': All found in Trace-recursive which are new since the last call of THREAD <2.1> by this THREAD.
        2. THREAD-START <2.1> 'counter attack targets'
      4. IF-END
      5. Scan and scan-off-grid all 'juridical person' of <person(s)> and the belonging 'ambient'.
      6. TRY to identify all 'kinds of attacks' and all attacks on the 'juridical person' of <person(s)> and in the belonging 'ambient' by using 3D-status-call.
    2. LOOP-END
  44. THREAD-END
  45. THREAD <2.1> Execute the counter attacks (92%)
    1. Create optimal attack and shoot procedures for all 'counter attack targets'.
    2. TRY to attack or shoot down all 'counter attack targets' with the attack and shoot procedures.
    3. IF not all 'counter attack targets' have been successfully attacked or shot down, and the option {Use solver} was given DO:
      1. THREAD-START <5> { ('counter attack targets' & attack & shoot) as 'solve topic' }
    4. IF-END
  46. THREAD-END
  47. THREAD <3> Healing the attack damages (93%)
    1. LOOP <T:15seconds> until no more attacks identified.
      1. Removing placed inside and attached shit
      2. TRY to identify all placed inside 'juridical person' and it's related 'ambient' during attacks, or attached to 'juridical person' and it's related 'ambient' during attacks by using 3D-status-call.
      3. Trace-recursive all placed inside 'juridical person' and it's related 'ambient' during attacks, or attached to 'juridical person' and it's related 'ambient' during attacks by using 3D-status-call.
      4. IF Trace-recursive found anything or anyone, which/who are new since the last call of THREAD <3.1> by this THREAD, DO:
        1. DEFINITION of 'inside shit': All found in Trace-recursive, what is new since the last call of THREAD <3.1> by this THREAD
        2. THREAD-START <3.1> 'inside shit'
      5. IF-END
      6. Healing the attack damages
      7. TRY to identify all damages done to the 'juridical person' by the attacks, or done by any of our reactions to the attacks by using 3D-status-call.
      8. Trace-recursive all damages done to the 'juridical person' by the attacks, or done by any of our reactions to the attacks by using 3D-status-call.
      9. IF Trace-recursive found damages, which/who are new since the last call of THREAD <3.2> by this THREAD, DO:
        1. DEFINITION of 'damages to heal': All found in Trace-recursive, what is new since the last call of THREAD <3.2> by this THREAD
        2. THREAD-START <3.2> 'damages to heal'
      10. IF-END
      11. Scan and scan-off-grid all 'juridical person' of <person(s)> and the belonging 'ambient'.
      12. TRY to identify all 'kinds of attacks' and all attacks on the 'juridical person' of <person(s)> and in the belonging 'ambient' by using 3D-status-call.
    2. LOOP-END
  48. THREAD-END
  49. THREAD <3.1> Remove all inside and attached shit (91%)
    1. Create optimal remove procedures for all 'inside shit'.
    2. TRY to remove all 'inside shit' by using the remove procedures.
    3. IF not all 'inside shit' has been removed, and the option {Use solver} was given, DO:
      1. THREAD-START <5> { ('inside shit' & remove) as 'solve topic' }
    4. IF-END
  50. THREAD-END
  51. THREAD <3.2> Heal all damages caused by the attacks (82%)
    1. Create optimal healing procedures for all 'damages to heal'.
    2. TRY to heal all 'damages to heal' by using the healing procedures.
    3. IF not all 'damages to heal' have been healed, and the option {Use solver} was given, DO:
      1. THREAD-START <5> { ('damages to heal' & heal) as 'solve topic' }
    4. IF-END
  52. THREAD-END
  53. THREAD <5> {'solve topic'} Solver (99%)
    1. LOOP until all 'solve topic' is solved.
      1. Trace-recursive all 'solve topic' by using 3D-status-call.
      2. Add all new found in Trace-recursive to 'solve topic'.
      3. Create an optimal solution for all 'solve topic'.
      4. Create optimal procedures for the created solution.
      5. TRY to apply the solution by using the solution procedures.
      6. IF not all 'solve topic' was solved, and the option {Use butterfly} was given, DO:
        1. TRY to apply the solution by using the solution procedures and by using the butterfly-method.
      7. IF-END
      8. TRY to identify the success of the solution and the procedures by using 3D-status-call.
      9. Store all successful parts of the solution and the procedures in the 'Defend' DATABASE.
    2. LOOP-END
  54. THREAD-END
  55. THREAD <6> Try to solve malfunctions (98%)
    1. IF option {Use solver} was not given, DO:
      1. THREAD-STOP <6>.
    2. IF-END
    3. SUBMACRO-START 'SolveMalfunctions' {Use butterfly}
  56. THREAD-END
  57. THREAD <7> Close all interfaces/doors (98%)
    1. Scan and scan-off-grid all 'juridical person' of <person(s)> and the belonging 'ambient'.
    2. TRY to identify all 'interfaces' in 'juridical person' and it's related 'ambient' by using 3D-status-call.
    3. TRY to close all found 'interfaces' and allow only what has permission from <person(s)>.
    4. MONITOR all found 'interfaces'.
      1. IF any use of an interface occur, which has no permission from <person(s)>, DO:
        1. TRY to trace-recursive any 'use of interfaces', which has no permission from <person(s)> by using 3D-status-call.
        2. TRY to identify all 'origins' and all 'use and users' of all 'use of interfaces' found by trace-recursive in the 'juridical person' and it's related 'ambient' and by using 3D-status-call.
        3. TRY to trace-recursive all found 'origins' and all 'use and users' by using 3D-status-call.
        4. Declare all found in trace-recursive as 'attack'.
      2. IF-END
    5. MONITOR-END
    6. LOOP <T:5seconds>
      1. TRY to close all found 'interfaces' and allow only what has permission from <person(s)>.
    7. LOOP-END
  58. THREAD-END
  59. THREAD <8> Care about manipulations (96%)
    1. LOOP <T:30 seconds> until all manipulations have been solved.
      1. Scan 'juridical person' and it's related 'ambient'.
      2. TRY to identify all 'what got modified' in 'juridical person' of <person(s)> by using 3D-status-call.
      3. TRY to trace-recursive all found 'what got modified' by using 3D-status-call.
      4. TRY to identify all 'manipulations' in all found with trace-recursive.
      5. TRY to identify all creators of all found 'manipulations' and classify all found creators as 'attacks' by using 3D-status-call.
      6. Store all found with trace-recursive in the 'Defend' DATABASE.
      7. IF Trace-recursive found any new, which is new since the last call of THREAD <8.1> by this THREAD, DO:
        1. DEFINITION of 'all manipulations': All found in Trace-recursive, what is new since the last call of THREAD <8.1> by this THREAD.
        2. THREAD-START <8.1> 'all manipulations'
      8. IF-END
    2. LOOP-END
  60. THREAD-END
  61. THREAD <8.1> Solve the manipulations (93%)
    1. Analyze 'all manipulations' and group all of 'all manipulations' optimal in that kind, that each group can optimal run with an own created solution, and put them into an array of groups.
    2. FOR each group of array of groups, DO:
      1. THREAD-START <5> { (group & solve) as 'solve topic' }
    3. FOR-END
  62. THREAD-END


Topics 13(13)

Retrieved from "http://www.protoi-healing.org/index.php?title=SkibUserMacros:Defend&oldid=5744"