IL opcodes documentation designed with dynamically building assemblies in C# in mind. This documentation implies you know the basics of C# and programming fundamentals, but not how a computer operates at the deep level of understanding (e.g. stacks, heap, instructions, opcodes, etc.)
If you don't know what IL is, it stands for Intermediate Language, also referred to as Common Intermediate Language (CIL). CIL is the one that's used in generating IL code for dynamic assemblies in C#.
v*.*.* for production releases, and a tag of v*.*.*-qa.* for QA / test releases. For example, v1.6.2-qa.3.release.yml action should create a draft release, with the game's rbxl file automatically attached to it.deploy.yml action will deploy the place file to either your production environment or your test environment, depending on the naming of the tag.
| ## Welcome to boatbomber's publish workflow. | |
| # You'll need a few things in your GitHub Action secrets for this to work: | |
| # - ROBLOSECURITY : A cookie of a Roblox account (used to install Studio for testing) | |
| # - RBXID : Another cookie from the account (also used in Studio install) | |
| # - PUBLISHCLOUD : A Roblox OpenCloud API key with Write permission in Place Management for your game | |
| # This workflow assumes that you have: | |
| # - A `aftman.toml` with rojo, wally, selene, darklua, and run-in-roblox | |
| # - A `default.project.json` that builds a place file |
| --- | |
| -- @classmod CameraChallenge | |
| -- @author Quenty | |
| local require = require(game:GetService("ReplicatedStorage"):WaitForChild("Nevermore")) | |
| -- Challenge: | |
| -- 1. Make `camera' always point to the the current or last known camera. | |
| -- a. Problem: CurrentCamera can be nil. | |
| -- b. Guarantee that `camera' is never nil. |