正在加载视频...

视频加载失败

Vibe coding a web-based MMORPG w/ Three.js updates: 🎮 Player controls & movement ⛰️ Basic terrain formation 🌓 Day & night cycle w/ sun & moon 📝 Lighting editor to debug in-game Cursor & Anthropic claude-3.7-sonnet-thinking did a good job with the moon shader!

13,185 次观看 • 1 年前 •via X (Twitter)

11 条评论

Invalid.eth 的头像
Invalid.eth1 年前

@threejs @cursor_ai @AnthropicAI Been trying to watch a lot of vibe coding content, but this is the first time i admit, id pay ($40-80) for videos detailing someone's process. Please build your own community and share your journey🙏🏻

OPEN 的头像
OPEN1 年前

Introducing OPEN, the first genre-defining AAA metaverse gaming experience with top-tier IP powered by web3 technology. Coming to @thereadyverse. #opensoon

Matthew 的头像
Matthew1 年前

@threejs @cursor_ai @AnthropicAI How did you do the terrain and physics I failed for about 3 days with cannon and ammo till i hacked it

Majid Manzarpour 的头像
Majid Manzarpour1 年前

@threejs @cursor_ai @AnthropicAI The terrain is just a deformed plane, it's divided into a grid and then formed with height calculations and smoothing kernels. I'm using simplex noise for the mountain parts too.

rozar.btc 的头像
rozar.btc1 年前

@threejs @cursor_ai @AnthropicAI looks sick! any plans for in-game items/economy?

Majid Manzarpour 的头像
Majid Manzarpour1 年前

@threejs @cursor_ai @AnthropicAI Definitely!

Florian Kalisch 的头像
Florian Kalisch1 年前

@threejs @cursor_ai @AnthropicAI That has developed nicely. It looks great. Is that still 100% vibe coding? The new update looks very time consuming. You had inspired me to give it a try as well, but I'm still far from such a nice look.

Majid Manzarpour 的头像
Majid Manzarpour1 年前

@threejs @cursor_ai @AnthropicAI Yep, didn't take much time! I've spent a lot of time researching prompting over the past few years though

marc-antoine 的头像
marc-antoine1 年前

@threejs @cursor_ai @AnthropicAI Can you add 2 more sun and make it a trisolaris simulation

Max Hertan 的头像
Max Hertan1 年前

@threejs @cursor_ai @AnthropicAI Sent DM!

marco 🕸🐸 的头像
marco 🕸🐸1 年前

@threejs @cursor_ai @AnthropicAI Really cool !!

相关视频

THIS GUY VIBE CODED A FULL CAPYBARA FOOD DELIVERY GAME IN 2 WEEKS WITH CLAUDE CODE you play as a capybara delivering food on a bike. orders stack on the back, you have a phone with apps in-game and the whole delivery system is realistic 2 weeks, zero game dev experience, and ENTIRELY AI generated the full stack: > claude code for all the code > three.js for the 3D engine > suno for original music > elevenlabs for sound effects and voice > GPT images-2 and grok for textures and illustrations > tripo3d for generating all the 3D assets the cinematics are all in-game too. he asked claude to build a cinematic editor with timeline controls, camera animation, and transitions. then he just placed the cameras himself his workflow was more planning than coding (obviously): > come up with the core mechanic > plan every feature using claude /plan mode > generate assets with AI tools > spend most of his time on the final polish, prop placement, and making the design feel right he said the human part is what most vibe coded games are missing. AI can generate everything but having taste for what looks good and what feels right is still on you the game is playable right now in the browser this is what vibe coding is actually capable of in the game dev space right now a year ago this would have taken a small team of developers, a sound designer, and an artist working together for months now one person with no experience can ship a polished playable game with story, music, and mechanics in 14 days the tools keep getting better and the barrier to making real games keeps getting lower

Om Patel

240,916 次观看 • 2 个月前

