daily3014

Works by:

1. suspending the thread via an instance function that yields or via task.wait
2. resuming the thread via coroutine.resume

Highlights:

• hides return values from hooks
• breaks those that "bypass" it (example: Simple Spy)
• works on any instance function that yields
• calling those functions will return the return values of the previous yield
• probably has other uses, i couldnt be bothered to explore

gaymeowing

--!native

-- uuid
-- function for generating a uuid, based on https://gist.github.com/jrus/3197011

local uuid_format = "%x%x%x%x%x%x%x%x-%x%x%x%x-4%x%x%x-%x%x%x%x-%x%x%x%x%x%x%x%x%x%x%x%x"
local wrap_in_curly_braces_format = "{%*}"
local string_format = string.format
local random_seed = math.randomseed
local random = math.random

jackdotink

-- Licensed under the MIT License, Copyright (c) 2024 jack.ink

local function resume_with_error_check(thread: thread, ...: any): ()
	local success, message = coroutine.resume(thread, ...)

	if not success then
		print(string.char(27) .. "[31m" .. message)
	end
end

hhkcu

-- Create a new DynamicImage
local dynamicImage = Instance.new("DynamicImage")

-- Set the size of the dynamic image
local imageSize = Vector2.new(512, 512)
dynamicImage.Size = imageSize

-- Parent the dynamic image to the workspace or another GUI element
dynamicImage.Parent = script.Parent -- MUST BE AN IMAGELABEL - WILL CRASH IF NOT

jLn0n

PLEASE USE THE LINK BELOW INSTEAD!!!

https://celeryrblx.github.io/lua/rnet/

if u still wanna use it click here.

Rerumu

-- Roblox's Luau as a Luau script
-- Translated using https://github.com/Rerumu/Wasynth
local luau_script = [[
	print("Hello, World!")
]]

local Integer = (function()
	local Numeric = {}

DvilMuck

// ==UserScript==
// @name         Aternos Anti Anti-adblock
// @namespace    r0630hh1edcuum5397kimyc0ucwy2h3psn4c6r1u4j
// @version      0.1.25
// @description  Fuck anti-adblock from the free hosting minecraft servers Aternos.org. Parry this you filthy casual!
// @author       Angry Developer against excessive ADs
// @source       https://gist.github.com/DvilMuck/f2b14f3f65e8f22974d781277158f82a
// @supportURL   https://gist.github.com/DvilMuck/f2b14f3f65e8f22974d781277158f82a
// @updateURL    https://gist.github.com/DvilMuck/f2b14f3f65e8f22974d781277158f82a/raw/aternosAntiAntiadblock.user.js
// @downloadURL  https://gist.github.com/DvilMuck/f2b14f3f65e8f22974d781277158f82a/raw/aternosAntiAntiadblock.user.js

luismts

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.