Warning: Undefined array key 1 in /var/www/html/lib/tpl/mikio-blitz/mikio.php on line 815
≪ View Page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
blitz:objectgimmick [2026/07/06 17:27] – gameboyadv4002blitz:objectgimmick [2026/08/17 19:52] (current) – gameboyadv4002
Line 10: Line 10:
 Normal sponges scale up to 60 units in all dimensions. Rectangles scale to the same degree except for X, which scale to 90 units. Sponges marked Small only grow to 45 units. Normal sponges scale up to 60 units in all dimensions. Rectangles scale to the same degree except for X, which scale to 90 units. Sponges marked Small only grow to 45 units.
  
 +===== Splat Switch (Paintable Target) =====
 +Obj_SwitchPaint(Small)(Octa) is fairly simple. If you paint it, it sends out a signal to every object connected via Switchable--SendTo.
 +
 +<code>
 +    - Id: obj266
 +      IsLinkDest: false
 +      IsPlayTimerSE: false
 +      IsUsePredictAlertOnOff: false
 +      LayerConfigName: Cmn
 +      Links:
 +        Switchable__SendTo:
 +          - {DefinitionName: Switchable__SendTo, DestUnitId: obj264, UnitFileName: ''}
 +      OffCounter: !l 0
 +      Rotate: {X: 90.00000, Y: 0.00000, Z: 0.00000}
 +      Scale: {X: 1.00000, Y: 1.00000, Z: 1.00000}
 +      Switchable__InitialState: !l 0
 +      Switchable__RespawnReset: !l 2
 +      Team: !l 0
 +      Translate: {X: -168.62500, Y: 532.37620, Z: 987.45650}
 +      UnitConfigName: Obj_SwitchPaintOcta
 +</code>
 +  * Switchable--RespawnReset: This parameter is common to most Switch objects, and should generally be left as 2 to make sure death doesn't lock players out. It's more noticeable in this case, as leaving this parameter as 0 will make the object appear visibly painted on respawn.
  
 ===== Ink-Switch (Spinning Target) ===== ===== Ink-Switch (Spinning Target) =====
-In order to get obejcts to move in accordance with the progress of an Ink-Switch (SwitchShock), you need RailTogglePoint. These are attached in the same way as [[blitz:special|Obj_AbstractLift]], connect it to the rail with RailableParams_Rail, and connect the objects you want moved with ActorBindable. Connect the SwitchShock to the RailTogglePoint with SwitchableSendTo. As far as I can tell, it must be attached to the destination rail point, not the original position.+In order to get obejcts to move in accordance with the progress of an Ink-Switch (SwitchShock), you need RailTogglePoint. These are attached in the same way as [[blitz:special|Obj_AbstractLift]], connect it to the rail with RailableParams_ToRail (not RailableParams_Rail), and connect the objects you want moved with ActorBindable. Connect the SwitchShock to the RailTogglePoint with SwitchableSendTo. A more complete explanation can be found at [[blitz:special|Invisible Objects]].
  
-In Fld_OctCleaner_OctMsn, every RailTogglePointOcta has the following parameters.+<code> 
 +    - Id: obj960 
 +      IsLinkDest: false 
 +      LayerConfigName: Cmn 
 +      Links: 
 +        Switchable__SendTo: 
 +          - {DefinitionName: Switchable__SendTo, DestUnitId: obj959, UnitFileName: ''} 
 +      ModelName: null 
 +      Rotate: {X: 0.00000, Y: -90.00000, Z: 0.00000} 
 +      Scale: {X: 1.00000, Y: 1.00000, Z: 1.00000} 
 +      Switchable__InitialState: !l 0 
 +      Switchable__RespawnReset: !l 2 
 +      Team: !l 2 
 +      Translate: {X: 137.50000, Y: 150.00000, Z: -760.00000} 
 +      UnitConfigName: SwitchShockOcta 
 +</code> 
 +The SwitchShock object does not have any paramters unique to it.
  