Claude Code is now scary good at full-stack! I asked it to build a real-time weather intelligence dashboard with an interactive 3D globe and a forecasting layer that predicts weather 3 days ahead. It came back with a spinning globe that has a day/night cycle using NASA satellite imagery, city lights on the dark side, weather icons that switch between sun and moon based on local time, and a time travel slider that scrubs through 10 days of data. Claude Code built the whole thing in a single session, including the backend, database, data pipeline, and frontend. For the database, I needed something fast for time-series workloads since the app ingests hourly weather readings across many cities and serves time-range queries on every slider interaction. I used Tiger Cloud by Tiger Data - Creators of TimescaleDB, which gives you managed TimescaleDB on the Postgres you already know. Claude Code connected to it through the Tiger CLI MCP server and set up the entire backend directly: - Provisioned the database service - Created hypertables for time-partitioned weather storage - Set up continuous aggregates for pre-computed rollups - Built the data ingestion pipeline and the full NextJS + ThreeJS frontend The time travel slider queries thousands of rows on every position change. On a regular Postgres table, this would require manual partitioning and index tuning to stay fast as data grows. TimescaleDB partitions the data by timestamp automatically, so each query only hits the relevant time chunk. Continuous aggregates serve the trend charts and forecast layer from pre-computed rollups instead of rescanning raw data on every request. The video below shows the final build in action, and I worked with the Tiger Data team to put this together. Tiger CLI is open-source (Apache 2.0) and works with Claude Code, Cursor, Codex, Gemini CLI, and VS Code. To try this yourself: → Sign up for Tiger Cloud (I have shared the link in the replies). It gives you $1,000 free credits (no card needed) → Install Tiger CLI: curl -fsSL https(:)//cli(.)tigerdata(.)com | sh → Run tiger mcp install claude-code → Give Claude Code a prompt and let it build Find the sign-up link in the replies.

Avi Chawla

14,579 次观看 • 1 个月前

