Skip to content

Roadmap

  • Luau runtime layer (thanks godmothersfire!)
  • Parts (thanks godmothersfire!)
  • Shadows (thanks godmothersfire!)
  • RunService (thanks godmothersfire!)
  • Workspace (thanks godmothersfire!)
  • UserInputService (thanks godmothersfire!)
  • Lighting (needs more work)
  • TweenInfo (thanks godmothersfire!)

Projects will initially have:

  • a .gargantuan/project.instance.json
  • a .gargantuan/project.config.json

Studio progress:

  • .instance.json format (thanks godmothersfire!)
  • Load projects by CLI (thanks godmothersfire!)
  • Opens existing projects (thanks godmothersfire!)
  • DirectoryLink (NOTE: needs bugfixes and edge casing for Rojo init.luaus) (thanks godmothersfire!)
  • New project flow
  • Implement UI primitives
  • Widgets
  • Docking
  • Plugins system
  • Ribbon bar
  • Settings plugin
  • Explorer plugin
  • Properties plugin
  • Console plugin
  • Building tool plugin
  • Run Rojo inside Gargantuan :)
  • ProcessService (great for Lest and friends!) (thanks godmothersfire!)
  • Implement the remaining data types to API parity
  • ScriptSecurity enum, tentatively: None, Plugin, Studio, Internal
  • require() implementation with user-provided require aliases (thanks godmothersfire!)
  • @game/... maps to requiring DataModel... (thanks godmothersfire!)
  • Roblox compatibility mode
  • Render GuiObjects
  • Render Frames
  • Render TextLabels
  • Render ImageLabels
  • UIListLayou
  • UICorners, UIGradients, UIPaddings, UIStroke, etc
  • UISizeConstraint, UIGridLayouts, UIPageLayouts, UIFlexItem etc
  • TextButtons and ImageButtons receive input
  • TextBoxes are stateful
  • Render ScrollingFrames
  • Render EditableImages
  • Drag and drop
  • EditableImages
  • ViewportFrames
  • Stylesheets?
  • Basic physics colliders (thanks Native315!)
  • Mesh colliders
  • Visual Materials
  • Physical Materials
  • MaterialService
  • PBR
  • LightingService
  • LightingEffects
  • Textures and decals
  • GlslSourceContainer, VertexShader, FragmentShader, ComputeShader classes
  • Competent lighting/renderer
  • MVP player controller preset (Exact obbying can be done later)
  • Monorepository layout (Can be done in 0.1 if deemed feasible)
  • Migrate to flecs with an ECS layout (Spook has a reference implementation)
  • .instance.bin format
  • Compile projects into executables
  • Implement client-server boundaries (run two Gargantuans at once for now)
  • Datastores
  • Monetization $$$$$$ (by the developer, not Gargantuan)
  • Constraints
  • ParticleEmitters
  • Trails
  • Beams
  • Implement the assortment of Lute stdlibs
  • Implement code modifications with @std/syntax
  • Self-hosting game servers
  • Self-hosting CDN servers
  • API rich enough to get large games onto Gargantuan (ie. Welcome To Hell)
  • Visual scripting (block & node based)