Загрузка видео...

Не удалось загрузить видео

На главную

⭐ALTITUDE'S 1V1 FFA⭐ -Added Pump Pullout (with broken pullout setting) -Tried fixing Infinite Tac Sprint again MAP CODE: 3427-2189-5758 Remember to favorite the map to support it! #UEFN #Verse Fortnite Developers

22,050 просмотров • 6 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

NEW YEAR, NEW GRIFT I saw a post about this and decided to look into it. Right now, the highest paid promoted slot is an RvB map with SINGLE PLAYER LOBBIES, that alone should raise eyebrows. This isn’t an accident. When you load into the map, you’re placed into a boxed area containing matchmaking portals that redirect players to another map using the same thumbnail, but under a different creator code. So why do this, I have an educated guess... The payment method tied to the promotion will be canceled and/or a stolen identity/credit card is used to run the promotion in the first place And when the fallout happens, who will get punished? The creator whose map ultimately received the traffic, highly unlikely... This mirrors patterns we’ve already seen with XP abuse and TikTok scam loops. The platform often cannot definitively prove that both accounts belong to the same individual, which means this can easily become a weaponized tactic to get other creators flagged, demonetized, or banned. So in the end, it seems this will be another situation that will end up abused and those willing to commit fraud will benefit. On any platform where money is involved, these types of individuals will do anything to earn a piece of the profits. Without stronger verification like biometric checks from Clear (similar to what platforms like LinkedIn already use) this type of abuse will continue. I am positive this is not what Epic had envisioned when creating the Promoted Row, I do think this needs to be addressed sooner than later though, as it is only going to get worse. Because if creators are already willing to do this so openly today, what should we expect once microtransactions are introduced? I feel guilty tagging, but I feel it is important to get eyes on this as soon as possible. Tim Sweeney Mark Rein Epic Games Store Fortnite Developers

Dustin (DWDFN)

15,106 просмотров • 6 месяцев назад

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,104 просмотров • 25 дней назад

🚁 My war drone simulator Apocalypse Drone now has support for 32 players! I also made it Conquest/CTF so you have multiple bases that you have to capture, each round the map is procedurally generated and random so every time it's different (like Battlefield) There's still some bugs to work out and most importantly I have to figure out soldier animations, because they're fixed models now But I have got really far this time I think and coding with AI is really way further than it was a year ago, you mostly notice that how few times you get stuck, only one time this month building this I got stuck which was today where I moved the AI players to the server and they kept showing up as invisible, very buggy, every time I told it that it couldn't fix it though Then I asked it to fundamentally analyze the current server-side AI player code and make it work like industry standard, and it took a long time and fixed everything Last year I'd get stuck hundreds of times and the AI just couldn't get itself out of a hole, but now it can I think it's impressive that just last year only for the first time we could make actual games with AI But this year as non-game dev, I can get pretty close to the level of a multiplayer game from 20y ago (like Battlefield 1942, that lots of ideas here are based on, but with drones :D) Obviously we're still far away from AAA (I hate that term though) but the curve of exponential progress is there again, as it was in AI image generation, then video, and now code, first bad, then better, then good enough! Here's a video of gameplay from my drone sim You can play it with the link in the reply below and it's multiplayer!

@levelsio

55,036 просмотров • 3 месяцев назад