Hey True Earthers... If you get tired of globers bitching about a model, or sunrise angles, or star trails, or sunlight, or eclipses, anyone can ALWAYS reference THIS MODEL The reason it is called "Shane's Mode;" is strictly so YOU can use it, and I can take all the criticism, insults, ridicule, jokes, attacks, etc. The general idea is that the community gets the considerable benefit of presenting an accurate model and using it to explain several normal phenomena at once. Then, only I get the drawbacks of all that will surely come from it, and everyone else will benefit. I planned it this way, because I largely don't care about what any of the globers piling the hate over here so we can press forward. Or.. you know, f*ck me for saying the word model, and for bendy light or for whatever. If that's the case, no hard feelings. One last thing, the smaller dome in the model simply represents the limit of an observers view, a spherical limit with a radius of 3959. The math that supports that is here... and here. The descriptions are entirely reworked, mostly spelling error free, and entirely plausible. So feel free to bring it up in debates, forums, streams, podcasts, or whatever you like. The model adequately emulates and explains all of these observations: Sunrise, Sunset, Moonrise, Moonset, Moon Phases, Moon's apparent rotation, Sun's position on Equinox, Seasons, some aspects of Solar and Lunar Eclipses, Star trails, 24 hours Day/Night at the North-pole and Antarctica, Celestial Poles, Why people south of the equator can see the same Stars rotate clockwise around a singe celestial pole at the same time at different continents [Southern Cross Observations] Cheers everyone! The FULL Description is below, and it is LONG. Sorry. The Model This model does not assume a physical Sun nor Moon which will show a collective convergence for every observer on Earth. It only matches their apparent positions as observed across the plane. The Bislin model acknowledges this and moves all celestial bodies to a nearly infinite distance away. This does nothing more than create a triangle large enough that you can mathematically abstract your way into the inverse of everything you experience. The truth is there is a limit to one's visual space. And this limit is necessarily geometrically spherical. Because one never observes objects in anything but their 'apparent location' within one's personal celestial sphere, there is no need to explain a tiny ball of heat mysteriously powering itself along at 3100 miles above the plane. This is not reality. We feel we only have to model the exact apparent position for each observer. We do not have to provide an explanation for what you think should be required. This model relays the apparent size and positions of Sun, Moon and star constellations. It depicts their paths as well as the day-night terminator. Simply by observing reality and plotting that data on a planar map we demonstrate that the Sun, Moon and stars can move beyond the limit of one's vision and become unresolvable by the naked eye. We show how this can be conflated with the assertion that objects ACTUALLY drop down below the horizon when, in reality, they are only apparently dipping below the horizon when exceed limit of your vision. It is elegantly simple and easy to understand without the bullshit. Sun/Moon tracks: In 24 hours, the fixed stars rotate about 1 degree more than 360 degrees so that, in 365.25 days, the star constellations return to the same place in the sky. This is seen by incrementally advancing DayOfYear (click the field and use Arrow Up or Down). The Dome grid will advance each day by about 1 degree. Advance the time in 24 hours steps and the Sun noticeably moves between the Solstice lines. The Sun will also trace a figure 8. This is caused by the Sun's Ecliptic plane at 23.44 degrees to the orbital plane. The paths of the Sun and Moon are visible against the fixed star background (Dome Grid) by checking the options Sun track and Moon track. For a description of the tracks, click the Eclipses button. They correspond to observable reality. The tracks are derived from the solar and lunar cycles and are absolutely not exclusive to either model. It would be extremely dishonest to claim anything else. Sorry, Walter. Retrograde Motion of the Moon's track: The Sun's path stays fixed on the Dome Grid. But, the Moon's path slowly rotates retrograde against the Dome Grid and rotates one full rotation in 6,798 days. This is due to the oscillation and intersection of the Moon's orbit caused by the distant Sun. Currently, the Moon Ecliptic is such that the path of the Moon extends the path of the Sun, North/South, by about five degrees. Approximately 3,400 days later, the path of the Moon moves inside the path of the Sun by about 5 degrees. This observation is simply translated to the planar model. Eclipses: The intersection points of the Sun and Moon's paths are called Knots. Two Knots are marked by a green dot. If the Sun and Moon are on two opposing Knots, a Lunar Eclipse occurs. The Sun and Moon on the same Knot will result in a Solar Eclipse (play Demo Eclipses from Step 6 on). This Flat Earth model can predict Solar and Lunar Eclipses. It can also absolutely predict the optical effect conflated with the Moon's alleged shadow on Earth during a Solar Eclipses or vice versa. It uses a ratio of the cycle that is based on the radius of a shadow, as postulated by Phillippe de La Hire, in the 1700s. It was first calculated for a Lunar Eclipse. But, the ratio applies to all future eclipses which belong to an appropriate series. This ratio is then applied to the predicted path to dynamically widen or shorten the path in order to accommodate the penumbral and umbral radial intersection as a visible sphere on the plane. We then apply this integer as a scalar to correctly approximate the size of the optical effects conflated with shadows. All of the maps onto which the eclipse can be projected use the same globular coordinate system, unfortunately. Now, it can be shown that heliocentrism cannot predict eclipses at all. They can only interpret the cycle data in the same way the ancients did and apply more refined mathematics. Moon Phases and Orientation: The model shows the Moon phases and the orientation of the Moon with respect to the Observer's horizon. The apparent rotation of the Moon during the day is due to the fact that the camera's up vector remains perpendicular to the surface of Earth while following the path of the Moon. This perfectly matches reality. Equinox: This model produces the correct apparent Sun positions during an Equinox. The Sun rises due East at 6:00 AM and sets due West at 6:00 PM. Poles: This model produces a 24 hour day and night on the North Pole and in Antarctica. Heliocentric Model: Simple observations mathematically translated to this planar projection perfectly map the paths of the Sun, Moon and stars (star trails) as they appear to the Observer inside their personal celestial sphere. As with all other celestial observations, the Equinox, the Solstice Knots and the Day-Night terminator can be derived from basic observation and data applied to the planar projection. No need for baseless assumption. The Heliocentric model utterly fails here. Newton's laws can be reduced to exclude mass and still manage to describe the same periodicity and, thusly, the same relationship. No need for an exclusivity claim here at all, is there, Walter? Shapes on the Dome: The shape of Sun, Moon and star constellations appear on the personal celestial sphere exactly as they do in reality, and when projected onto the globe. Again, because we invoke the same radius to describe the spherical limit of our celestial view, the very same observations become easily explainable when using all of the normal conventions, with no need to invent branches of physics and invert reality. All features of this model are derived only from observations of the sky. Observations of the sky have always been kinematically equivalent - equally applicable to geocentric and heliocentric model. This was rather the point of the invention of Special and General Relativity (nonsense). Problems with the Shane's Flat Earth Model Distances: Many people misunderstand distances on map projections. On the AE map, distances measured in an exactly North-South direction are correct. Other measurements are also proportionately correct. Data translation between projections is tied to the coordinates we use. The longitude and latitude we use in any of the appropriate 200 map projections will ensure the distances between those points remain accounted for, at scale. Please learn how map scaling works if this seems inadequate to you. Only an absolute moron would expect visual distance to be equal in an equal area, or equal distance, cartographic transformation. Right, Walter? Personal Celestial Sphere: The Sun and Moon trace specific paths across the celestial sphere. The paths of the celestial bodies are directly mapped from observation to the planar projection. They also follow the cycle of the Heavens, with no need for gravity, Newton, nor the very lackluster performance of gravity based predictions of systems with 2 or more bodies. It was jaw dropping to see that poor Walter actually wrote that gravity caused this. I assume it was because he knew he would never have to answer any challenges. Show me the math which uses the gravitation from all of the forces Walter listed and I will immediately remove this section. Moon Phases and Field Rotation: Moon phase and apparent orientation, as shown, perfectly represent what every observer on Earth sees, correct to their location. The 15 year solar cycle and the 18 (10/11) month lunar cycle have been understood for so long that people eventually forgot and are now incorrectly perceive their paths. Only in modernity do the vast majority of people wander about under their own personal clock without the ability to read it. How sad. The Day/Night Terminator: The shape that matches reality is a bit peculiar and it changes over the course of a year. The shape not only depends on the location of the Sun but its height and speed as well. Again, we know the Sun circles the plane at a 23.4 degree tilt. And this perfectly defines the terminator line. There is absolutely no reason to invoke bendy light in order to explain any of these observations. The model simply matches what we see. It represents reality. Missing The Third Dimension: We need to correct the inherent misunderstanding in the assumption of the physicality of any 'dome'. Modeled here is a personal celestial sphere. It uses a radius. It just so happens that Shane has been arguing this concept and this radius since the day he showed Walter Bislan's model as evidence, amid the jeers of the uneducated masses. As it turns out, the personal celestial sphere is a visual limit imposed on one's spherical view of the heavens. It most simply describes the particular visible slice of the heavens. And it moves that amount with you where ever you go. This is such an elegant, beautiful explanation to what had been perplexing the flat Earth community for years: how the stars work. The personal celestial sphere, once properly understood, is a perfect explanation for everything we see in the sky. It explains the curved nature of the arcs of summer and winter, the behaviors of the Sun and Moon, as well as the apparent non movement of the static stars in relation to each other. Every single stellar observation is explained as well as, if not better than, any Heliocentric explanation. Any person who incorrectly assumes a visual distance scale also assumes things to be visually identical in size and demonstrates a massive misunderstanding of proper distance scaling inherent in all map projections - particularly in the AE map. It's as if everyone has forgotten that the AE map is equal to the Globe map, which is also equal to 199 other map projections. The choice of projection does not matter. They are all the same. They all represent the same distances. We can make predictions based on cycles as well as the next guy. So, we wont need help there. As we keep saying, every observation in the sky is equal between geocentric and heliocentric perspectives. People seem to be INTENTIONALLY misunderstanding that, at this point. Light-Bending: absolutely not required in any way shape nor form. Observable reality matches the model in every way; I cannot imagine a better fit. To now try to invent a need for bendy light would only publicly highlight the ineptitude of a lower tier glober - and their inability to learn and adapt, a vital skill in these times. Our model perfectly represents azimuth and elevation of every celestial object in its apparent position. This is all that we ever see. There is no need to explain what has never been observed. The visualization of the South Pole in action is actually what brought Shane to the ultimate understanding of the celestial wheels. So, thank you again, Walter! Light Bending Over Night-Shadow: to match the 24 hour Daylight in Antarctica data from the light forms a shape congruent to a coffee cup caustic effect. Shadows Of Eclipses: although this model can predict the date of Eclipses, it was argued that it can be used for nothing else. Please check the provided links to review the absurdity of those claims. Conclusion Some observations, like the positions of the Sun, Moon and Star Constellations as well as Sun/Moon-rise/set can be explained by a Flat Earth Model - if we allow ourselves to adhere to the mathematical principle of equivalence. What a concession. Some final thoughts: 1) Distances on the AE Map are 100% 1:1 equivalent when you comprehend how to accordingly use the scale provided with the ruler which represents longitude. 2) LEARN ABOUT MAPS. Hopefully, the covariant scaling and lossless unlimited translations between the projections will teach you this valuable lesson. Equinox, Solstice, Azimuth, Elevation This model draws a perfectly circular orbit of the Earth around the Sun and a perfectly circular orbit of the Moon around the globe Earth. This is because the planar Earth has no moronic need for elipicity because they didn't back themselves into a logical corner by making shit up. This model chooses to match: Spring Equinox at 12:00 UT, March 20, 2017 Solar Eclipse at 18:00 UTC, August 21, 2017 Azimuth and Elevation of the Sun and Moon are also slightly inaccurate (according to the assumed Heliocentric requirement) due to the use of circular instead of elliptical orbits. This affects also Moon phase. Computing Day-Night Terminator The Day-Night terminator is derived from to match reality as follows: 1. A circle perpendicular to the Earth-Sun axis in the Sun coordinate system is computed depending on the Sun's position at a point in time relative to the intersection knot of the Equatorial plane of the Earth and the ecliptic plane of the Sun. This is entirely possible in both models. 2. This circle is then transformed to the globe Earth coordinate system. There is no way around using this coordinate system. If Walter Bislan comes asking for his source code, tell him thank again, from shane. Any questions can be sent to [email protected]

