It does that because you declared the WakaTime messages that go to the log as warnings. Pushing a fix now.

ZIP archive is named WakaTimeForUE4-main or WakaTimeForUE4-release after downloading. So if user does not pay too much attention to folder name described in README file and just unpack archive and copies WakaTimeForUE4-main folder to Plugins, wakatime icon is not found by Style->Set. It's rendered just like a pink square.

Maybe there is some better way for naming or you could warn user specially in README?

1. It would be great if there would be a license in this repository, so you can (safely) use / extend / (... whatever the license allows) the plugin
2. There are copyright notices in the code reserving all rights to Epic Games. I guess they were meant for the default code when initializing a new plugin, but since this isn't the default code anymore they shouldn't be there at all (?)

Having a whitespace in your user folder causes the editor to exit on startup with the error "Path 'C:/Users/{name}' could not be found". The path is there, it just seems like the plugin cuts the path off at the space so instead of it searching for "My name" it searches for "My" which returns an error. Is there any way to allow white spaces so users with one in their user folders can open the plugin? I tried looking through the source code but couldn't find a way to let it see past spaces. (Creating this issue on behalf of one of my team members, other than that the plugin works great, thank you!)

This issue has already been tracked down and will be resolved in the next update ;)

Building a project a project with the plugin on windows generates the following warnings:

winnt.h(603): [C4005] 'TEXT': macro redefinition
Platform.h(1082): [C4005] see previous definition of 'TEXT'

Desktop

• OS: Windows
• Unreal Engine 4.26.2

Additional context
This due to the #include <windows.h> here

Since all WakaTime plugins seem to use the user's home dir as a config dir, I recommend doing the same here.
So at launch, we would read ~/.wakatime.cfg, see if there's an API key - if there isn't one, ask for it, and then put it in there. If there is, just continue loading. This way, all the WakaTime plugins, including this one, share one common config.

I will try to do this in the PR I opened.

Thanks

Today I accidentally noticed that my UE4 activity is not being logged!

WakaTime receives the heartbeats, but they don't appear on the dashboard, so perhaps the raw heartbeat data is faulty.

The reason could be that the heartbeat's is_write param is null, but I'm not sure.

https://wakatime.com/api/v1/users/current/heartbeats?date=2021-08-01&show=machine_name,user_agent

To view raw heartbeat data for the currently logged-in account (change the date as appropriate).

• #12
• #6
• #8
• Fix version in cpp:128 (command building)
• #14
  • #15
• #16
• #17
• #18

I already have about half of the code for this, so I will handle it to the end.

Hi I got a problem that I cant use this plugin.
my UE version is 4.27
and I got this on the opening

Who approved this? A global variable that gets freed without the module being shutdown?

Btw. its already happening on shutdown...

EDIT: Thanks to gitblame: Was introduced here 94148de

Results in:

Log          LogWakaTime               Running command:  /c start /b where /r Z��\.wakatime\wakatime-cli-windows-amd64.exe
Log          LogWakaTime               Did not find wakatime
Log          LogWakaTime               Running command:  /c start /b mkdir Z��\.wakatime
Log          LogWakaTime               CLI not found, attempting download.

LogTemp: Warning: WakaTime: Sending Heartbeat
LogTemp: Warning: WakaTime: Heartbeat successfully sent.

^ Shows up even though there is no way the heartbeat was actually sent due to no internet connection

• Has ide wakatime, has python
• Has cli, has python
• has python, doesn't have cli, doesn't have ide waka
• doesn't have python, nor cli

For a pass, the plugin has to be able to send a correct heartbeat

If using git in the current project, the plugin should fetch the current branch name and pass it along to the waka heartbeats. If someone is using the Projects feature in WakaTime, this can give useful insights as to which branches is your time going against, but since the plugin doesn't report this information, WakaTime just says "Unknown".

Hey,

Are you planning on implementing support of UE5 any time soon? I am working on migrating my projects to it and would love to use this plugin!

Thanks

Hi,

I am using WakaTime in many editors and IDEs.
They have installed the official version to ~/.wakatime/wakatime-cli
Now, the executable name within that dir is wakatime-cli.exe, not just wakatime. This way the system cannot find the executable. Removing the extension, on the other hand, causes the executable to be unrunnable.

I'm no Windows guru, so I don't really know what to do here. Tried making an alias, like I would do in Linux, but it doesn't work. Windows's "macros" are not very efficient and don't reportedly work in batch scripts.

Ideas?

Thanks

In UE5_Latest(Github::ue5-main)

WakaTimeForUE.cpp#L145:
FEditorDelegates::PostSaveWorld.Remove(PostSaveWorldHandle); -> FEditorDelegates::PostSaveWorldWithContext.Remove(PostSaveWorldHandle);

WakaTimeForUE.h:
Add #include "EditorStyleSet.h"

And

WakaTimeForUE.Build.cs:
Add "EditorStyle" Module

Because:
WakaTimeForUE.h#L145:
FEditorStyle::GetStyleSetName() // Error

When plugin is enabled, all packaging fails due to "Unknown Cook Failure".

Starting the editor without the plugin successfully packages the project.

I need to look into this issue, but I do not have a viable internet connection, so it has to wait a bit.
Sorry for the inconvenience.

When I try to save my project this error appears. Tested it with the command console typing "wakatime -h" and works fine as well as python and pip.

i see the logo of wakatime and i have the correct api key, but is not working

Scan the user home directory, looking for the .wakatime.cfg file. If it isn't there, create it. If it is there, check if it contains an API key. If it does, do nothing. If it doesn't, ask the user to input it and save it in there as api_key=<apiKey>.

Today, I have renamed the plugin from WakaTimeForUE4 to just WakaTimeForUE; the reason for this was the fact, that UE5 is out and the plugin is (more or less) compatible with UE5.

This issue will be kept open while it is true, so check it in case there is an issue. It might be listed here.

Possible issues

• There is an issue stating something about having the plugin in UE5Modules and whatnot... the solution to this issue is to move the plugin from the engine to the project.

After all the changes regarding wakatime cli, the code become really messy. It's time for a cleanup.