{"version":3,"sources":["styles/BB4AlphaPreviewNotes.module.scss","containers/BB4AlphaPreviewNotes.tsx"],"names":["module","exports","BB4AlphaPreviewNotes","React","createElement","className","styles","container","src","alt","content"],"mappings":"mGACAA,EAAOC,QAAU,CAAC,UAAY,wCAAwC,QAAU,wC,kCCDhF,8CAoJeC,UAjJc,WAC3B,OACEC,IAAAC,cAAA,OAAKC,UAAWC,IAAOC,WACrBJ,IAAAC,cAAA,OAAKI,IAAI,2EAA2EC,IAAI,mBACxFN,IAAAC,cAAA,OAAKC,UAAWC,IAAOI,SACrBP,IAAAC,cAAA,UAAI,yBACJD,IAAAC,cAAA,SAAG,6CACHD,IAAAC,cAAA,UACED,IAAAC,cAAA,UAAI,iDAGJD,IAAAC,cAAA,UAAI,qCAIND,IAAAC,cAAA,WACED,IAAAC,cAAA,UAAI,kDAKND,IAAAC,cAAA,UACED,IAAAC,cAAA,UAAI,iBAGJD,IAAAC,cAAA,UAAI,qBAGJD,IAAAC,cAAA,UAAI,gBAGJD,IAAAC,cAAA,UAAI,gCAGJD,IAAAC,cAAA,UAAI,iCAIND,IAAAC,cAAA,UAAI,sBAGJD,IAAAC,cAAA,SAAG,sUAIHD,IAAAC,cAAA,SAAG,wsBAKHD,IAAAC,cAAA,UAAI,oCAGJD,IAAAC,cAAA,UACED,IAAAC,cAAA,UAAI,gBAGJD,IAAAC,cAAA,UAAI,UAGJD,IAAAC,cAAA,UAAI,mBAGJD,IAAAC,cAAA,UAAI,OAGJD,IAAAC,cAAA,UAAI,oBAGJD,IAAAC,cAAA,UAAI,4BAGJD,IAAAC,cAAA,UAAI,uBAGJD,IAAAC,cAAA,UAAI,6BAGJD,IAAAC,cAAA,UAAI,eAKND,IAAAC,cAAA,SAAG,yFAIHD,IAAAC,cAAA,SACED,IAAAC,cAAA,cAAQ,qBAA0B,sZAGpCD,IAAAC,cAAA,SACED,IAAAC,cAAA,cAAQ,UAAe,uZAEzBD,IAAAC,cAAA,SAAGD,IAAAC,cAAA,cAAQ,mBAAwB,0SAA0SD,IAAAC,cAAA,UAAI,+BAAsC,wGAAoGD,IAAAC,cAAA,UAAI,sBAAuB,iBAExfD,IAAAC,cAAA,SAAG,2DACuDD,IAAAC,cAAA,UAAI,OAAQ,yKAAqKD,IAAAC,cAAA,UAAI,eAAgB,kJAE/PD,IAAAC,cAAA,SAAG,0UAIHD,IAAAC,cAAA,SACED,IAAAC,cAAA,cAAQ,qBAA0B,8YAA8YD,IAAAC,cAAA,UAAI,8BAA+B,2KAGrdD,IAAAC,cAAA,SAAG,0QACsQD,IAAAC,cAAA,UAAI,oHAAqH,oPAElYD,IAAAC,cAAA,SAAG,wIACoID,IAAAC,cAAA,UAAI,sDAAuD,mOAElMD,IAAAC,cAAA,SACED,IAAAC,cAAA,cAAQ,qCAA0C,uFAAuFD,IAAAC,cAAA,UAAI,+CAAgD,+QAE/LD,IAAAC,cAAA,SACED,IAAAC,cAAA,cAAQ,uBAA4B,0ZAAuZD,IAAAC,cAAA,UAAI,kCAAmC,MAGpeD,IAAAC,cAAA,SACED,IAAAC,cAAA,cAAQ,6BAAkC,8MAE5CD,IAAAC,cAAA,SAAG,4jBAGHD,IAAAC,cAAA,SAAG,yVAIHD,IAAAC,cAAA,SAAG,wbAIHD,IAAAC,cAAA,SACAD,IAAAC,cAAA,cAAQ,gBAAqB","file":"static/js/37.9bdc45c1.chunk.js","sourcesContent":["// extracted by mini-css-extract-plugin\nmodule.exports = {\"container\":\"BB4AlphaPreviewNotes_container__2BsNo\",\"content\":\"BB4AlphaPreviewNotes_content__2HEpL\"};","import React from 'react'\nimport styles from '../styles/BB4AlphaPreviewNotes.module.scss'\n\nconst BB4AlphaPreviewNotes = () => {\n return (\n <div className={styles.container}>\n <img src=\"https://frontend-assets.buildbox.com/bb4-quick-start/bb4_quick_start.png\" alt=\"preview header\"/>\n <div className={styles.content}>\n <h1>BB4 Quick Start Guide</h1>\n <p>This document is split into two sections:</p>\n <ul>\n <li>\n Limitations, Warnings, and Important Notices:\n </li>\n <li>\n Features, focus, and what's next\n </li>\n </ul>\n <div>\n <h3>\n Limitations, Warnings, and Important Notices:\n </h3>\n\n </div>\n <ul>\n <li>\n No 2D Support\n </li>\n <li>\n No Mobile Exports\n </li>\n <li>\n No Mac Build\n </li>\n <li>\n BB3 Imported Project Warning\n </li>\n <li>\n Time-Sensitive Access Period\n </li>\n </ul>\n <h3>\n Detailed Comments:\n </h3>\n <p>\n General Limitations - The team is hard at work making the most stable, cutting edge, and feature rich Buildbox software to date. We want to bring back all the missing pieces better than ever. We're tackling them as fast as we can with Mac support likely the first to come and mobile exports to follow shortly thereafter.\n\n </p>\n <p>\n Regarding pre-existing BB3 Projects - we've done a great deal to make BB3 projects function inside of BB4. But with an entirely new engine under the hood, and new features being added on top of it, the ways existing projects can break are numerous. When faced with the decision of supporting older projects or giving new tools to make new projects, we have erred on the side of new tools for new projects. If you want to open, test, and explore your BB3 projects in BB4, please do! It is incredibly important that you make sure you backup your project files prior to importing them as BB4 projects are not backwards compatible and we cannot guarantee that your game will run the way you want it to in BB4.\n\n </p>\n \n <h3>\n Features, focus, and what's next\n </h3>\n <ul>\n <li>\n AI (General)\n </li>\n <li>\n Assets\n </li>\n <li>\n Special Effects\n </li>\n <li>\n Fog\n </li>\n <li>\n AI Node Creation\n </li>\n <li>\n Skybox & Ground Textures\n </li>\n <li>\n AI Scene Generation\n </li>\n <li>\n New AI Interaction Points\n </li>\n <li>\n Final Note\n </li>\n </ul>\n\n <p>\n Now that the scary stuff is behind us, let's get excited about what BB4 has to offer!\n </p>\n\n <p>\n <strong>The future is AI.</strong> AI has evolved over the last year at a pace seldom seen. That which was impossible yesterday is often possible today, and improved upon tomorrow. We at Buildbox are proud to bring to you the next set of game-creation AI tools to your fingertips. A toolset that continues to be reimagined, iterated upon, and upgraded - what you see today is incredibly powerful and still only the tip of the iceberg!\n </p>\n\n <p>\n <strong>Assets</strong> - We've purchased, created, and linked a great deal of new assets to the backend and given our AI access to search, arrange, and deliver the assets to you. While we can't guarantee to have everything you ask for, the ever-expanding catalog of assets gives you a lot of great options to start, or expand, your project with. Asking the Buildbox AI Assistant to \"Add a <blank>\" gets this process going.\n </p>\n <p><strong>Special Effects</strong> - we've created a new particle emitter node. This has a lot of controls for you to create your own great animations. But you don't have to do everything yourself! The AI currently knows and is equipped with the tools it needs to create fire, water, snow, and smoke. You can tell the AI to \"<em>Set my <asset name> on fire</em>\" and check out the results. Effects don't need to be tied to an asset, asking the Buildbox AI to \"<em>Add a water effect</em>\" also works!\n </p>\n <p>\n While we are talking about animations, let's talk about <em>Fog</em> for a second. We've introduced a whole new fog system in BB4 (the old one still exists) and you can get started on the world setting or by simply asking the AI to \"<em>Turn Fog On</em>\". If you want to customize these settings you can do so from the 3D World attributes panel on either the mind map or inside the world editor.\n </p>\n <p>\n These are certainly quick and easy ways to access different areas of the software, and show you how we are trying to integrate AI into every area of the software. But while those are certainly easy to use and interesting, how far do they really push the boundaries of what is possible in Buildbox? Well, let's talk about that.\n </p>\n\n <p>\n <strong>AI Node Creation.</strong> We've worked hard on giving you no-code solutions that still provide you the freedom to get in and customize the logic, which resulted in the powerful BB3 JavaScript nodes. Now, in BB4, we decided to take that to the extreme - and now AI can modify nodes or even write custom nodes for you. You can select your asset, and ask it to do more things than I could possibly give you examples for. \"<em>Make it patrol in a circle</em>\" is one simple example but the entire point of this system is that it isn't limited to nodes, or pre-existing logic so your imagination begins to set the boundaries.\n </p>\n\n <p>\n We continue to work to make the AI understand common speech and not just keywords. We have also worked to make sure it understands compound requests with ands, commas, and other linking terms usable. So, for example, you can give the AI Assistant the command to \"<em>Make this jump when I press spacebar and change to a random color and deal damage to the player if it hits them.</em>\" With that said, oftentimes it's best to group your thoughts (and requests) together in batches that make sense. It gives the system more flexibility and makes it easier to modify. This isn't a requirement by any means, just a suggestion.\n </p>\n <p>\n In many cases, when referencing another asset in your project, using its exact name will optimize your results. An example would be \"<em>Heal my character when he collides with a Med Pack</em>\" where \"Med Pack\" is the exact name of your powerup in your project. While the AI will always do its best to understand your intentions, being vague with what it's supposed to interact with can lead to unexpected results.\n </p>\n <p>\n <strong>Custom Skyboxes & Ground textures</strong> - there are two areas right now that aren't limited to assets we have available. \"<em>Make the sky & ground look like I'm on Mars</em>\" will generate and apply custom textures to the new skybox and the returning ground texture areas of your currently active world. Those commands do not need to be run together, so if you only want a skybox or ground texture you can limit your request to those areas.\n </p>\n <p>\n <strong>AI Scene Generation</strong> - This is one area we continue to work hard on. A lot goes into a scene. Asset selection, arrangement (including both size and scale), as well as more game-creation things like physics settings. This area has a lot of room for growth, and we are excited by both the challenge and the opportunity to provide some really cool tools for you to play with. You can try this feature out by asking the system to \"<em>Make me a scene in a graveyard</em>\".\n </p>\n\n <p>\n <strong>New AI Interaction Points</strong> - While the Buildbox AI Assistant is your primary and most visible access point to using AI to easily and quickly improve your game creation experience, there are two other areas you should know about.\n </p>\n <p>\n The first is the AI Edit button at the top of the attributes panel located on the right side of the screen when you have an asset or a node selected. This gives you finer control over where and what is being modified. It can also, in some cases, speed up the process. You should consider using this when you know the asset or node you want modified. When you click the button a text entry form will appear, simply type in your request and it'll be funneled down to the AI Assistant with all the relevant information to optimize your request tagging along for the ride.\n </p>\n <p>\n The AI Edit button will always generate / edit custom code for you. Using the regular AI assistant will result, in most cases, in the system attempting to use default Buildbox Nodes to accomplish your request. But, as noted above, this is an evolving system and we continue to tweak where and how the AI interacts with you and your project.\n </p>\n\n <p>\n The second new interaction point is the group of 3 new selection tools in the top left hand corner of the editor screen. These are the Rectangle, Free Form, and Paint Brush tools. You can use these tools to highlight an area of the screen in which you want to add assets to. Much like the AI Edit button mentioned above, this gives you more control over where added assets appear and this can also speed up how long the process takes.\n </p>\n\n <p>\n <strong>A final note</strong> - As with all AI, ours is constantly evolving. There will be times it isn't perfect, and your increased use and feedback only helps us improve and deliver to you better tools to create your games with. We hope you have as much fun using these as we've had creating them!\n </p>\n\n </div>\n\n\n </div>\n )\n}\n\nexport default BB4AlphaPreviewNotes"],"sourceRoot":""}