Guns, Gore and Cannoli 2 review

Skip

by Tzeelim

Product overview of Guns, Gore & Cannoli 2 From Crazy Monkey Studios Unlike around the first Part, GGC2 has added another Tracker here, reading out Player data every Second To Third-party Vendors. Google Analytics Process: ggc2:6616 Method: POST Url: HTTP://WWW.GOOGLE-ANALYTICS.COM/COLLECT HTTP/1.1 User Agent: Mozilla/5.0 (Windows NT 10; WOW64) Example: Vaque 1&Tidwn UA-26276791-18&cidt-ups xxxxxxx&taries screenview&cdphone-level-WarehousePart1&an=GGC2&av=release_1.0.4&ul=de&z=1889389733 tracking Pixel Details: FORMAT: GIF, 35 bytes, 1w x 1h, Global Color Table: 2 colors explanation of Variables v = Protocol version tid = Google Analytics Account-In the Case UA-26272791-1 is assigned to the Domains "crazymonkeystudios.com" and "gunsgorecannoli.com," Cid = ClientID Identification (e.g. SteamID or as coded generic) t = Tracking Method (Event) ec = event type (hole System Data of the User) ea = event action (used DPI, Graphics memory, Processor, etc.) ev = Event value (e.g. in Conjunction with DPI: Value 96) ni = Declared Hit as non-interactive to = Program name (GGC2) av = program version (1.0.4) ul = Voice Settings of the Users sr = Used Resolution in the Game cd = Screen name (e.g. main Menu (E.g. MainMenu, level-cutscene, Level-WarehousePart1)) qt = Wait Time (to collect Offline data) | Value here at 11838 z = Cache Buster As can be seen on an obrigged URl, not much fits in, so the Service rushes in The Background During game Initialization and then with every Action of the Player with updated data spam-like and renews itself with Various Variables. A few Examples are in the list above. Based on this, it is possible to follow player actions (ev, ea, ec, cd) step by Step. Unity3D Method: POST Urls: Cdp.cloud.unity3d.com, api.uca.cloud.unity3d.com, config.uca.cloud.unity3d.com User Agent: UnityPlayer/5.6.2f1 (http://unity3d.com) Used Unity License: Advanced Pro Condified "Standard" Records of Unity collected by Player Be. AppID, unique User/Sessionid to track and identify the player, Device ID, Device Info, Operating System 64/32 Bit, product version, Motherboard, device name (indicated by the user When Installing the Operating system), processor/GHZ, Nets used, Clock Frequency, Ram, Vram, resolution, Dpi, Language, sensors, graphics Carte/Manufacturer/DirectXLevel, Shader, GFX-Api/Textureinfos/Flags/Cubemaps etc. This Service, too, rushes through in a Tour ... [04.06 17:05:09] ggc2.exe * 64-cdp.cloud.unity3d.com:443 open [04.06 17:05:10] ggc2.exe * 64-cdp.cloud.unity3d.com:443 close, 1664 bytes (1.62 KB) sent, 3701 bytes (3.61 KB), received lifetime 00:01 [04.06 17:05:12] ggc2.exe * 64-api.uca.cloud.unity3d.com:443 open [ 04.06 17:05:13] ggc2.exe * 64-api.uca.cloud.unity3d.com:443 close, 1607 bytes (1.56 KB) sent, 3701 bytes (3.61 KB) Received, lifetime 00:01 conclusion Unlike the first Part, a second Service was added here. There are no Hints about Analytics again. Likewise, the Optionality is lacking and processed again by Third-party Providers ... Even if the Developer Studio may have Access to it. Block of these Addresses is therefore recommended before the Start of The game via hosts or at DNS level. And who knows ... Maybe there is also a third Tracker in the third Part;] Until then, have Fun with this "Metal Slug" ^^