Video yükleniyor...
Video Yüklenemedi
Introducing Brendan Editing Pack 3! Available now at: What’s inside? • 12 Exclusive Tutorials & 3 Edit Breakdown Videos • 100+ Project Files • CRT Overlays & 900+ Overlays • 5 Film CC's & 2 Signature CC's • Bonus: Shake Pack 1
15,819 görüntüleme • 1 yıl önce •via X (Twitter)
2 Yorum
Brendan1 yıl önce
Check out the edits in the pack: Preview CCs here:
SamusVisuals1 yıl önce
Do you need any specifox plug ins
![🎬Whimsical Reverie | Preview: Version 2.2 Outfit Gifts 🏮Exclusive Bonus Event Duration: After the Version 2.2 update on January 29, 2026 – March 2, 2026, 12:49 (UTC-7) During the event, you can purchase the outfit Poem of Emberlight at a discounted price of 1 Diamond if you have activated Monthly Gifts or are within its validity period. Spend 1 more Diamond to obtain its evolution outfit [Poem of Emberlight: Dizzy]! 🏮Flavors of Life Event Duration: After the Version 2.2 update on January 29, 2026 – March 2, 2026, 12:49 (UTC-7) During the event, complete tasks to earn [Supreme Flavor]. Collect the required number of [Supreme Flavor] to exchange for rewards, including the 4-star outfit [Tasting the World], the sketch for the outfit [Tasting the World], and Diamonds! 🏮Warm Wishes Event duration: February 14, 2026, 13:00 – March 2, 2026, 12:49 (UTC-7). During the Warm Wishes event, log in daily to open a Lucky Pack and receive a random gift. Log in for 5 days to receive all gifts, including the 3-star outfit [Warm Holiday], [Momo's Cloak: Blaze], Revelation Crystal *1, and Resonite Crystal *3! 🏮New Arrivals in the Starlit Shop The Starlit Shop in Version 2.2 is updating with fresh arrivals! The following will be available in the Limited-Time section: [Dress: Clear Rainbow], [Chest Accessory: Double-Petal Bonds], [Chest Accessory: Midnight Missive], [Pose: Fortune Follows], and [Pose: Wishing Wealth]. [Starlit Crystals] can be used to exchange for them. Please note: After the Version 2.2 update launches, all limited-time items in the Version 2.1 "Life as a Poem" Starlit Shop will be removed. Stylists, don't miss your last chance to grab these! —— ➤ Infinity Nikki Version 2.2 Chromatic Beings Everbright launches globally on January 29 (UTC-7)! ➤ Download Now: ➤ Join us on Facebook Group: #InfinityNikki #ChromaticBeingsEverbright](https://image.24vids.com/tw-2015638532052721676/amplify_video_thumb/2015637327524102146/img/zdn8sLyiA5tikMJJ.jpg)
![Love and Deepspace | The New 5-Star Memory Limited Wish Pool [Sylus: Kitten Included] is Coming Soon! "Cats are good at entertaining themselves. Humans are different, though. This one really misses his kitten." 💫Event Duration: From 05:00 on May 22 to 04:59 on May 31 (Server Time) 💫Limited 5-Star Memory Rate Up 1. During the event, the drop rate of the limited 5-Star Memory [Sylus: Kitten Included] will go up drastically. 2. After the event ends, this limited 5-Star Memory will not be obtainable through other means and will not enter the permanent Wish Pool: Xspace Echo. 3. All Limited Wish Pools share one pity system. A 5-Star Memory is guaranteed within a specific number of Wishes. If the 5-Star Memory you have obtained from the Limited Wish Pool is not the event-limited Memory, you will obtain the event-limited Memory the next time you obtain a 5-Star Memory. The pity count from the last Limited Wish Pool can be applied to this Limited Wish Pool, and pity count from this Wish Pool will also be applied to the upcoming Limited Wish Pool. *You can read more about the event on the in-game rule page. 💫Dragon Li's Blessing: Wish Rewards During the event, after making a certain number of Wishes, you can claim various rewards, including [Sylus: Kitten Included] Exclusive Memory-Themed Outfit [Citrus Spark], Universal Hat [Brimlight Still], General Photo Pose [There, There], [Deepspace Wish: Limited*20], Memory Ascension Materials, etc. Notes: 1. The reward Photo Pose and Accessory will be available in Lunar Shop after this round of events ends. 2. After the event ends, the exclusive reward outfit will not be obtainable through other means. It will be rerun alongside the wish event in the future. The cumulative wish history from the first run of this wish event will apply to its Rerun Wish Pool. 3. The cumulative wish rewards are only available during this wish event. *Actual effects of the Outfit and Accessory may vary in-game. 🎁New Packs During the event, the new [Softfluff Pack] and [Sweet Indulgence Pack] series, which include [Deepspace Wish: Limited] and other materials, will be available in Shop. Both [Deepspace Wish] and [Deepspace Wish: Limited] can be used for the Limited 5-Star Memory wishes, with [Deepspace Wish: Limited] being prioritized for use. *After the event ends, [Deepspace Wish: Limited] will automatically convert to Empyrean Wishes. ——— 🪐Official Discord: 🪐Download and Log in Now: #LoveandDeepspace #Sylus](https://image.24vids.com/tw-2056578603278532847/amplify_video_thumb/2056573216207110144/img/8MCoXkxZGHp-bnYK.jpg)
![✨ I made a 100% AI video of a single night in 🇩🇪 Berlin's underground techno scene Doing an AI shoot is very much like a real life shoot, you have to prepare locations, settings, outfits and models, you can do the same: 1) First I generated photos with the [ 🇩🇪 Berlin nightlife ] photo pack on they're all non-existing AI people except me and my gf 2) Then I put the pics I liked in Kling AI to make them into 10 second videos (with Professional Mode), soon I'll have API access and it'll be one-click inside Photo AI to turn a photo into a 10-sec video, it then takes about 5 minutes to make a video. It's not always great, especially dancing is hard to get right! 3) Then I wanted to have a German narrator talking about Berlin's techno nights in a poetic way like a documentary, so I asked ChatGPT 4o: "write in the style of a cult German novelist about the Berlin techno scene" I then copied that text into Eleven Labs and selected a German AI voice 4) I then collected all the videos, the music and the audio narrator and edited them together in Final Cut Pro adding music from HÖR and adding audio effects 5) Then I added English captions with CapCut Time to make it: 3 hours for 1 minute of video I hope you like it! My dream is to have this entire pipeline in Photo AI at some point. Connecting to Kling AI's video API is the first step to that. Imagine just writing a prompt and you end up with a video like this without all the work Credits: Music: Asquith - Let Me (Rave Mix) [ASQ004] Barbax - Si Vis Pacem Para Bellum (Original Mix) Mixed by Ellen Allien @ HÖR Video: 100% AI characters and video by Photo AI Edited by me Narrator voice: 100% written by ChatGPT 4o 100% narrated by Eleven Labs AI voice](https://image.24vids.com/tw-1836017413650829587/ext_tw_video_thumb/1836016292328865792/pu/img/pZMR0VCR6sYaD8Vj.jpg)
![Hezbollah has been boasting how it could destroy the USS Gerald R. Ford (CVN-78) and its escorts. Lets dive into how Hezbollah Terrorists could attack a US Navy Aircraft carrier in the Med, what could happen, and the possible outcomes, assisted with Command Development Team simulation software. To understand the footage shown, let me break down some basic concepts of modern naval combat: Military ships often use a concept called "EMCON", which stands for EMission CONtrol, or "Radio silence" in laymans terms. Consider it like this: if you are with a flashlight in the night, you can spot a person say 500 Meters away by shining at him with the flashlight. You will however, be able to see that flashlight from many kilometers away, without being seen, even if it is directed at you, giving you the location of the person with the flashlight, without disclosing your presence. So ships really avoid "radio emissions", such as radar. Carrier Strike Groups (CSG) like the Ford CSG WANT Radar coverage for their own safety, but not in a way that their location can be known. This is done by Airplanes that fly in the general vicinity of the CSG, providing coverage, without compromising the CSG location. The US Navy uses the E-2 Hawkeye for this in most cases. In this case here, we are not using the E-2 Hawkeye, but the (likely in Theater anyway) E-3 Sentry from NATO. A system that is likely LESS sophisticated than the cutting edge E-2D Advanced Hawkeyes that were visible on the USS Ford pictures that surfaced recently. We do not simulate any carrier based "Combat Air Patrol" either, to test the "ship based" defenses. The composition of the Ford CSG is modeled using the actual ships listed. The CSG is moving on a nothern course at 15 knots, under full EMCON, 115 miles off the coast. The maximum range of the Russian Bastion-P coastal missle complex is about 100 miles, we have to assume that the US Navy will sail their ships outside of (possible) Hezbollah radar range. We also assume, as this is a time of very heightened alert, that the US Navy has Rules of Engagement that would allow it to shoot down any Hezbollah drones or craft coming at it with apparent hostile intention. I have assumed this to be 50 miles away from the CSG in this scenario. Now lets look at the Hezbollah side. We assume to have 6 Bastion-P complexes, with 2 missles per Transport-Erector-Launcher (TEL). So if it can be figured out where the CSG is, 12 P-800 Oniks missle with speeds over Mach 2 would be able to engage the CSG. The problem however is, that you can not "shoot" at a ship without knowing its location. While this may sound very simple indeed, when the ship you are looking for does not disclose its location voluntarily, you can not go to "marinetraffic" and look for the carrier. You can also not use your airforce, if you do not really have one, like Hezbollah. You can not use Sattelites, if you have none. You can try to use drones, if you know the overall direction, or use radar. Land based Radar? Out of Range. Drones? Yes, lets fly drones to the overall direction, hoping to see the carrier. Satellites? Nope. Wait, lets ask Putin. He will probably be nice enough to us, to have a liasion tell us in real time from a russian sattelite where the CSG is. And thats what we are running with here, as drones will not reach the carrier. A russian sattelite could provide rather real time information on the CSG location, allowing manual targeting. The video will provide you with the results. A US CSG with such powerful escorts will not be fundamentally threatened by the assets of Hezbollah. It will have to defend, but will do so rather easily. At the conclusion of the Engagement, the CSG still has literally 100s of SM-2, SM-6 and ESSM Missles. Note: this is done on commercially available software, the software uses NTDS/APP6 icons, white is air radar range, yellow surface, green sonar. The white cones off the missles are their onboard active radar seeker. If you have any questions understanding any of the things displyed, please ask. Note that this is a hobby analysis with publicly available data and tools, and not military research. Thanks for reading! #usnavy #HezbollahTerrorists #hezbullah #hezbollah #israel #IsraelUnderAttack #ukraine #russia #nato Naval News SubBrief Tyler Rogoway Status-6 (War & Military News) TheIntelFrog @CovertShores Raw Combat log output, starting with Hezbollah detecting CSG via RU Proxy: 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1070 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1071 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1072 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1073 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1145.4nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1074 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1153.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1075 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1148nm 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1073 has been positively identified as: DDG 63 Carney [Arleigh Burke Flight I] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1121 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1071 has been positively identified as: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1070 has been positively identified as: CVN 78 Gerald R. Ford - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1072 has been positively identified as: DDG 61 Ramage [Arleigh Burke Flight I] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1074 has been positively identified as: DDG 80 Roosevelt [Arleigh Burke Flight IIA] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1129 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1075 has been positively identified as: CG 60 Normandy [Ticonderoga Baseline 3, VLS] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1124 nm) 13/10/2023 12:47:23 - [USA] Contact: BOGEY #24 has been classified as: Ababil-3 UAV [Mod. Seeker 2D Copy] - Determined as: Unfriendly (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: AN/SPY-1D(V) MFR [ABM Mod]] [NCTR mode] at 56.9 nm) 13/10/2023 12:47:23 - [USA] Contact: BOGEY #26 has been classified as: Shahed-161 UAV - Determined as: Unfriendly (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: AN/SPY-1D(V) MFR [ABM Mod]] [NCTR mode] at 34.9 nm) 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3507 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 95.2nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3508 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.4nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3509 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 95.6nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3510 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.8nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3511 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.1nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3512 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.4nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3513 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 97.1nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3514 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 98nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3515 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 97.2nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3576 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 68deg - 91nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3577 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 89.9nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3578 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 90.7nm 13/10/2023 12:48:13 - Side 'Hezbollah' is now considered HOSTILE to USA 13/10/2023 12:48:13 - [USA] Contact: Shahed-161 UAV #26 has been manually marked as hostile! 13/10/2023 12:48:20 - [USA] Contact: BOGEY #22 has been manually marked as hostile! 13/10/2023 12:48:55 - [Hezbollah] New contact! Designated SAM #1238 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 266deg - 10nm 13/10/2023 12:48:59 - [Hezbollah] New contact! Designated SAM #1243 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 266deg - 8.6nm 13/10/2023 12:49:00 - [Hezbollah] New contact! Designated SAM #1245 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 234deg - 13.3nm 13/10/2023 12:49:17 - Weapon: RIM-174A ERAM SM-6 Blk IA #40 is attacking Shahed-161 UAV with a base PH of 90%. PH adjusted for weapon speed: 36% (pure-aerodynamic attitude control). Intercept angle is 304 deg - hit probability adjusted to 25%.Final PH: 25%. Result: 30 - MISS 13/10/2023 12:49:17 - [Hezbollah] Hezbollah :Contact SAM #1238 has been lost. 13/10/2023 12:49:25 - [Hezbollah] New contact! Designated SAM #1271 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 248deg - 13.1nm 13/10/2023 12:49:34 - Weapon: RIM-174A ERAM SM-6 Blk IB #41 is attacking Ababil-3 UAV [Mod. Seeker 2D Copy] with a base PH of 90%. Intercept angle is 51 deg - hit probability adjusted to 65%.Final PH: 65%. Result: 12 - HIT 13/10/2023 12:49:34 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:34 - [Hezbollah] Hezbollah :Contact SAM #1271 has been lost. 13/10/2023 12:49:34 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has been destroyed! 13/10/2023 12:49:34 - [USA] Contact Ababil-3 UAV [Mod. Seeker 2D Copy] #23 has been lost. 13/10/2023 12:49:39 - Weapon: RIM-174A ERAM SM-6 Blk IB #42 is attacking Ababil-3 UAV [Mod. Seeker 2D Copy] with a base PH of 90%. Intercept angle is 313 deg - hit probability adjusted to 66%.Final PH: 66%. Result: 11 - HIT 13/10/2023 12:49:39 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:39 - [Hezbollah] Hezbollah :Contact SAM #1243 has been lost. 13/10/2023 12:49:39 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has been destroyed! 13/10/2023 12:49:39 - [USA] Contact Ababil-3 UAV [Mod. Seeker 2D Copy] #24 has been lost. 13/10/2023 12:49:43 - Weapon: RIM-174A ERAM SM-6 Blk IB #43 is attacking Shahed-161 UAV with a base PH of 90%. Intercept angle is 65 deg - hit probability adjusted to 57%.Final PH: 57%. Result: 11 - HIT 13/10/2023 12:49:43 - [Hezbollah] Shahed-161 UAV has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:43 - [Hezbollah] Hezbollah :Contact SAM #1245 has been lost. 13/10/2023 12:49:43 - [Hezbollah] Shahed-161 UAV has been destroyed! 13/10/2023 12:49:43 - [USA] Contact Shahed-161 UAV #25 has been lost. 13/10/2023 12:49:54 - [Hezbollah] New contact! Designated SAM #1301 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 258deg - 10.5nm 13/10/2023 12:50:10 - Weapon: RIM-174A ERAM SM-6 Blk IA #44 is attacking Shahed-161 UAV with a base PH of 90%. PH adjusted for weapon speed: 83% (pure-aerodynamic attitude control). Target signature modifier: -5% (Director [Active Radar Seeker] has tech-gen: Late 2010s). Intercept angle is 316 deg - hit probability adjusted to 59%.Final PH: 59%. Result: 42 - HIT 13/10/2023 12:50:10 - [Hezbollah] Shahed-161 UAV has suffered weapon damage: 89 DPs 13/10/2023 12:50:10 - [Hezbollah] Hezbollah :Contact SAM #1301 has been lost. 13/10/2023 12:50:10 - [Hezbollah] Shahed-161 UAV has been destroyed! 13/10/2023 12:50:10 - [USA] Contact Shahed-161 UAV #26 has been lost. 13/10/2023 12:51:58 - [USA] Contact: VAMPIRE #3507 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3508 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3509 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3511 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:00 - [USA] Contact: VAMPIRE #3510 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:00 - [USA] Contact: VAMPIRE #3512 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:04 - [USA] Contact: VAMPIRE #3513 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:04 - [USA] Contact: VAMPIRE #3577 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:05 - [USA] Contact: VAMPIRE #3514 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:05 - [USA] Contact: VAMPIRE #3515 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:06 - [USA] Contact: VAMPIRE #3576 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:06 - [USA] Contact: VAMPIRE #3578 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:08 - Weapon: RIM-162D ESSM #45 is attacking SSC-5 Stooge [P-800 Yakhont] #28 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 357 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 34 - HIT 13/10/2023 12:52:08 - [USA] Contact GuidedWeapon #3507 has been lost. 13/10/2023 12:52:09 - Weapon: RIM-162D ESSM #46 is attacking SSC-5 Stooge [P-800 Yakhont] #29 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 31 - HIT 13/10/2023 12:52:09 - [USA] Contact GuidedWeapon #3508 has been lost. 13/10/2023 12:52:11 - Weapon: RIM-162D ESSM #49 is attacking SSC-5 Stooge [P-800 Yakhont] #32 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 36 - HIT 13/10/2023 12:52:11 - [USA] Contact GuidedWeapon #3511 has been lost. 13/10/2023 12:52:11 - Weapon: RIM-162A ESSM #52 is attacking SSC-5 Stooge [P-800 Yakhont] #31 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 355 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 9 - HIT 13/10/2023 12:52:11 - [USA] Weapon: RIM-162A ESSM #57 has been redirected to new target: GuidedWeapon #3515 13/10/2023 12:52:11 - [USA] Contact GuidedWeapon #3510 has been lost. 13/10/2023 12:52:12 - Weapon: RIM-162D ESSM #50 is attacking SSC-5 Stooge [P-800 Yakhont] #30 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 356 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 25 - HIT 13/10/2023 12:52:12 - [USA] Contact GuidedWeapon #3509 has been lost. 13/10/2023 12:52:12 - Weapon: RIM-162A ESSM #55 is attacking SSC-5 Stooge [P-800 Yakhont] #33 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 355 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 20 - HIT 13/10/2023 12:52:12 - [USA] Weapon: RIM-162A ESSM #59 has been redirected to new target: GuidedWeapon #3576 13/10/2023 12:52:12 - [USA] Contact GuidedWeapon #3512 has been lost. 13/10/2023 12:52:13 - [USA] Weapon: RIM-162D ESSM #47 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:14 - [USA] Weapon: RIM-162D ESSM #48 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:15 - Weapon: RIM-162A ESSM #57 is attacking SSC-5 Stooge [P-800 Yakhont] #36 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 0 deg - hit probability adjusted to 80%.Final PH: 80%. Result: 71 - HIT 13/10/2023 12:52:15 - [USA] Contact GuidedWeapon #3515 has been lost. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #60 is attacking SSC-5 Stooge [P-800 Yakhont] #34 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 360 deg - hit probability adjusted to 80%.Final PH: 80%. Result: 49 - HIT 13/10/2023 12:52:16 - [USA] Weapon: RIM-162A ESSM #65 has no eligible alternative target to be redirected to... 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3513 has been lost. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #51 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #54 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #58 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #59 is attacking SSC-5 Stooge [P-800 Yakhont] #38 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 357 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 75 - HIT 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3576 has been lost. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #63 is attacking SSC-5 Stooge [P-800 Yakhont] #38 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 359 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 57 - HIT 13/10/2023 12:52:16 - [USA] Weapon: RIM-162A ESSM #70 has been redirected to new target: GuidedWeapon #3514 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3577 has been lost. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #53 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162A ESSM #65 has no eligible alternative target to be redirected to... 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #56 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #61 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:18 - Weapon: RIM-162A ESSM #70 is attacking SSC-5 Stooge [P-800 Yakhont] #35 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 63 - HIT 13/10/2023 12:52:18 - [USA] Contact GuidedWeapon #3514 has been lost. 13/10/2023 12:52:18 - Weapon: RIM-174A ERAM SM-6 Blk IA #73 is attacking SSC-5 Stooge [P-800 Yakhont] #39 with a base PH of 90%. Intercept angle is 355 deg - hit probability adjusted to 88%.Final PH: 88%. Result: 34 - HIT 13/10/2023 12:52:18 - [USA] Contact GuidedWeapon #3578 has been lost.](https://image.24vids.com/tw-1712917679114207477/ext_tw_video_thumb/1712917122450419712/pu/img/CBxmEA_xSAI9jj3d.jpg)
![HERMES AGENT HAS 5 SYSTEMS RUNNING UNDER THE HOOD. UNDERSTAND THEM AND YOU USE THE AGENT 10X BETTER. In this video Alejandro AO 🤗 explained: 1. THE AGENT LOOP every message triggers the same cycle: → you send a message → Hermes builds context (SOUL.md + memory.md + user.md + skills + tools + message history) → sends everything to the LLM → LLM decides: call a tool or respond → if tool call: execute, return result, loop back → if response: deliver to you → after response: memory update (agent checks if anything is worth remembering, writes to memory.md or user.md) this loop is why Hermes gets better over time. the memory update after every response means the agent learns from every conversation. 2. CONTEXT ASSEMBLY what the LLM sees on every turn: → SOUL.md (your agent's personality and rules) → memory.md (facts the agent learned over time) → user.md (facts about you, auto-updated) → AGENTS.md and .hermes.md (project context files) → skill descriptions (loaded on demand) → tool schemas (available actions) → message history (current conversation) if SOUL.md is empty, Hermes falls back to a default system prompt. write your own SOUL.md and the agent becomes yours, not generic. CONTEXT COMPRESSION: conversations hit context limits. Hermes handles this at two checkpoints: preflight: before each turn. if conversation exceeds 50% of context window, compression fires. older messages get summarized. last 20 messages stay intact (protect_last_n). gateway auto-compression: between turns. fires at 85%. more aggressive. prevents API errors before the agent even starts processing your message. after compression, a new session lineage ID is generated. the agent can trace back to the original conversation through SQLite. three things break prompt cache: switching models mid-session, changing memory files, or changing context files. 3. THE GATEWAY the system that keeps Hermes reachable on 27+ messaging platforms. an async loop runs continuously. listens for incoming messages from Telegram, Discord, Slack, WhatsApp, email, SMS, and every other adapter. when a message arrives: → gateway identifies which session it belongs to → queries SQLite for the full message history (session ID = platform prefix + chat ID) → builds the context from scratch → sends everything into the agent loop → delivers the response back to the platform the gateway also runs the session manager. when you send a message while the agent is busy: → default: queued for next turn → /steer: injected without interrupting → /interrupt: stops current work without the gateway, Hermes is a CLI tool. with the gateway, Hermes is an always-on agent you reach from your phone. 4. MEMORY (THREE LAYERS) LAYER 1 — MARKDOWN FILES SOUL.md (identity), memory.md (learned facts), user.md (facts about you). injected into context after the system prompt. updated by the agent after every response. LAYER 2 — SQLITE full transcripts of every session stored locally. FTS5 full-text search across all past conversations. session lineage tracking across compressions. the agent can recall what you discussed weeks ago using /recall or session search. LAYER 3 — EXTERNAL PROVIDERS (optional) 8 supported providers: Mem0, SuperMemory, Honcho, Zep, and more. each works differently (semantic search, LLM extraction, similarity matching). queried after the first message in each session. the agent processes your topic first, then checks external memory for related context from past conversations. not enabled by default. enable for significantly better long-term recall. 5. CRON ENGINE a loop inside the gateway ticks every 60 seconds. each tick checks ~/.hermes/cron/jobs.json for scheduled tasks. if a job is due: → fresh session (no chat history, no memory pollution) → execute the prompt with assigned tools → store the run output as markdown in ~/.hermes/cron/output/[job-id]/ → deliver result to your home messaging platform cron does NOT use the send_message tool. delivery happens at the system level, not the agent level. a cron session cannot create more cron jobs. prevents runaway loops. WHY THIS MATTERS: the agent loop teaches it. the context assembly focuses it. the gateway reaches it. the memory remembers it. the cron engine automates it. five systems. one agent. understanding how they connect changes how you configure every level. full 15 levels breakdown in the article 👇](https://image.24vids.com/tw-2069309997008224672/amplify_video_thumb/2069308076566478848/img/ERC35adthbsEENqN.jpg)
![Use this prompt in OpenClaw to create your own AI agent command center that syncs up your life like Tony Stark's Jarvis in Iron Man. Adapt the specifics (agent names, data sources, branding) below to your own setup. Prompt: Build me a mission control dashboard for my OpenClaw AI agent system. Stack: Next.js 15 (App Router) + Convex (real-time backend) + Tailwind CSS v4 + Framer Motion + ShadCN UI + Lucide icons. TypeScript throughout. This is the command center where I monitor and control my autonomous AI agent(s) running on OpenClaw. The agent operates 24/7 on a Mac Mini, connected to Telegram/Discord, running cron jobs, spawning sub-agents, and reading/writing to a filesystem-based memory and state system. Dark mode only. Ultra-premium aesthetic, think Iron Man's JARVIS HUD meets a Bloomberg terminal. Subtle glass effects (backdrop-blur-xl, bg-white/[0.03]), no heavy gradients or glow. Rounded corners (16-20px on cards). Framer Motion for page transitions, stagger animations on card grids, spring physics on interactions. Mobile-first responsive. Never cookie-cutter. ## Architecture The dashboard reads live data from TWO sources: 1. **Convex**: real-time database for structured data (tasks, contacts, content drafts, calendar events, activity logs) 2. **Local API routes** (`/api/*`): read files from the agent's workspace filesystem at `~/.openclaw/workspace/` and return JSON. This is how live system state flows into the dashboard. ## Pages & Views (8 nav items, some with tab sub-views) ### 1. HOME (`/`) Dashboard overview. Grid of live status cards: - **System Health**: read from `/api/system-state` (parses `state/servers.json`). Show each service with UP/DOWN indicator, port, last check time. - **Agent Status**: read from `/api/agents` (parses `agents/registry.json` + agent workspace files). Show active agent count, healthy/unhealthy ratio, active sub-agent count from OpenClaw sessions API. - **Cron Health**: read from `/api/cron-health` (parses `state/crons.json`). Table of all scheduled jobs with name, schedule, last status (green/red dot), consecutive errors. - **Revenue Tracker**: read from `/api/revenue` (parses `state/revenue.json`). Current revenue, monthly burn, net. - **Content Pipeline**: read from `/api/content-pipeline` (parses `content/queue.md`). Kanban-style: Draft | Review | Approved | Published counts. - **Quick Stats**: total tasks, pending approvals, active sessions, uptime. All panels auto-refresh every 15 seconds. Live indicator dot + "AUTO 15S" badge in header. ### 2. OPS (`/ops`) with 3 tabs: Operations | Tasks | Calendar **Operations tab:** Full operational view. Server health table, branch status (from `state/branch-check.json`), observations feed (from `state/observations.md`), system priorities (from `shared-context/priorities.md`). **Tasks tab:** Strategic task suggestion system. API route `/api/suggested-tasks` reads/writes `state/suggested-tasks.json`. Cards grouped by category (Revenue, Product, Community, Content, Operations, Clients, Trading, Brand) with emoji headers. Each card shows title, reasoning, next action, priority badge, effort badge, approve/reject buttons. Filter bar by status and category. **Calendar tab:** Weekly calendar view from Convex `calendarEvents` table. Drag-to-create, color-coded by type, time slots. ### 3. AGENTS (`/agents`) with 2 tabs: Agents | Models **Agents tab:** Card grid of all registered agents from `/api/agents`. Each card shows name, role, model, level (L1-L4), status. Cards are CLICKABLE: expanding into a detail panel showing: - Agent personality (reads their SOUL .md) - Capabilities and rules (reads their RULES .md) - Sub-agents they can spawn - Recent outputs (reads from `shared-context/agent-outputs/`) **Models tab:** Model inventory table showing all available models, their routing (which tasks go to which model), costs, and failover chains. ### 4. CHAT (`/chat`): 2 tabs: Chat | Command **Chat tab:** Chat interface to communicate with the agent. Left sidebar shows session list (from `/api/chat-history` reading .jsonl transcript files). Main area shows messages with role-aligned bubbles (user right, assistant left), date separators, channel badges (telegram/discord/webchat). Input bar with send button + voice input (Web Speech API with SpeechRecognition). Messages sent via `/api/chat-send` which queues to a file the agent reads. **Command tab:** Quick command interface for common operations. ### 5. CONTENT (`/content`) Content pipeline management. Read from Convex `contentDrafts` table AND `/api/content-pipeline`. Show drafts in kanban columns. Each card shows title, platform target, draft text preview, status, created date. Edit/approve/reject actions. ### 6. COMMS (`/comms`) with 2 tabs: Comms | CRM **Comms tab:** Communication hub showing recent Discord digest, Telegram messages, notification history. **CRM tab:** Client pipeline kanban (Prospect → Contacted → Meeting → Proposal → Active). API route `/api/clients` reads markdown files from `clients/` directory. Each card shows client name, status, contacts, last interaction, next action. ### 7. KNOWLEDGE (`/knowledge`) with 2 tabs: Knowledge | Ecosystem **Knowledge tab:** Searchable knowledge base. Global search across all workspace files using `/api/knowledge` endpoint. **Ecosystem tab:** Product grid showing all products/apps in the ecosystem. Each card shows product name, status (Active/Development/Concept), health indicator, key metrics. Cards link to `/ecosystem/[slug]` detail pages with tabbed views (Overview, Brand, Community, Content, Legal, Product, Website, Actions). Detail pages read from `/api/ecosystem/[slug]` which parses workspace memory files. ### 8. CODE (`/code`) Code pipeline view. Shows repositories from `/api/repos` (scans ~/Desktop/Projects/ for git repos). Each repo card shows name, branch, last commit, dirty file count, language breakdown. Detail view at `/api/repos/detail` shows recent commits, file tree, open PRs. ## Navigation Top horizontal nav bar, NOT sidebar. All 8 items visible at all viewport widths. Use `flex` layout with `flex-1` items. Text size uses `clamp(0.45rem, 0.75vw, 0.6875rem)` for fluid scaling. Active item gets `text-primary bg-primary/[0.06]` static highlight (no sliding animation). Agent/app name visible at md+ breakpoints (`hidden md:inline`). Tab sub-views use a reusable `TabBar` component with pill/glass styling and Framer Motion `layoutId` transitions. Tab state stored in URL via `?tab=` search params. ## API Routes (all under `src/app/api/`) Each API route reads from the agent's workspace filesystem and returns JSON: - `/api/system-state` → reads `state/servers.json`, `state/branch-check.json` - `/api/agents` → reads `agents/registry.json`, agent SOUL .md files - `/api/agents/[id]` → reads specific agent's SOUL .md, RULES .md, outputs - `/api/cron-health` → reads `state/crons.json` - `/api/revenue` → reads `state/revenue.json` - `/api/content-pipeline` → parses `content/queue.md` (markdown with status markers) - `/api/suggested-tasks` → GET (read) / POST (approve/reject) on `state/suggested-tasks.json` - `/api/observations` → reads `state/observations.md` - `/api/priorities` → reads `shared-context/priorities.md` - `/api/chat-history` → reads .jsonl transcript files with pagination/search/channel filter - `/api/chat-send` → writes to queue file - `/api/clients` → reads markdown files from `clients/` directory - `/api/ecosystem/[slug]` → reads memory files for specific ecosystem - `/api/repos` → scans project directories for git repos - `/api/health` → returns status, uptime, memory usage, Convex connectivity All filesystem paths should be configurable via environment variable (default: `~/.openclaw/workspace/`). ## Convex Schema Define tables for: activities, calendarEvents, tasks, contacts, contentDrafts, ecosystemProducts. Include seed scripts (`convex/seed.ts`) to populate initial data. ## Key Design Rules - Mobile-first, test at 320px minimum - Font sizes 10-14px for body text, everything must fit naturally at small viewports - Cards use consistent border radius (16-20px) - Glass cards: `bg-white/[0.03] backdrop-blur-xl border border-white/[0.06]` - No heavy blur blobs or grain overlays - Stagger animations on card grids (0.05s delay per item) - Skeleton loading states for all async data - Custom scrollbar styling - Empty states with helpful messaging - All text must use Inter or system font stack - Never mix sharp and rounded corners in the same view - Premium = lighter feel, more whitespace, less visual noise ## File Structure ``` src/ app/ page.tsx, layout.tsx, providers.tsx agents/page.tsx calendar/page.tsx chat/page.tsx code/page.tsx comms/page.tsx content/page.tsx ecosystem/page.tsx, ecosystem/[slug]/page.tsx knowledge/page.tsx ops/page.tsx api/[...all routes above] components/ nav.tsx tab-bar.tsx dashboard-overview.tsx ops-view.tsx, suggested-tasks-view.tsx agents-view.tsx, models-view.tsx chat-center-view.tsx, voice-input.tsx content-view.tsx comms-view.tsx, crm-view.tsx knowledge-base.tsx, ecosystem-view.tsx code-pipeline.tsx activity-feed.tsx, calendar-view.tsx ui/ (ShadCN primitives) hooks/ lib/ convex/ schema.ts functions for each table seed.ts ``` Build the complete application. Every component, every API route, every Convex function. Production-quality code and premium design, not stubs. Dark mode only. Make it look incredibly beautiful and premium, no cookie cutter UI / AI slop.](https://image.24vids.com/tw-2022461932759060993/amplify_video_thumb/2022461533629091841/img/ccYthyhazjUQDwn3.jpg)