OFFICIAL: EASTER EGG GUIDE FOR TOTENREICH: Wonder Weapon: 1. Head to The Drydocks and lower The Crane, this will allow you to wall jump and interact with the tip of the ship to pick up the Chain Link 2. Next, Head to Storm Bridge and pick up Chili Chunks behind the truck next to Deadshot 3. Place Chili Chunks on the table in the middle of the Skalen Market 4. Next, Head to Burial Grounds left-side door and interact with the keyhole. 5. Interact with the door again and hold it to open the door and to unlock the underground area. 6. This will spawn a Zursa Bear during a special round (starting the second special round) you need to kill him and he will drop The Lantern 7. Place The Lantern in the center of the Underground Room in Burial Grounds. 8. Constellations will appear around the wall. Interact with them as they’re shown on the table in this order: left, right, back, front. 9. Once completed, Astrid will appear and talk, she will then travel to different areas of the map. She will occasionally stop and you will need to kill frost zombies next to her. 10. Once all the Soulboxes are completed an Obstacle Course will form on the outside of The Lighthouse, climb to the top by Jumping / Wall Jumping up 11. Once you reach the top, Listen to the Astrid talk and pick up The Jotunn Star Wundersignal: 1. After completing Jotun Star Quest Head to The Lighthouse and inside on a shelf there will be a Crowbar 2. There are Multiple Wooden Boxes around the map with red IDs on the bottom right corner of the front of the box in red (for example III-6) use The Crowbar on the Wooden Box that has the Roboterteile ID (the IDs are on the shipping manifest in the War Factory Admin Room), this will give Flak Gun Round War Factory Core Foundry Fjord Road Dry Dock 3. Head to Turret Gun beside The Lighthouse and place Flak Gun Round then melee with Jotunn Star 4. Next, Head to The Robot Head in spawn and interact with it to search broken piece to get The Transmitter 5. Go to Tyr’s Head and place it inside the Wall Machine thingy at the top of the Ladder 6. Next, whilst inside of Tyr’s Head underneath the balcony there are 3 white lights, 2 of these lights will blink, count how many times it blinks -Both lights will remain on, There is the sound of a light turning on to indicate the start of a new light flashing cycle where both lights will flash at the same time to a certain count (for example left 2, right 5). Both lights will be on and then it will flash another set (for example left 6, right 4). (Unsure if these 2 combos have to be put into console in order but correct entry will give two different voicelines.) After entering one correctly you will be kicked out to hear voiceline and can re-enter console to input the 2nd shortly afterwards. 7. Now head to Core Foundry, and use a molotov to burn the ascender to access the consoles. 8. Ascend and interact with the consoles, The next part is timed and has a cooldown if you fail - you need to Calibrate the Amplitude and Frequency using the flashing light code. 9. Once this has been done head to the room Next to the Radio Tower and pick up The Wunderbarrage Controller Atomkraft Core 1. Find three uraniums: Uranium #1 Find the Fishing Rod (Olaf’s Personal Item) locations: - Dry Dock - Storm Bridge - Fishery Island - Beacon island Look for a Glowing Green Fish jumping around the water at each Fishing Location and use the Fishing Rod at that location once you see it Fishing Locations: Eidskallen Landing x2 Beacon Island x2 Eidskallen Square x2 Dry Dock (found one so far) Fishery Island x2 Tyr’s Foot (found one so far) Once the fish is caught it will spawn an Irradiated Ravager (HVT) that will disappear and respawn somewhere else, chase it down and kill it (check your map to see its location, it shows up as an HVT). It will drop a Uranium. Uranium #2 Next, Craft an ARC-XD (there is one for free in Eidskallen Square on top of a box near the flame trap, you can get it by fishing as well) and melee the vent at Core Foundry to the left of the zipline to open the Secret ARC-XD Course. Blow up the boat full of barrels. Once the course is completed the 935 Genetic Lab room will be open and another Uranium x2 will be inside a Prison Cell There are several Jars with Heads inside in this room, all labelled A,B,C,D,E Look down the Hallway inside the Lab and note which numbered rooms have Nuclear Symbols 1 = A, 2 = B, 3 = C, 4 = D and 5 = E Take one Jar at a time that corresponds with the Numbers next to Nuclear Symbols and place them on the machine to the right of the cell door, once the correct jars are placed the Jar on the left side of the machine will glow purple and you can pick up acid There is a Big Chunk of Meat on a desk next to multiple drawings in the same Room, interact with it, then Pick up The Necrospike Once you have The Necrospike, use it on the Prison Cell Door, this will trigger a lockpick mini game. Spin the lockpick until the lock turns white 3x to unlock the cell, then pick up the second Uranium. Uranium #3 Next you need to craft or obtain the Glocke Drop, once you have one call it in, then shoot 20 mid-air zombies it throws up. This will drop the third and final Uranium. 2. At the Dry Dock, you need to call a WunderBarrage (unlocked by completing Wundersignal steps) in on the “02 Building” at Dry Dock (where there’s debris on the stairs), this will open the stairs to the Machine Workshop. 3. Inside The Workshop there is a Claw Machine which you can place all of The Uranium inside of and play a mini-game. -Have a big group of 7 cores and a small group of 2 cores. 4. Once you complete the Mini-game you will be able to pick up The Atomkraft Core (Note: you drop if you zipline, and cant sprint with it) 5. Head to Quick Revive and place The Atomkraft Core on generator next to quick revive. Go into the shed behind quick revive and turn on the generator. You must now defend the The Atomkraft Core until it’s charged. In interrupted you must turn on the generator again to continue. 6. Take the The Atomkraft Core to the barrel on the Storm Bridge and a Mini-Cutscene will play between the Giant and The Robot. Vegvisir 1. After the cutscene finishes, The Dravakar Shard will spawn at Tyr’s Foot, pick it up 2. Pick it up and place the Shard inside the Bloodheim Hall on the bonfire 3. Use WW range attack to light the fire 4. Use Disciple Injection (there should be a free one around the map) and throw zombies into the bonfire (I only had to throw four) 5. A lockdown will start. Kill the boss zombie and pick up the Sunstone from the bonfire 6. Put the Sunstone in the church and do a range WW attack on it. 7. Around the map, there will now be floating rocks and runes. Above the church there will now be a compass with runes and arrows. -Shoot the floating rune rocks with the ranged WW in the order of the arrow lines. If an arrow has 1 line, then that's the first one. If an arrow has 2 lines, that's the second one, etc. 8. Go into Tyr's Head and interact with the console to start the boss fight. Credit to Callum and the ZoneX discord