-  *       AccOff: 0.01000 +Objects attached to Ink-Switches typically undo slower than they progress, and that needs to be reflected in the RailTogglePoint object's parameters, not the Ink Switch.
-  *       AccOn: 0.10000 +
-  *       DetectPlayerIsNearDistanceXZ: 100.00000 +
-  *       IsFollowRailPointRotate: false +
-  *       IsFollowRailRotate: false +
-  *       IsLinkDest: true +
-  *       IsSwitchStopSmooth: true +
-  *       LayerConfigName: Cmn +
-  *       ModelName: null +
-  *       OutAreaSpeedRate: 1.00000 +
-  *       QuakeAmplitudeCoef: 1.00000 +
-  *       QuakeDecrement: 0.20000 +
-  *       QuakeFrequency: 0.50000 +
-  *       RailableParamsSolveType: !l 0  +
-  *       SwitchStopFrame: !l 0 +
-  *       SwitchStopRegist: 0.05000 +
-  *       SwitchableParamsInitialState: !l 0 +
-  *       SwitchableParamsRespawnReset: !l 2 +
-       +
-However, the following parameters are different. +
-  *   TerminateAtTerminal: (bool) +
-  *   SpeedOff: (float) +
-  *   SpeedOn: (float) +
- +
-Objects attached to Ink-Switches typically undo slower than the progress.+
  
 ===== Canned Weapons ===== ===== Canned Weapons =====
 Canned Main and Sub weapons are handles by an object called Obj_ItemCanMainSub. The "MainWeaponName" parameter is used to decide the main, "SubWeaponName" is for the sub, with these parameters being set to null when the other is in use. Canned Main and Sub weapons are handles by an object called Obj_ItemCanMainSub. The "MainWeaponName" parameter is used to decide the main, "SubWeaponName" is for the sub, with these parameters being set to null when the other is in use.
 +
 +From D01 Ink from Above Station (OctMissleTacopter [sic]):
 +<code>
 +    - CheckColPillerContinuous: false
 +      DontActivateOnRespawn: false
 +      Id: obj636
 +      IsLinkDest: false
 +      LayerConfigName: Cmn
 +      Links: {}
 +      MainWeaponName: Twins_Gallon_00
 +      ModelName: null
 +      SubWeaponName: null
 +      Switchable__InitialState: !l 0
 +      Switchable__RespawnReset: !l 2
 +      Team: !l 2
 +      UnitConfigName: Obj_ItemCanMainSubOcta
 +</code>
  
 Canned Specials are simply called "Obj_" and the special's internal name, i.e. Obj_SuperLanding for a canned Splashdown. Canned Specials are simply called "Obj_" and the special's internal name, i.e. Obj_SuperLanding for a canned Splashdown.
Line 51: Line 82:
 Using it is as simple as linking it to an instance of the relevant can with the DstCan link. Using it is as simple as linking it to an instance of the relevant can with the DstCan link.
  
 +===== Ink Pistons/Ink Sticks =====
 +Internally referred to as Obj_GeyserAuto(Octa).
 +
 +<code>
 +    - DelayFrame: !l 0
 +      DurationFrame: !l 180
 +      IntervalFrame: !l 240
 +      IsDisplayBaseModel: !l 0
 +      IsKeepDuration: false
 +      IsLightType: false
 +      IsLinkDest: false
 +      IsMovedByPlayer: false
 +      IsSetCameraXluFixBB: false
 +      IsSwitchDrivenType: false
 +      LayerConfigName: Cmn
 +      Length: 500.00000
 +      Links: {}
 +      MovingFrame: !l 20
 +      Radius: 20.00000
 +      Team: !l 0
 +      UnitConfigName: Obj_GeyserAutoOcta
 +</code>
 +
 +  * DelayFrame: Frames before the piston first activates
 +  * DurationFrame: Frames that it is active for
 +  * IntervalFrame: Frames between activations
 +  * IsKeepDuration: Boolean that is true if the ink piston never retracts
 +  * Length: Length of piston (note that the game only renders the last 500 units worth of piston. The hitbox is still active, but that's of little use to a player)
 +  * Radius: Radius of piston (note that the object itself never changes size, only the hitbox. It is recommended to keep it as 20)
 +  * Team: If set as 0, the piston's hitbox will repel, but will not damage. The fx surrounding the piston are the player's colour, but not the piston itself.
 +
 +If you want to have two sets of pistons that alternate, you can use this formula:
 +
 +x is the time you want the piston to be active for.
 +
 +y is the time that neither piston is active for.
 +
 +Piston 1:
 +<code>
 +    - DelayFrame: !l 0
 +      DurationFrame: !l x
 +      IntervalFrame: !l x + 2y
 +</code>
 +
 +Piston 2:
 +<code>
 +    - DelayFrame: !l x + y
 +      DurationFrame: !l x
 +      IntervalFrame: !l x + 2y
 +</code>
 +      
 ===== Dash Tracks/Panels ===== ===== Dash Tracks/Panels =====
 Dash tracks are internally referred to as Obj_DashPanel. Dash tracks are internally referred to as Obj_DashPanel.