Messages

1

OXCE Suggestions Y-script / Re: [Suggestion] Ability to BLIT objects by script.

« on: December 30, 2024, 12:55:49 pm »

Really hoping this gets revisited. The Inventory Paperdoll hook would really be helpful to display custom script-based status effects, currently very limited ways to convey such info to players using scripts.

2

OXCE Suggestions DONE / Re: Converting OXCE to rapidyaml

« on: December 01, 2024, 02:13:00 pm »

Possible issue regarding submod inheritance found by Mercury in Rosigma.

Rosigma modifies the startingbase rulesets found in the base 40k mod, however if the facility section of startingBase for a certain difficulty/faction is not modified, and therefore not included in Rosigmas ruleset, the base starts with no facilities. It seems that the facility section is not getting inherited properly in the submod. Not sure if its a intended change or not, but since its behaving differently than OXCE v7.15, thought it worth reporting anyways.


Factions/difficulties where Rosigma has modifies the starting facilities seems to work as intended.

Here is a comparison of the relevant starting base sections from the 40k mod and Rosigma

40k:

Code: [Select]

startingBaseSuperhuman: #*** Imperial Guard
  facilities:
    - type: STR_ACCESS_LIFT
      x: 2
      y: 2
    - type: STR_HANGAR
      x: 2
      y: 0
    - type: STR_HANGAR
      x: 0
      y: 4
    - type: STR_HANGAR
      x: 4
      y: 4
    - type: STR_GUARD_BARRACKS
      x: 3
      y: 2
    - type: STR_GENERAL_STORES
      x: 2
      y: 3
    - type: STR_LABORATORY
      x: 3
      y: 3
    - type: STR_WORKSHOP
      x: 4
      y: 3
    - type: STR_SMALL_RADAR_SYSTEM
      x: 1
      y: 3
  randomSoldiers:
    STR_GUARDSM: 16
    STR_COMMISSAR: 1
    STR_GUARD_OFFICER: 1
  crafts:
    - type: STR_CHIMERA
      id: 1
      fuel: 1000
      damage: 0
      weapons:
        - type: STR_CRAFT_MULTILASER_UC
          ammo: 100
      items:
        STR_GRENADE: 4
        STR_LASER_RIFLEG: 14
        STR_LASGUN_CLIP: 14
        STR_LONGLAS: 1
        STR_LASGUN_CLIP_HOTSHOT: 1
        STR_HEAVY_STUBBER: 1
        STR_HEAVY_STUBBER_CLIP: 1
        STR_PISTOL: 1
        STR_PISTOL_CLIP: 2
        STR_OFFICERS_SWORD: 1
    - type: STR_VALKYRIE
      id: 1
      fuel: 1800
      damage: 0
      weapons:
        - type: STR_STINGRAY
          ammo: 6
        - type: STR_CANNON_UC
          ammo: 100
      status: STR_READY
    - type: STR_LIGHTNING_INTERCEPTOR
      id: 1
      fuel: 1000
      damage: 0
      weapons:
        - type: STR_STINGRAY
          ammo: 6
        - type: STR_CANNON_UC
          ammo: 100
      status: STR_READY
  items:
    STR_AVALANCHE_LAUNCHER: 1
    STR_AVALANCHE_MISSILES: 10
    STR_CANNON: 2
    STR_HWP_CANNON_SHELLS: 1
    STR_GRENADE: 10
    STR_KRAK_GRENADE: 10
    STR_LASER_RIFLEG: 2
    STR_LASGUN_CLIP: 10
    STR_LONGLAS: 1
    STR_LASGUN_CLIP_HOTSHOT: 5
    STR_ROCKET_LAUNCHER: 1
    STR_SMALL_ROCKET: 4
    STR_SMOKE_GRENADE: 8
    STR_HEAVY_STUBBER: 1
    STR_HEAVY_STUBBER_CLIP: 4
    STR_HEAVY_BOLTER_GUARD: 1
    STR_AC_AP_AMMO: 4
    STR_GUARD_ARMORS_MEDIC: 2
    STR_PISTOL_CLIP: 3
    STR_CHAINSWORD: 1
    STR_LASER_PISTOLG: 1
    STR_LASPISTOL_CLIP: 5
    STR_KILLPOINT_TOKEN: 180
    STR_STINGRAY_LAUNCHER: 1
    STR_STINGRAY_MISSILES: 25
  scientists: 10
  engineers: 10
Rosigma:

Code: [Select]

