Plugin Script can't get access to node varible and signals | GDQuest | Page 1

jaunty elm Mar 21, 2025, 12:48 AM

#

I made a object pool debug panel as a new editor window, but met some issue
Here is my editor script, class, and error
I did try using @export but, it always print 0

plugin-script-cant-get-access-to-node-varible-and-signals-v0-yfeb6h4zuxpe1.webp

plugin-script-cant-get-access-to-node-varible-and-signals-v0-qz78pzg5vxpe1.webp

plugin-script-cant-get-access-to-node-varible-and-signals-v0-qiz1dza8vxpe1.webp

fathom scroll Mar 21, 2025, 2:06 AM

#

For some reason line 44 is not triggering correctly. Is detecting the SpawnManager as an ObjectPool type, if SpawnManager is inheriting from ObjectPool, even if the class_name is different is gonna trigger the "ObjectPool" check.

jaunty elm Mar 21, 2025, 2:37 AM

#

fathom scroll For some reason line 44 is not triggering correctly. Is detecting the SpawnManag...

Well, I did fix the issue, just use the @export, then there is another issue, it seems that Editor Plugin script can get data from the current running scene(Remote Scene). It only get the local scene data

#Plugin Script can't get access to node varible and signals