The logo competition for the 2025 4chan Winter Cup is now taking submissions.
The deadline is January 6th, 23:59 UTC. Logos will be placed in this gallery to facilitate discussion. This will be followed by a polling period to determine which logo will be used.

Please send all submissions to Potatotron. You must supply a high-res PNG file (5000x5000 limit) and the original multi-layer source file.

Cloverleaf logo: .png .svg

Cloverball logo: .ai .png .svg

User:Two Scoops/Ideas

From Rigged Wiki
Jump to navigation Jump to search

WIP

AKA "Shit I want to do but have no time for"

Rigsuite (SEN:P-AI 2.0)

Either a single program or suite of programs that would almost completely automate the task of rigging as well as save editing and record-keeping.

A general overview of functionality:

  • Most if not all options/configuration should be done through a config file rather than wasting time going through all the trouble of making an options menu UI just so it can turn out janky and poorly layed out.
    The config file would serve multiple roles and could optionally be split into multiple files for convenience (for example, only overwriting one chunk of config you possibly just got from someone else by simply replacing the file)
    Rather than try to "invent" some new format or something, and due to the possible structural complexity it could take on, the config file would be written in the form of a Lua script (it could be any script language, but I've just preemptively decided on Lua)
    • General settings/configuration
    • The in-memory or file layout of various data structures like the stats table or tactics info (for SEN:P-AI this is currently just hard-coded which means I have to create a new exe every time I update something as simple as a stat name)
    • The cup rules. For game day that would be shit like number of subs or voluntary timeouts, and if this thing gets used for tactical exports/imports then also stuff like legal player stats. This is not easily expressible as an all-data-no-logic file format, hence the scripting language.
    • (possibly) Instructions for manipulating the UI to achieve requested tactical changes in an automated way via virtual controller input (also in the form of a script)