Shane St Pierre

90,809 次观看 • 2 年前

Elon Musk just took Anthropic's biggest customer hostage three days before their IPO. He paid $60 billion for it without spending a dollar of cash. But the company he bought is actively losing the race he claims to be winning: The company is Cursor, the AI coding tool used by most of Silicon Valley and a huge chunk of Fortune 500 engineering teams. Its best feature is called Composer, and Composer became the most-loved AI coding product on earth for one specific reason: It runs on Anthropic's Claude. The phrase "vibe coding" was literally coined by a researcher playing with Cursor's Composer running on Claude Sonnet in early 2025. Anthropic's enterprise revenue exploded in 2025 partly because every engineer using Cursor was effectively a paying Anthropic customer underneath. Cursor became one of the largest external pipelines of Claude usage anywhere on the internet. And last week, Anthropic confidentially filed paperwork to go public. Three days after SpaceX completed its own IPO on Friday, Elon Musk exercised an option he had quietly signed in April and bought Cursor for $60 billion. The deal was announced Tuesday morning in an 8-K filing. By the time most people read the headline, the pipeline feeding Anthropic's biggest enterprise channel was already legally owned by its biggest RIVAL, days before that rival walks onto the public markets and has to explain its growth story to Wall Street. Now look at how he paid for it: Not one dollar of cash changed hands. The entire $60 billion was paid in SpaceX stock. Stock that was minted out of thin air on Friday when the company went public at $135 a share. By Tuesday, that same stock was trading at $211. So Musk used four days of public-market hype to mint $60 billion of fresh equity and immediately spent it on an acquisition that had been pre-arranged before anyone in the IPO even saw the prospectus. SpaceX investors who bought shares in the last four days got diluted by 3.4% before they understood what they owned. The IPO was literally the printing press for the acquisition. Now look at what he ACTUALLY bought: Cursor's market share among enterprise customers has been collapsing. According to spending data from Ramp, it fell from 41% in June 2025 to 26% in May 2026, bleeding ground every month to GitHub Copilot and Amazon Q. The smart money knew. Andreessen Horowitz, Thrive, and Nvidia were about to lead a round at a $50 billion valuation, which they already considered aggressive. Elon paid 20% more than that for a company actively LOSING the race. He paid premium for declining momentum. And he did this because his own AI division was in trouble. xAI has been struggling quite a bit so SpaceX needed an AI story that could survive a public-market quarterly earnings call. The fastest way to get one was to buy a brand engineers already trusted before that brand's market share slipped any further. So follow the whole chain: SpaceX went public to mint the currency. Elon used that currency to buy a fading market leader at a premium. And the seller of choice happened to be Anthropic's biggest enterprise pipeline with the timing landing in the exact window between Anthropic filing its prospectus and pricing its IPO. This was literally a hit job on Anthropic's IPO. Anthropic's next move is the one to watch. If they cannot show Wall Street that Cursor's revenue can be replaced fast, the most hyped AI IPO of the year just walked onto the public markets with a huge problem.

Ricardo

64,021 次观看 • 1 个月前

I see the player you mean. PLAYERNAME? Yes. Take care. It has reached a higher level now. It can read our thoughts. That doesn't matter. It thinks we are part of the game. I like this player. It played well. It did not give up. It is reading our thoughts as though they were words on a screen. That is how it chooses to imagine many things, when it is deep in the dream of a game. Words make a wonderful interface. Very flexible. And less terrifying than staring at the reality behind the screen. They used to hear voices. Before players could read. Back in the days when those who did not play called the players witches, and warlocks. And players dreamed they flew through the air, on sticks powered by demons. What did this player dream? This player dreamed of sunlight and trees. Of fire and water. It dreamed it created. And it dreamed it destroyed. It dreamed it hunted, and was hunted. It dreamed of shelter. Hah, the original interface. A million years old, and it still works. But what true structure did this player create, in the reality behind the screen? It worked, with a million others, to sculpt a true world in a fold of the [scrambled], and created a [scrambled] for [scrambled], in the [scrambled]. It cannot read that thought. No. It has not yet achieved the highest level. That, it must achieve in the long dream of life, not the short dream of a game. Does it know that we love it? That the universe is kind? Sometimes, through the noise of its thoughts, it hears the universe, yes. But there are times it is sad, in the long dream. It creates worlds that have no summer, and it shivers under a black sun, and it takes its sad creation for reality. To cure it of sorrow would destroy it. The sorrow is part of its own private task. We cannot interfere. Sometimes when they are deep in dreams, I want to tell them, they are building true worlds in reality. Sometimes I want to tell them of their importance to the universe. Sometimes, when they have not made a true connection in a while, I want to help them to speak the word they fear. It reads our thoughts. Sometimes I do not care. Sometimes I wish to tell them, this world you take for truth is merely [scrambled] and [scrambled], I wish to tell them that they are [scrambled] in the [scrambled]. They see so little of reality, in their long dream. And yet they play the game. But it would be so easy to tell them... Too strong for this dream. To tell them how to live is to prevent them living. I will not tell the player how to live. The player is growing restless. I will tell the player a story. But not the truth. No. A story that contains the truth safely, in a cage of words. Not the naked truth that can burn over any distance. Give it a body, again. Yes. Player... Use its name. PLAYERNAME. Player of games. Good. Take a breath, now. Take another. Feel air in your lungs. Let your limbs return. Yes, move your fingers. Have a body again, under gravity, in air. Respawn in the long dream. There you are. Your body touching the universe again at every point, as though you were separate things. As though we were separate things. Who are we? Once we were called the spirit of the mountain. Father sun, mother moon. Ancestral spirits, animal spirits. Jinn. Ghosts. The green man. Then gods, demons. Angels. Poltergeists. Aliens, extraterrestrials. Leptons, quarks. The words change. We do not change. We are the universe. We are everything you think isn't you. You are looking at us now, through your skin and your eyes. And why does the universe touch your skin, and throw light on you? To see you, player. To know you. And to be known. I shall tell you a story. Once upon a time, there was a player. The player was you, PLAYERNAME. Sometimes it thought itself human, on the thin crust of a spinning globe of molten rock. The ball of molten rock circled a ball of blazing gas that was three hundred and thirty thousand times more massive than it. They were so far apart that light took eight minutes to cross the gap. The light was information from a star, and it could burn your skin from a hundred and fifty million kilometres away. Sometimes the player dreamed it was a miner, on the surface of a world that was flat, and infinite. The sun was a square of white. The days were short; there was much to do; and death was a temporary inconvenience. Sometimes the player dreamed it was lost in a story. Sometimes the player dreamed it was other things, in other places. Sometimes these dreams were disturbing. Sometimes very beautiful indeed. Sometimes the player woke from one dream into another, then woke from that into a third. Sometimes the player dreamed it watched words on a screen. Let's go back. The atoms of the player were scattered in the grass, in the rivers, in the air, in the ground. A woman gathered the atoms; she drank and ate and inhaled; and the woman assembled the player, in her body. And the player awoke, from the warm, dark world of its mother's body, into the long dream. And the player was a new story, never told before, written in letters of DNA. And the player was a new program, never run before, generated by a sourcecode a billion years old. And the player was a new human, never alive before, made from nothing but milk and love. You are the player. The story. The program. The human. Made from nothing but milk and love. Let's go further back. The seven billion billion billion atoms of the player's body were created, long before this game, in the heart of a star. So the player, too, is information from a star. And the player moves through a story, which is a forest of information planted by a man called Julian, on a flat, infinite world created by a man called Markus, that exists inside a small, private world created by the player, who inhabits a universe created by... Shush. Sometimes the player created a small, private world that was soft and warm and simple. Sometimes hard, and cold, and complicated. Sometimes it built a model of the universe in its head; flecks of energy, moving through vast empty spaces. Sometimes it called those flecks "electrons" and "protons". Sometimes it called them "planets" and "stars". Sometimes it believed it was in a universe that was made of energy that was made of offs and ons; zeros and ones; lines of code. Sometimes it believed it was playing a game. Sometimes it believed it was reading words on a screen. You are the player, reading words... Shush... Sometimes the player read lines of code on a screen. Decoded them into words; decoded words into meaning; decoded meaning into feelings, emotions, theories, ideas, and the player started to breathe faster and deeper and realised it was alive, it was alive, those thousand deaths had not been real, the player was alive You. You. You are alive. and sometimes the player believed the universe had spoken to it through the sunlight that came through the shuffling leaves of the summer trees and sometimes the player believed the universe had spoken to it through the light that fell from the crisp night sky of winter, where a fleck of light in the corner of the player's eye might be a star a million times as massive as the sun, boiling its planets to plasma in order to be visible for a moment to the player, walking home at the far side of the universe, suddenly smelling food, almost at the familiar door, about to dream again and sometimes the player believed the universe had spoken to it through the zeros and ones, through the electricity of the world, through the scrolling words on a screen at the end of a dream and the universe said I love you and the universe said you have played the game well and the universe said everything you need is within you and the universe said you are stronger than you know and the universe said you are the daylight and the universe said you are the night and the universe said the darkness you fight is within you and the universe said the light you seek is within you and the universe said you are not alone and the universe said you are not separate from every other thing and the universe said you are the universe tasting itself, talking to itself, reading its own code and the universe said I love you because you are love. And the game was over and the player woke up from the dream. And the player began a new dream. And the player dreamed again, dreamed better. And the player was the universe. And the player was love. You are the player. Wake up.

KikiLove1111

18,309 次观看 • 3 年前

Vibe Coding a AAA game with threejs Day 10: Deep dive into world authoring What started as a "i need terrain to build a racing game" slowly evolved to an open world Take a last look at the buildings, because they are getting kicked out next for some really good ones (i don't know how yet, but i'm confident gpt will tell me, but i feel like blender will be involved, ughhh) Anyways, fully reworked the road system, it is now a graph and junctions, bridges, elevations etc. are first class. Previous demos were filled with me carefully placing the race tracks, deleting them, placing them again, and again, until they were okay to show for a demo. Not so fun behind the camera! It's now basically using a very similar system to cities skylines 2, which has really nailed the perfect UX to build road systems. It's also much more flexible now and i believe the world editor can be used for much more than racing games: Rail networks (train game?) or maybe a 3rd person open world game? or actually another cities skylines? who knows, feels like i got a moat on the web now We'll see, after yesterday i've received lots of requests to open source it Which i may actually do at any time if i feel like it, but not for now. There's so many interesting problems with world modeling, i feel like i finally found a rabbit hole worth diving into for a long time! Might have to delay the human designer app until the point where i need humans in the city, we'll see, it'll all eventually come together - it always does Anyways, not gatekeeping, if you have ANY questions on how i solve things, feel free to ask! Also i will open source the procedural buildings soon, i really don't need them anymore

robot 2.0

43,872 次观看 • 1 个月前

Promised to ship before the movie so... 📅 53 days 🤖 731 vibe coded commits ⚡️ Powered by Three.js 🚀 Inspired by a space plumber 🙋‍♂️ AMA, no secrets, no shame High level, grouped list of what's in this game: Galaxy DNA - Lumas - Star Bits - Spin attack with air boost + ground-cancel - Galaxy gravity - Octoombas - Gateway Galaxy music track Vibe Coding Process - Claude Code (Opus) for ~95% of all code - CLAUDE.md project instructions file (163 lines of rules + constraints) - 87 implementation plans written before coding - 36 AI code reviews (ECS, architecture, performance) - 11 retrospectives after major features - 60 extracted skills (reusable knowledge from debugging sessions) - Constraints doc that grows every time something breaks (115 lines) - /lets-build workflow: discovery → plan → review → implement → verify - Every feature: plan first, review the plan, then build in atomic commits - Custom level construction CLI (AI-assisted placement) - this evolved over 53 days Architecture - Custom ECS engine (Structure-of-Arrays, zero-alloc hot paths) - Benchmarks faster than bitECS on packed iteration - 117 ECS systems orchestrated in explicit update order - Data-oriented Process system (sequential/parallel composition) - 30+ process types: UI animations, camera arcs, sfx Rendering - Three.js + Pixi.js sharing one WebGL2 context - Three renders 3D, Pixi renders UI — no extra canvases - Half-res bloom, color grading, occlusion silhouettes - Fresnel rim lighting + hemisphere ambient for Galaxy-style polish Physics - Rapier3D WASM physics (SIMD build) - Kinematic character controllers for player + all enemies Gravity - Galaxy-style gravity fields (walk around surfaces) - 4 gravity field types - Priority-based gravity resolution with distance tiebreakers - Convex hull letter platforms with per-face gravity - Spring-damped gravity transitions Shadows - Multi-pass gravity-aware shadow system - Per-instance shadow filtering via vertex shader attributes - InstancedMesh candidates promoted across gravity fields - Dynamic frustum sized from camera FOV each frame Camera - camera system with 12 critically damped springs - Follow-gravity mode (trailing orbit in tangent plane) - Fixed-up mode (screen stays level on letter platforms) - Top-down mode (Galaxy overhead cam, roll-free quaternion) - Camera collision via 4-direction spherecast repulsion - Override blend system for boss fights + pipe travel - Catmull-Rom spline intro flythrough with per-waypoint duration Space - Procedural space nebula (simplex noise shader, 3 octaves) - 1,800 seeded stars with per-star brightness + color variety - Galaxy-authentic palette across all screens Enemies - 5 enemy types with full AI state machines - Goomba, Koopa, Spiny, Bob-omb, Octoomba - 3D distance → FOV cone → LOS raycast detection pipeline - Editor-placed OBB avoidance zones with deflection hysteresis - Recoil, stun, shell, fuse, and ranged attack behaviors Boss Fight - Bowser Jr. boss fight - Multi-phase combat with Bob-omb spawning - Controlled intro/outro sequence Mario - Galaxy-style spin attack - Rainbow diamond particle burst (InstancedMesh, 64 pool) - Hit-stop with global time scale freeze + camera shake - Air boost, ground-cancel, shell kick at extended range - Invulnerability frames during active spin Yoshi - mount/ride system with shield HP - +3 extra HP ring on mount, damage depletes shield first - Overflow damage carries to Mario - Forced dismount on shield break with poof effect Objects - Coin system with InstancedMesh rendering (256 max) - Per-instance opacity via shader patching - Pop → float → shrink → fade collection animation - Swap-and-pop O(1) entity removal - Star bit burst spawning with attraction system - Pipe warp travel with camera override blend - Parallel-transported screen-right vector during crossfade - Shadow field updates for traveling entities - trampoline - 3D assets from Hello Mario Framework (now archived) and game rips Audio - 17+ wired sound effects with spatial audio - Bob-omb fuse sound: per-entity lifecycle, looping playback tracking - Distance-based volume for poof and explosion effects UI - Odyssey-style ring HP meter with shield inner ring - Number roll + arc lerp stagger on health changes - Gold coin counter HUD - Loading screen with code-split fast first paint - Pretext layout flow in "legal" screen with retro Mario Controls - Mobile touch controls: virtual joystick + A/B buttons - Proportional analog stick with walk/run speed switching - Gamepad support: Xbox, PlayStation, Switch Pro - Dead zones, auto-reconnect, synthetic DOM key bridge Dev Tooling - experimental CLI level construction tool with undo history - 18 placement types with type-safe defaults - Atomic file writes, auto-backup (max 20), live reload - Dev server auto-save plugin for visual editor - Two-panel debug editor (Tweakpane) - Hierarchy + inspector with gravity field live editing - Translation/rotation gizmos with gravity-relative local space - Per-waypoint camera preview for intro spline tuning 731 commits. 53 days. 95%+ vibe coded.

Tommy Leung

184,445 次观看 • 3 个月前

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code 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. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 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 Kumarfor 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

85,668 次观看 • 2 个月前

ICARUS INTERNATIONAL CONSULTING GROUP THE MANUFACTURED DELAY Our unprecedented analysis reveals what headlines miss: how logistics, capability architecture, and environmental constraints shape outcomes long before decisions are announced. In early 2026, the world watches the Persian Gulf and debates timing, politics, and personalities. Commentators ask when the strike against Iran will happen and why it has not yet begun. Some call it hesitation. Others blame temperament or political caution. That framing misses the point. The delay has nothing to do with POTUS Trump’s mood or indecision. It is about whether the United States is prepared not just to strike Iran, but to sustain pressure long enough to break a regime, not merely signal deterrence. What the public sees looks formidable: advanced aircraft forward deployed, stealth fighters shaping the air picture, heavy strike assets positioned across the region. On paper, it resembles dominance. In reality, it is a posture built for the opening move, not the endgame. Wars against states are not decided by the first strike. They are decided by what still functions after the first retaliation. Land-based airpower, regardless of sophistication, is chained to fixed infrastructure. Runways do not move. Against a capable adversary, they are mapped, targeted, and neutralized early. Once runways are cratered, sortie generation collapses, and with it the ability to sustain tempo. Stealth fighter jets platforms such as the F-35 solve a different problem. They penetrate, observe, and dismantle critical nodes with precision. But they are not designed to deliver sustained volume or to support prolonged deep operations on their own. Precision opens access; it does not maintain pressure. This is why the delay exists. A premature strike would shock, but it would also risk stalling into attrition, cost imbalance, or forced pause once infrastructure is degraded and magazines thin. Regime change does not occur in a single night. It requires endurance. That endurance arrives with the USS George H. W. Bush (CVN-77) The Bush is not deployed for symbolism or redundancy. It is the logistical hinge of the entire campaign. As a mobile airfield, it brings its own runway, its own fuel, and its own regeneration cycle into the battlespace. It cannot be pre-targeted the way land bases can, and it does not pause when infrastructure ashore burns. More importantly, it enables depth. From its deck, fighters and support aircraft can launch repeatedly, refuel one another, and sustain long-range operations that push bombers and strike aircraft deeper into contested space. It keeps penetration corridors open after stealth has done its initial work. It allows heavy strike platforms to return, rearm, and go back again—day after day. This is the difference between a warning shot and a campaign. With a carrier-based sustainment hub in place, the mission expands from signaling to dismantlement. Targets are not struck once; they are revisited. Air defenses are not blinded briefly; they are exhausted. Internal security, logistics, and command structures are degraded faster than they can adapt. Our analysis not only highlights the decisive architecture of logistics and force design but also shows how environmental factors shape strategic timing on the ground. In February 2026, the Moon will transition from a full phase on February 1 to a new Moon around February 17, when lunar luminosity is effectively zero and nights are darkest, creating conditions that can favor operations requiring concealment and minimized visual detection. This environmental window — where the Moon’s light no longer illuminates the battlefield — aligns with the maturation of a logistics and sustainment network that enables sustained operations deep into contested airspace. Rather than acting under a bright, reflective full Moon, planners may exploit the dark of the waning and new Moon period as a temporal enabler for deep penetration sorties, aerial refueling sequences, and carrier-to-shoreside combat logistics, precisely because reduced lunar illumination lowers visual and infrared signatures that adversaries could exploit. The shift from bright lunar conditions to new Moon darkness around mid-February is thus not accidental; it synchronizes with the arrival of sustainment and strike capacity that turns a deterrent posture into one capable of regime-scale pressure. That is the hallmark of regime-change–scale operations. This is why the delay is manufactured. The system is being completed, not debated. The question is not whether force can be used, but whether it can be kept on long enough to matter. Once that answer is yes, the clock stops stretching. Until then, what looks like restraint is something else entirely. It is discipline. Icarus International Consulting Group

Icarus International Consulting Group LLC

144,298 次观看 • 5 个月前