startingBaseSuperhuman: #*** Imperial Guard
  randomSoldiers:
    # STR_GUARDSM: 16
    STR_PILOT_GUARD: 3
    # STR_COMMISSAR: 1
    # STR_GUARD_OFFICER: 1
    # STR_PENITENT_GUARD: 4
  crafts:
    #- type: STR_CHIMERA
    #- type: STR_VALKYRIE
    #- type: STR_LIGHTNING_INTERCEPTOR
  items:
    STR_AVALANCHE_LAUNCHER: 1
    STR_AVALANCHE_MISSILES: 10
    STR_STINGRAY_LAUNCHER: 2
    STR_STINGRAY_MISSILES: 25
    STR_CANNON: 2
    STR_HWP_CANNON_SHELLS: 10
    STR_KRAK_GRENADE: 10
    STR_LASER_RIFLEG: 16
    STR_LASGUN_CLIP: 24
    STR_STUB_RIFLE: 2
    STR_STUB_GUN_AMMO: 10
    STR_MISSILE_LAUNCHER_GUARD: 1
    STR_SMALL_ROCKET: 4
    STR_SMOKE_GRENADE: 8
    STR_HEAVY_STUBBER: 2
    STR_HEAVY_STUBBER_CLIP: 5
    # STR_HEAVY_BOLTER_GUARD: 1
    # STR_AC_AP_AMMO: 6
    STR_BOLTPISTOL_LIGHT_ULTRA: 1
    STR_LIGHT_BOLTPISTOL_AMMO: 6
    STR_CHAINSWORD: 1
    STR_LASER_PISTOLG: 1
    STR_LASPISTOL_CLIP: 5
    STR_KILLPOINT_TOKEN: 180
    # STR_ALIEN_HABITAT: 3
    STR_OFFICERS_CHAIN_SWORD: 1
    STR_OFFICER_COMMISSION: 1
  scientists: 10
  engineers: 10
The Chamber Militant (Experienced) difficulty seems to have the same issue.

I tested this with both of these forks:
https://github.com/Delian0/OpenXcom
https://github.com/MeridianOXC/OpenXcom/tree/test-rc0-fix

Versions of mods used:
Rosigma: https://codeberg.org/LeflairKunstler/ROSIGMA/src/commit/59c9e24e1161894de2504d52f1862b31e4209a86
40k: https://github.com/BeatAroundTheBuscher/OXCE_40k/tree/c3043bc82257cdfe7802e47668001edd53d7f16e

3

OXCE Support Y-scripts / Re: Drugs that restore / give time (tu)

« on: June 17, 2022, 01:55:18 am »

I see two issues with the script.
Firstly the scripthook is missing (i.e. the part that determines when the script runs). I presume the script you grabbed used the healUnit: hook, you need to add it one line above code: |. Note that if you're adding it to a file with multiple existing scripts, there might already be a healUnit: hook, in which case you only need to add the script after it (adding the hook again will not work).
Secondly the Tag required by the script most likely isn't defined which means you need to add that too. Here is an example on how it should look like:

Code: [Select]

extended:
  tags:
    RuleItem:
      WM_IS_WACKY: intIf the RuleItem section already exists in the file you can just add WM_IS_WACKY: int among the existing tags.

One pitfall to avoid is that you need to add tags to an item in the same file as where the tags are defined, otherwise the script may not work.
The easiest way to achieve what you're trying to do would be to just to create a new .rul file and add the new script and item, it should look something like this

Code: [Select]

items:
  - type: STR_COMBAT_DRUGS
    medikitActionName: STR_INJECT
    costUse:
      time: 1
      health: 1  (We will lost 1 hp for each use)
      stun: -50
      morale: -50
      mana: -50
    costThrow:
      energy: 6
      time: 40
    flatRate: true
    isConsumable: true
    flatUse:
      time: true
      health: true
    recoveryPoints: 1
    tags:  (The tag is what the script will use)
      WM_IS_WACKY: 1

extended:
  tags:
    RuleItem:
      WM_IS_WACKY: int
  scripts:
    healUnit:
    code: |
          var int temp;

          item.getTag temp Tag.WM_IS_WACKY;

          if neq temp 0;
            # debug_log "healUnit: applying wacky medikit, skip normal effects completely";
            set medikit_action_type 0;

            target.getTimeUnits temp;
            add temp 55;
            target.setTimeUnits temp;

            target.getEnergy temp;
            add temp 50;
            target.setEnergy temp;

            return;
          end;

          # debug_log "healUnit: not wacky...";
          return;

