ArmCord rebranded to Legcord

[Andrew-J-Larson]

Still functionally the same, they just had to do a name change because of a cease and desist from Arm (the corporation).

More info about the name change is on their Discord: https://discord.com/channels/820732039253852171/821385577194717194/1294353795647668306

https://github.com/Legcord/Legcord

[Botspot]

Yeah I saw it. I have all necessary changes ready to push, but at the moment I have been having some trouble getting LegCord to launch.

[Botspot]

Lead dev of legcord has confirmed a launch bug and plans to fix it tomorrow.

[theofficialgman]

@Andrew-J-Larson just an fyi, I would classify this as a "Suggestion" based on our current descriptions as this is not a new application to pi-apps

let us know if we can provide any further clarification regarding our issue template descriptions.

[theofficialgman]

at the moment I have been having some trouble getting LegCord to launch.
Lead dev of legcord has confirmed a launch bug and plans to fix it tomorrow.

Any mention of that publicly? A quick scan of the discord and github didn't bring me any results.

[Botspot]

He says https://github.com/Legcord/Legcord/releases/tag/v1.0.1 should work.

[theofficialgman]

I have all necessary changes ready to push

Regarding this, I am not sure what your plan was for this but I would prefer and recommend that the system standardized with our latest transition (Geekbench to Geekbench 5) be used here and the runonce be made just like that for Armcord -> Legcord.

[theofficialgman]

@Botspot it seems my recommendation was ignored f593c97#diff-7035412399e0395e1ed812fc1f3f1eb906b9b33e5149c2c2ab2916c1cc78c22bR175-R177

this won't work for users that have Armcord installed. They will be left with Armcord still installed and will not update to Legcord until the next pi-apps Legcord install script update after they have had this runonce executed.

The method I suggested avoids that issue.

[Botspot]

I apologize. I only saw your message after making the commit. Will fix.

[theofficialgman]

@Botspot I think branding is wrong here f593c97
It is Legcord not LegCord

[theofficialgman]

handled with 3a60909 (see commit message)