Font-n-Clock | フォントな時計 1.0.0

[mizznoff]

mizznoff submitted a new resource:

Font-n-Clock | Clock overlay with customizable fonts - Digital clock source that works with custom local fonts

View attachment 121069

(The English version is below.)

フォントな時計

PCにインストールされたフォントを使用して、配信画面に載せる時計素材を作成できるプラグインです。

インストール方法

Windowsの場合:
(1) Font-n-Clock-1.0.0-windows.zip をインストールしてください。
(2) エクスプローラーを開き、アドレスバーに C:¥ProgramData¥obs-studio と入力してください。
View attachment 121068

(3)...

Read more about this resource...

 

[Decors]

I can't edit or reply to rating so posting here.

Looks like portable mode does not support the module directory structure.

Regarding the installation instructions:In OBS Studio portable mode, external paths like "C:\ProgramData\obs-studio\plugins\..." are completely ignored. Furthermore, OBS portable mode does not scan subdirectories like "plugins/<name>/bin/64bit/" inside the portable root either. It strictly only scans the classic flat paths:- <OBS-Root>/obs-plugins/64bit/*.dll- <OBS-Root>/data/obs-plugins/<name>/Because of this, users running OBS in portable mode cannot use the plugin as packaged, and must manually extract the files into those classic flat directories to make it work.
With that said, you should use standard data/ and obs-plugins/ structure.

 

[mizznoff]

I see, Portable Mode was out of consideration. Thank you for the additional information.

However, C:\ProgramData is currently recommended as the installation destination for OBS plugins (my explanation also follows this).

Plugins Guide | OBS

OBS Knowledge Base. Install and remove OBS Studio plugins the manual way

obsproject.com

With that premise in mind, I investigated and confirmed that plugins are recognized even in Portable Mode if you place them as follows:

• Font-n-Clock\bin\64bit\Font-n-Clock.dll -> <OBS-Root>\obs-plugins\64bit\
• Font-n-Clock\data\* -> <OBS-Root>\data\obs-plugins\Font-n-Clock\

(Reference: https://obsproject.com/forum/resources/sceneanchor.2666/)

Would you mind trying this method?

 

[Decors]

However, C:\ProgramData is currently recommended as the installation destination for OBS plugins (my explanation also follows this).

Plugins Guide | OBS

OBS Knowledge Base. Install and remove OBS Studio plugins the manual way

obsproject.com

With that premise in mind, I investigated and confirmed that plugins are recognized even in Portable Mode if you place them as follows:

• Font-n-Clock\bin\64bit\Font-n-Clock.dll -> <OBS-Root>\obs-plugins\64bit\
• Font-n-Clock\data\* -> <OBS-Root>\data\obs-plugins\Font-n-Clock\

(Reference: https://obsproject.com/forum/resources/sceneanchor.2666/)

Would you mind trying this method?

As you noted, that workaround is exactly what I pointed out in my previous post, and I have already verified that it works properly.
To sum up the current situation: the root problem is an oversight on OBS Studio's side. While the official documentation recommends the isolated module structure, OBS's portable mode was never updated to scan those subdirectories. Because external paths like ProgramData are completely bypassed, portable users are left unable to install the plugin out of the box.
Personally, I have already extracted the files manually and have it working, so it doesn't really affect me anymore. However, thinking about other portable users who will inevitably run into the exact same hurdle, wouldn't it be much better to adjust the packaging or installation instructions on your end?
Providing the classic obs-plugins/ and data/ layout—or at least documenting the portable method in the instructions—would allow them to install it seamlessly without running into this gap in OBS.

 

[mizznoff]

> Personally, I have already extracted the files manually and have it working,

I am glad to hear that.

> However, thinking about other portable users who will inevitably run into the exact same hurdle, wouldn't it be much better to adjust the packaging or installation instructions on your end?

You are completely right.
Based on your suggestions, I decided to update the description to guide users on the installation path for Portable Mode.
Thanks to your feedback, I realized that the installation method differs for Portable Mode, and I truly appreciate that.

On the other hand, now that the installation instructions for Portable Mode have been added, your initial review no longer reflects the current situation. Therefore, would you mind withdrawing your review and the 1-star rating?
I would like to make this plugin widely used, and a 1-star rating becomes a barrier to that.