Skip to content

Fix callExtension error by passing empty array instead of nil#36

Merged
fank merged 2 commits intomainfrom
fix/extension-nil-args
Feb 3, 2026
Merged

Fix callExtension error by passing empty array instead of nil#36
fank merged 2 commits intomainfrom
fix/extension-nil-args

Conversation

@fank
Copy link
Member

@fank fank commented Feb 3, 2026

Summary

  • Replace nil with [] in all extension calls that pass no arguments
  • Add missing [] args to :TIMESTAMP: calls
  • Arma 3's callExtension requires the second parameter to be an array

Problem

The following errors occurred during gameplay:

[OCAP] [EXT] ERROR when calling extension: ["",0,102,":INIT:",any]
[OCAP] [EXT] ERROR when calling extension: ["",0,102,":TIMESTAMP:",any]
Error Type Any, expected Array

Changes

  • fnc_initDB.sqf: Changed :GETDIR:*, :INIT:STORAGE:, and :INIT: calls to pass [] instead of nil
  • fnc_eh_fired_client.sqf: Added [] args to :TIMESTAMP: calls
  • fnc_eh_fired_clientBullet.sqf: Added [] args to :TIMESTAMP: calls

fank added 2 commits February 3, 2026 15:24
Arma 3's callExtension requires the second parameter to be an array.
Passing nil caused "Error Type Any, expected Array" at runtime.
All sendData calls must include an args array as the second parameter.
@fank fank merged commit 70f1a23 into main Feb 3, 2026
@fank fank deleted the fix/extension-nil-args branch February 3, 2026 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant