Custom Logo
Guide to using custom logos.
Step 1: Convert Image to .svg
Danger:
Putting "_" in the name can corrupt the entire process.
Note:
I recommend using Vector Magic to convert images.
💡 TIP:
The logo must be 64x64 and the name must not be longer than 5 characters.
Step 2: prepare the addon
Open local game files in the path Counter-Strike Global Offensive\game\csgo and open the gameinfo.gi file and change it as I did, I removed everything unnecessary so that our addon did not contain unnecessary files and added the path to the ranks (after unloading in the workshop you will need to return the file to its original state)
"VpkDirectories"
{
"include" "panorama/images/tournaments/teams"
}
Step 3: Create the addon
After opening, click Create New Addon and write any name convenient for you and click Create

Step 4: Inside Counter-Strike 2 Workshop Tools
Let's open the Assets browser window.

Step 5:
After creating the addon, we must go to the game files and go along the path Counter-Strike Global Offensive\content\csgo_addons\<addon_name>, and we remove everything.

Step 6:
We create folder for the place where our logos are located and place them there Counter-Strike Global Offensive\content\csgo_addons\<addon_name>\panorama\images\tournaments\teams.

Step 7:
After that, open Workshop Tools and click on the top right corner of Asset Types and click on (Only) Opposite Vector Graphic (.vsvg, .svg) and wait until our classifications load and look like images.

Step 8:
We see the post creation window, enter the Name and description and just as you can see, my addon only contains the logos (100% black band).

Step 9:
After submitting, the publishing page will open and now we have to wait for Steam publishing approval (it can take hours).

Step 10:
Don't forget to go back to the initial file
"VpkDirectories"
{
"exclude" "maps/content_examples"
"include" "maps"
"include" "cfg/maps"
"include" "materials"
"include" "models"
"include" "panorama/images/overheadmaps"
"include" "panorama/images/map_icons"
"include" "particles"
"include" "resource/overviews"
"include" "scripts/vscripts"
"include" "sounds"
"include" "soundevents"
"include" "lighting/postprocessing"
"include" "postprocess"
"include" "addoninfo.txt"
}
Step 11:
After our workshop publication has been approved, get your link id (in my case, https://steamcommunity.com/sharedfiles/filedetails/?id=3429470796 and id 3429470796).
Now in cfg/multiaddonmanager/multiaddonmanager.cfg as shown in the example.
If you already have something there, then we simply end it with the comma.
mm_extra_addons "3429470796"
mm_extra_addons_timeout 10
mm_addon_mount_download 0
mm_cache_clients_with_addons 0
mm_block_disconnect_messages 0
Step 12:
Now in configs/plugins/TeamIdentityManager, in the TeamLogo field just enter the file name (in my case teamlogo).
{
"RandomTeamLogos": false,
"RandomTeamNames": false,
"CtTeamName": "CT",
"CtTeamLogo": "teamlogo",
"TTeamName": "T",
"TTeamLogo": "teamlogo",
"ConfigVersion": 1
}
Credits:
To make this tutorial, I was based on the pisex tutorial.