COD: Zombies News

81,036 просмотров • 2 месяцев назад

Here is the Geometry Nodes Weighted Normals with Laplacian Blur on a full character (a vroid). It easily improves the shading even on game topology with almost no setup. I built this as part of my quest to improve real time toon shading. 3D anime models are popular, but use of dynamic light is rare even among high quality vtuber models. This is for several reasons, but a big one is simply that it takes a lot of Custom Normals work to make 3D cel shading not look like a jagged mess (other pieces of the puzzle are issues like deformations, multiple lights, etc). And fixing Normals is tedious, especially on existing game topology. I have focused on proxy meshes for priority areas like character faces, but they aren't an efficient solution for the whole body + outfit. I wanted something I could just throw on any model and make it at least not a jagged mess anymore even if it wasn't perfect. As you can see from this clip, this does that very well! And vertex groups can be used to control the style of the effect and power. It still can't smooth beyond what the topology density can support, but the topo itself is no longer a problem (for higher res, could be run on a subdivided version of the model and then baked to a Normal Map.) The only changes I made to this model were adding a weld modifier to merge split edges during interpolation, and a vertex group to select the skirt. I have not yet added full handling and logic for detecting edges with big angles like the skirt, or for handling boundaries like on the hair, so both those areas can get better too. You can also see that while it successfully smooths out the Face, it isn't really stylistically correct there. That is still best done with a proxy mesh to define a new shape. This is part of the tools I am working on for Fondant. We are putting together a Blender Addon to release this + a proxy mesh tool for the face, and are working on resolving other problems in-engine to fully bring dynamic light to real time 3D toon shading. Give us a follow, and send them a DM if you are interested in testing these tools as they develop!

aVersionOfReality

14,679 просмотров • 1 год назад

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,376 просмотров • 3 месяцев назад

