(Fixed) UEFN API Outdated - Should say Timer.Start instead of Timer.Begin

General Issues and Bug Reporting
,
1

Edit: This issue has now been fixed :+1: :slightly_smiling_face: Thanks! The API Digests were temporarily outdated.

In the API documentation, the function to start the timer is listed as Begin<public>(Player:player):void = external {} but it should actually say Start<public>(Player:player):void = external {} :eyes: :open_mouth:

image
image718×152 10.5 KB

I found this out when trying to program a timer. I was getting a red underline with the message " Unknown Member ‘Begin’ in ‘timer_device’

image
image1027×245 28.5 KB

I noticed that in the User Options - Function section of the Timer’s Details panel, Start is used instead of Begin, so I tried typing Start and it worked.
image

The same mistake in the API occurs with BeginForAll, which should be StartForAll.

Personally I like Timer.Start better than Timer.Begin because it matches the terminology FNC creators are used to seeing in the device menu, and because the existing OnBegin isn’t related to the timer.

I’m listing this as Major because if a creator can’t figure out how to start a timer in Verse because the API is mistaken, it could block the creator from moving forward with a script. But the mistake is super fixable on Epic’s end, so it’s kind of Minor in that sense? No big deal.

2

Just looked into this, it appears to have been fixed. Thank you!

1 Like
3

For sure, no problem! I’m really enjoying learning Verse. :blush: I’m still seeing Begin on my webpage: Epic Games

image
image713×650 46.3 KB
. Maybe it hasn’t updated on my end yet.

4

Oops I meant the post below to be a reply to you. Still getting used to the Forums. :arrow_down:

5

I mean the post above. Previous post. :laughing:

6

Oh boy, someday I will understand how replies work.

7

Thanks for mentioning this. It appears that the digests were out of date. I’ve just updated our documentation, but it there will be some delay as it goes through the publishing process. I did verify the specific issue with the Start/Begin function in timer_device, and it looks good.

3 Likes
8

Thank you! :slightly_smiling_face: :+1: I updated the title and description of this post to show that the issue has been fixed.