I can no longer type cast an Agent into a Player as it no longer recognizes what an agent type is?
Creative
Assets
Open verse after the update
Type conversion to still work
Type conversion doesn’t work
PC, Windows
My entire verse is red yet i can build verse code.
So many errors
idk how im gunna write code in these conditions tbh how will you know whats a genuine error
I have an Await and its not recognizing it
@Flak Can this be looked at please its extremely difficult to even progress using verse now as its affecting creator scrips not just epics ones
I have the same issues. Verse showing syntax errors but “Build Verse Code” completes Successfully.
Yeah .Await is now a syntax error.
How can we be expected to use verse like this its crazy. I understand its still in dev but give us a verse that doesn’t bug. I think imma not touch it now until they fix it as i cannot do this.
agreed its unusable…current game we are working on has like 30 await statements…the whole thing is red.
i have maybe 100 
cnt use it tbh not even gunna try i will do other things. Hoping its a quick fix or they give us a work around or a version that works. Did you try switching back to 0 version do that help ?
I dont wanna mess but they might be able to give us a version without all the baggage
Just to bring some clarification to this, the issue isn’t generally casting player[Agent]. This works as intended as @Mineblo pointed out above.
The issue is trying to cast [player]Agent after retrieving the Agent from a listenable event. Below I have a snippet of my code from a Tycoon project that is running into this issue.
Thankyou for confirming the issue i just assumed it was the direct agent cast does it also show the loop error for your await() ? doesn’t seem like it in your snip
Yes the solution is to add a break in the loop (I added Sleep(0.0) as shown in the code which cleared the error but I have not tested it)
I see yeah, I did not realize this. Thank you for the clarification!
since technically the code will run is this required ? i understand it will hide the error but im thinking if i add that on all the ones i have which is a lot then i would have to remove them when its fixed hopefully soon
I usually don’t use them but I’ve seen others use it in the past. I believe there is some sort of benefit but I am not exactly sure
Facing same issue
Still having the same issues. Not only with player casting but as reported elsewhere any loops or subscribable events are un-usable.
With this I can’t even do any updated code due to these errors, which is stopping a lot of work from being done.
the code will build and you can publish with it so im unsure what you mean ? I think its more the visual red wiggles/errors that make it difficult to write more version and potentially debug actual issues.
Are the loops working fine though?
yea everything is working fine ive even published its just a visual thing
Can confirm this bug seems visual, the code will build without further errors and function correctly.