Exposing Demus Pixx Darm. Is this really the competitive scene you want, Fortnite Competitive ? Normally, I wouldn’t care, just like I haven’t for the past few years, but we’re tired. Tired of it always happening to us. Tired of how impossible it is to compete on equal terms. It feels like it’s no longer about who’s better. It’s about who has more connections, who does more teaming, and who threatens others harder. We want to expose three situations that are clearly prohibited in the official FNCS rules, and that completely break the values of fair competition. ----------------------- 1. Repeated griefing and intentional suicides to prevent us from qualifying The team doing this was already qualified. And because we were their biggest threat in their POI, they spent the entire final part of Day 2 looking for us, pushing us, and leaving matches on purpose just to requeue and keep griefing. In the clips, you can clearly see how they eliminate us and immediately suicide just to requeue and find us again. In one game, when we weren’t even in the lobby, they just stood still looking for our names and stream sniped to keep griefing. They’re not trying to win or qualify. They just want to prevent us from doing it. 🟥 This clearly breaks: · Section 8.1.3 – Game Sabotage “Players shall not engage in game sabotage… or any activity harmful to the enjoyment of Fortnite by other users as intended by Epic.” · Section 8.2.1 – Competitive Integrity “Any form of unfair play is prohibited by these Rules.” “Intentionally Disconnecting from Fortnite after you or a member of your team takes damage…” · Section 8.2.2 – Collusion “Feeding: Intentionally allowing oneself to be eliminated by an opposing player.” While this isn't traditional “feeding,” they are intentionally dying after targeting us, only to requeue and do it again. That’s sabotage, and it clearly violates the spirit and intent of these rules. ----------------------- 2. Systematic teaming with friends from their country 🇵🇱 There is no competitive integrity when 100% of the games are played the same way, by the same two teams trading surge, never finishing kills, and never actually fighting. This isn’t a real contest. It’s always the same surge base, the same damage pattern, and zero intent to eliminate. In one clip below, they even knock each other and have a launch pad right below them, but don’t use it. Because they’re friends. Let’s be clear: Kombek is in our heat, and he’s openly friends with Pixx Demus. If they’re teaming in customs, how can we trust that when we fight their friends during Heat 1, Kombek won’t rotate to back them up? It’s happened before. And it keeps happening. 🟥 This clearly violates: · Section 8.2.2 – Collusion “Teaming: Players working together during the Match while on opposing teams.” “Planned Movement: Agreement between two or more opposing players to land at specific locations and move through the map in a planned way before the Match begins.” “Communication: Sending or receiving signals (both verbal and non-verbal) to communicate with opposing players.” This isn’t strategy. It’s blatant system abuse, and everyone sees it. ----------------------- 3. Coaching and pre-planned griefing across heats They’re coaching teams (friends) in other heats to grief the players contesting their spot, so that if those friends qualify, they’ll get a completely free drop in Grands. They’re manipulating the tournament before it even begins, and the worst part is that they post about it publicly, proudly. And maybe this would make some sense if later that teams planned to contest Demus, Pixx or Darm in Grands, but they don’t. They’ve already agreed beforehand not to land on them. They’re just helping eliminate threats now so they can keep the drop uncontested later. This is about: - Coaching others to do their dirty work - Cross-heat griefing coordination - Securing free drops before even qualifying 🟥 This breaks: · Section 8.2.1 – Competitive Integrity “Each player is expected to play within the spirit of Fortnite and these Rules at all times during any Event Match.” “Utilizing outside assistance regarding the location of other players… or any other information not otherwise known to the player by the information on his or her own screen.” · Section 8.2.2 – Collusion “Any agreement to intentionally influence the outcome of any match or Event.” This isn’t a one-off case. It’s deliberate, long-term structural manipulation of drops, heats and the entire competitive system. ----------------------- Where’s the fairness when you load into a game? What chance do new or unknown players have if they don’t have the right connections? Do you really want a competitive scene where abusing the system, not skill, is what works best? And no, this isn’t “contest” These are 10 out of 10 games between the same two teams, building the same surge bases, trading damage, and making each other’s games infinitely easier. There’s no midgame. No map strategy. No real rotations. Just teaming and abuse. This is not the Fortnite we fell in love with Remove surge. Or at least: - Penalize repeated surge trades between the same teams - Prevent infinite surge exchanges between friends - Punish ultra-late rotations after fake trades Do something. Anything. Because this isn’t what competitive Fortnite was meant to be. We just want to compete. Show what Spain can do. Play fair. Real 3v3s. No alliances, no coaching favors, no manipulation. We appreciate any support on this post. We’re doing it for our region. We deserve the same right to compete as anyone else. We can’t stay silent when: - We’re being teamed on - We’re griefed in 5 straight games - Others are being coached to cone us We’ve already reported everything. And we encourage anyone who’s gone through something similar to report it too. We have clips, proof, screenshots, and we’re ready to provide whatever is needed for a serious investigation. All we’re asking for is a fair chance to compete. There needs to be a line. A precedent. If you care even a little about this game, it’s time to act. And let’s not pretend this is new. Every season it's the same. Hogman Loomin Leven Tocata Evanosaurus “Unrawrl Engine 5.8” Rex Fortnite_ES

khaorz

82,653 просмотров • 1 год назад