Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

Problem with CombatTracker? (TypeError: thispage.get(...).split is not a function)

Hi there, I am having a problem with some API script, very likely with CombatTracker (the problem occurs when I use CombatTracker by clicking on "Start Combat" or "Stop Combat"). Sometimes, it says Please update StatusInfo to the latest version. although I am using the latest version. Whenever the problem occurs, no other API script or macro works any more. When I check the API scripts afterwards, I get the following message: For reference, the error message generated was: TypeError: thispage.get(...).split is not a function TypeError: thispage.get(...).split is not a function at toBack (/home/node/d20-api-server/api.js:2895:40) at getOrCreateMarker (apiscript.js:2828:9) at removeMarker (apiscript.js:2539:9) at stopCombat (apiscript.js:2521:9) at handleInput (apiscript.js:2122:17) at eval (eval at &lt;anonymous&gt; (/home/node/d20-api-server/api.js:168:1), &lt;anonymous&gt;:65:16) at Object.publish (eval at &lt;anonymous&gt; (/home/node/d20-api-server/api.js:168:1), &lt;anonymous&gt;:70:8) at /home/node/d20-api-server/api.js:1739:12 at /home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:93:560 at hc (/home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:39:147) ModOutputConsole says the following (here the problem occured when clicking on "Stop Combat": TypeError: thispage.get(...).split is not a function TypeError: thispage.get(...).split is not a function &nbsp;&nbsp;&nbsp; at toBack (/home/node/d20-api-server/api.js:2895:40) &nbsp;&nbsp;&nbsp; at getOrCreateMarker (apiscript.js:2828:9) &nbsp;&nbsp;&nbsp; at removeMarker (apiscript.js:2539:9) &nbsp;&nbsp;&nbsp; at stopCombat (apiscript.js:2521:9) &nbsp;&nbsp;&nbsp; at handleInput (apiscript.js:2122:17) &nbsp;&nbsp;&nbsp; at eval (eval at &lt;anonymous&gt; (/home/node/d20-api-server/api.js:168:1), &lt;anonymous&gt;:65:16) &nbsp;&nbsp;&nbsp; at Object.publish (eval at &lt;anonymous&gt; (/home/node/d20-api-server/api.j<a href="s:168:1), s:168:1), us&gt;:70:8) &nbsp;&nbsp;&nbsp; at /home/node/d20-api-server/api.js:1739:12 &nbsp;&nbsp;&nbsp; at /home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:93:560&nbsp;&nbsp;&nbsp; at hc (/home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:39:147) In addition, here is some information to my API sandbox (what I am actually running): detected currently running sandbox... restarting "Loading character sheet data..." "Starting webworker script..." "Loading 0 translation strings to worker..." "-=&gt; GroupInitiative v0.9.36 &lt;=- [Thu Feb 03 2022 01:42:35 GMT+0000 (Coordinated Universal Time)]" "CombatTracker Ready! Command: !ct" "-=&gt; TokenNameNumber v0.5.15 &lt;=- [Fri Sep 17 2021 00:25:18 GMT+0000 (Coordinated Universal Time)]" "StatusInfo Ready! Command: !condition" "TerrainGenerator ver 0.2.0 loaded" "Script loaded: Waypoint Patrols, actively patrolling" "-=&gt; libTokenMarkers v0.1.1 &lt;=- [Wed Dec 30 2020 02:10:29 GMT+0000 (Coordinated Universal Time)]" " &gt; Loaded 55 Token Markers." I'd really prefer if someone could help me with this problem. Thanks in advance!
I get the Please update StatusInfo to the latest version. message every time I use Combat Tracker but I'm not getting the other messages, and yes I have the most recent StatusInfo from the Oneclick install.
1660934546
The Aaron
Roll20 Production Team
API Scripter
I just pushed a fix for the StatusInfo notice (it's just an outdated check, kicked the can down the road with the latest StatsuInfo version number). The crashes are a bit more peculiar.&nbsp; That's actually crashing in Roll20 code, not an API script.&nbsp; Something about the object being passed to the toBack() function seems to be invalid.&nbsp; If you can find a reproducible case, I can try and find a solution to it.