4

40k / Re: [ADDON] ROSIGMA

« on: April 29, 2022, 06:10:28 pm »

I believe this is the space hulk mission objective.

5

OXCE Support Y-scripts / Re: Scripting 'isFuseEnabled'

« on: February 25, 2022, 02:58:11 pm »

Code: [Select]

[25-02-2022_14-45-00] [ERROR] Error in parsing script 'newTurnItem' for 'Global Event Script': invalid variable definition after other operations: 'var int Fuse_State;'I believe this error is caused due to all variables being required to be declared before any operations (which is why var int Current_Turn; isn't throwing an error since it's before any operations).
I get no errors after editing the script to this:

Code: [Select]

extended:
  tags:
    RuleItem:
      AUTO_PRIMED_ENABLED: int
      AUTO_PRIMED_FUSE_TIME: int
      AUTO_PRIMED_GROUND_ARM: int
      AUTO_PRIMED_FIRST_TURN_ONLY: int
  scripts:
    newTurnItem:
      - offset: 52
        code: |
          var int Current_Turn;
          var int Fuse_State;
          var ptr RuleInventory Items_Inventory;
          var int Inventory_Slot;
          var int Auto_Prime;
          var int Fuse_Time;
          var int Ground_Arm;
          var int First_Turn_Only;
         
          battle_game.getTurn Current_Turn;

          item.isFuseEnabled Fuse_State;


          item.getSlot Items_Inventory;
          Items_Inventory.getType Inventory_Slot;

          item.getTag Auto_Prime Tag.AUTO_PRIMED_ENABLED;

          item.getTag Fuse_Time Tag.AUTO_PRIMED_FUSE_TIME;

          item.getTag Ground_Arm Tag.AUTO_PRIMED_GROUND_ARM;

          item.getTag First_Turn_Only Tag.AUTO_PRIMED_FIRST_TURN_ONLY;




          # If Grenade is not set for Auto Prime, Return.
          if neq Auto_Prime 1;
            return;
          end;

          # If Grenade is already armed, return
          if neq Fuse_State 0;
            return;
          end;

          # If Grenade is on ground and cannot ground arm, return
          if eq Ground_Arm 0;
            if eq Inventory_Slot INV_GROUND;
              return;
            end;
          end;

          # If Grenade can only be auto armed on first turn and it is after that, return
          if eq First_Turn_Only 1;
            if neq Current_Turn 1;
              return;
            end;
          end;

          # Set Grenade fuse to Fuse_Time
          item.setFuseTimer Fuse_Time;
          return;

6

OXCE Support Y-scripts / Re: Scripting 'isFuseEnabled'

« on: February 23, 2022, 08:41:26 pm »

The var int that the isFuseEnabled requires is where its return value is written.
So to do what you're trying to accomplish you'd need to do something like this:

Code: [Select]

scripts:
   newTurnItem:       
       - offset: 1
         code: |
          var int x;
          item.isFuseEnabled x; #x gets the value 0 or 1 depending on if the fuse is lit
          if eq x 0;
            <CODE>
          end;
          return;

Regarding the additional question, no, the pointer names vary between script hooks. You can find the pointers available for each hook in the script data section of the API.
For example in the newTurnItem hook, the pointer for the BattleItem is just item

Code: [Select]

Name: battle_game                             ptre      BattleGame
Name: item                                    ptre      BattleItem
Name: null                                              null     
Name: rules                                   ptr       RuleMod 
Name: side                                              int     
Name: turn                                              intThe pointer for BattleGame seems to be consistently battle_game though.

7

Help / Re: Recovering friendly spawned units?

« on: January 12, 2022, 09:14:36 pm »

Using builtInWeaponSets to add a dummy item with recoveryTransformations to change it back to the original item could probably do it.
Something like this:

Code: [Select]

units:
   - type: STR_EXAMPLE_UNIT
     builtInWeaponSets:
       - - STR_DUMMY_ITEM
items:
   - type: STR_DUMMY_ITEM
     fixedWeapon: true
     recover: true
     recoveryTransformations:
        STR_EXAMPLE_ITEM: [1]


8

OXCE Support Y-scripts / Re: Replacing weapon sprite depending of ammo.

« on: September 23, 2021, 01:50:40 pm »

Counter-Terrorist Operations, UNEXCOM: bureau 11 and OpenScarfCom also have scripts that do this