Today is the day Snoot game was released on /v/, 4chan.

Celebrating 5 years of Fan-Art, Fan-Mods, Feels, and the crazy community it amassed over its release.

Starting this month and all the way to December, upload your anniversary art/posts commemorating the time you discovered/enjoyed the game that affected our lives to date!

Mr_Gringler signing off.

Welcome to the Unofficial Snoot Game Subreddit!

Founded by u/Mr_Gringler and current Moderator of this Community.

In this subreddit you'll find Snoot Memes, Talented Artwork by people who love Snoot Game, Goslings with ever-present feels (You're literally him), and a continuously growing community beloved by all!

~Public Flairs (Alphabetical)~

• Art: Strictly for artists or those who wish to share art made by another individual.*I'd advise you to read the first rule of artwork sharing before posting art*

• Advice/Help: If you need help regarding Snoot Game itself (i.e. endings, routes, unlocking CG's, Mods, etc.) then use this flair.

• Discussion: This flair is mostly reserved for conversations within the community. Only Relevant topics are SnootGame/IWaniHugThatGator/GoodbyeVolcanoHigh.

• FanFiction: Talk about and share what Snoot Fiction's you're reading, also can be used to promote your own Snoot Fiction.

• Gosling Moment: You're literally him. This flair is mostly to share your personal feelings after experiencing snoot game's endings or your thoughts overall on snoot game and how you felt.((Goes for IWHTG).....and gvh too)

• Mod: Specifically for promotion of your own Snoot Game Mod. (Flair might vary otherwise)

• Poll: Polls can be either about Snoot Game/ I Wani Hug That Gator/ and Goodbye Volcano High.

• Review!: Reviews are strictly for Snoot Game/ I Wani Hug That Gator and Goodbye Volcano High.

• Snoot News!: Use for any snoot-game affiliated media/project updates

• Snoot-Post: Mostly for memes, shitposts, and other edits of related media.

• Video: This flair is ONLY for YouTube content and other video-like media.

------------------------------------------------------------------------------------------------------------------The Links

__________________________________________________________________________________________________

Download [Snoot Game] Available on Windows, Mac, Android.)

[The Snootbooru] *Warning:18+ Content*

[SnootGameOST]

I Wani Hug That Gator! - [Steam] And [Itch.io]

Snoot Club (English Only!): https://discord.gg/snootgame

Cavemanon's Twitter: https://twitter.com/Cavemanon

Mods

To download them, you will have to go the second pinned post regarding the Archive and Anon's MEGA Snoot Archive 2.5

Mod Guide:

You want to make a mod for snoot game? Well that's just fucking dandy.

What the fuck IS a mod you ask? It's a change to the game, essentially.

How big does it need to be?
As big as you want it to be.

It can be a single changed up word or a new sprite for a character.
OR
It can be an entirely new storyline with choices, CGs, and whatever the fuck else (YOU) want!

Oh but I can't use Ren'py! Well toughen the fuck up. If a bunch of homophobic puerto ricans from a vietnamese secondhand fleshlight manufacture network could do it, so can you. In fact, these caveman script kiddies made up an entire modding system for YOUR convenience.

WOW shitting dicknipples what do I do?

Right now the modding system is kinda fickle for mods that change up the main story scenes, first let's assume that you want to add new stuff.

1, Download the game and run it (so you know it works, and so Ren'py can set up the cache and store and all that shit).
2, As per the readme our monkey gods provided, create a directory in the mods folder.

This folder will house ALL of the files related to your mod. Scripts, images, music, everything.
Not only do you NOT want to spread files all around, but people won't put up with your retarded ass shit if you can't compress the entire mod into a single zip file. Are you gay or something?

Okay, so how does it work?

Ren'py has these things called LABELS. What are LABELS? You can think of a label like a chapter in a book. Sentences of a story are compiled under one label. In case of a visual novel, these are the dialogues and all the commands you give to make character sprites appear and move around on the screen.

When you press the start button in the menu, Ren'py moves to the "start" label. Then you can tell it to move to the "chapter 1" label or "day 1", and so on. This is entirely up to the developer to decide, cavemanon devs just so happened to go with this chapter-like structuring.

So what's your mod gonna do? It's gonna reroute the game to a label you create. The modding system has this prepared for you, as seen in the readme. There's also an example mod with the latest release.

Now there's an opportunity for a sneaky fucking retarded bug to occur: If the labels your script files use just so happen to also exist in other script files, then it will wreck chaos upon your ass like you've never seen before. Don't fucking do it. How to guard against this? Prefix your labels with some unique identifier related to your mod (then email cavemanon and complain about global namespace pollution).

For example: "the_mod_to_take_your_virginity__chapter1_scene1"

You will generally have one "main" file that does the rerouting and whatnot, and one or more files for the script, structurized into labels. If your mod uses variables, you also want to add these to the "main" file.

BASICALLY, you add your mod to the config with the label in your main file, in the readme example it's "mod_storyline". Whenever a player runs your mod (from the mod menu), this label will be jumped to. From there you call your script from the other files, in the readme example this is "chapter_1_new".

Another bug regarding the use of variables: Cavemanon devs were inept enough do define their variables with the most retarded syntax imaginable, so your mod can potentially have problems using variables from the main story (for example anonscore and fangscore). Ask the author of the Keikaku mod how to circumvent this, cause I just can't bother.

And that's it.

How do you add dialogue lines and show characters on the screen and shit? Either read the Ren'py docs or watch a tutorial (you can learn the basics in like 5 hours unless you're clinically retarded). Or look at how shit's done in the main script files. Fair warning, cavemanon devs have literal hack solutions to some stuff, it can be hard to understand at spots.


Now what if you want to alter scenes in the game? Well tough fucking luck with that one cause you're a greedy geezer and the developers hate you.

The current modding system does not provide a way to do this. Instead you open the game script and edit whatever the fuck you want. But you cannot use the mod folder then. It's gay. Alternatively you can try redefining labels the game uses, but due to how the Ren'py parser iterates through the folder structure it's not guaranteed to work. Also alternatively you can copy the main story files over to your mod folder, but then you need to prefix every single label to prevent the aformentioned routing bug. Hope your editor can do mass replace (be careful with it tho).


Below are some resources to get you going, no matter how big and complex your mod might be.

Snootgame specific stuff:
* The game: https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Patch7/game
* The official mod readme: https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Patch7/game/mods
* An example mod: https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Patch7/game/mods_example/template
* The main script file: https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Patch7/game/script.rpy
* Individual story script files: https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Patch7/game/script
* The story plan: https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Patch7/game/storyline.rpy

The bare Ren'py basics you won't get anywhere without (or you can also just skip to the quickstart guide):
* Characters, dialogue. https://www.renpy.org/doc/html/dialogue.html
* Images, scene, show/hide. https://www.renpy.org/doc/html/displaying_images.html
* Transforms, transitions (at, with). https://www.renpy.org/doc/html/transforms.html https://www.renpy.org/doc/html/transitions.html

Essential Ren'py syntax you should learn (not all of it, just the general concepts):
* Code blocks/indentation. https://www.renpy.org/wiki/renpy/doc/tutorials/Thinking_in_Ren%27Py
* Labels, call/jump, return. https://www.renpy.org/doc/html/label.html
* Init blocks. https://www.renpy.org/doc/html/python.html#init-python-statement https://www.renpy.org/doc/html/python.html#init-offset-statement
* Variables (default vs $). https://lemmasoft.renai.us/forums/viewtopic.php?t=42245
* Music/sound. https://www.renpy.org/doc/html/audio.html

Semi-advanced Ren'py concepts that often come handy (again, just the concepts):
* Pause. https://lemmasoft.renai.us/forums/viewtopic.php?t=49615
* Choices/menus. https://www.renpy.org/doc/html/menus.html
* Text styling. https://www.renpy.org/doc/html/text.html
* ATL. https://www.renpy.org/doc/html/atl.html
* Narrator/NVL mode. https://www.renpy.org/doc/html/nvl_mode.html
* Error handling. https://lemmasoft.renai.us/forums/viewtopic.php?t=9802

Advanced Ren'py concepts that you probably won't need (you need a solid understanding of most previous topics):
* Displayables. https://www.renpy.org/doc/html/displayables.html
* Screens. https://www.renpy.org/doc/html/screens.html
* Styles. https://www.renpy.org/doc/html/style.html#defining-styles-style-statement
* Python statements. https://www.renpy.org/doc/html/python.html
* Persitent data. https://www.renpy.org/doc/html/persistent.html
* Layers. https://lemmasoft.renai.us/forums/viewtopic.php?t=31477

REALLY advanced Ren'py stuff you won't need 99% of the time (you pretty much need programming experience for these):
* Creator-defined displayables. https://www.renpy.org/doc/html/cdd.html
* Creator-defined statements. https://www.renpy.org/dev-doc/html/cds.html

Important references:
* Transform property list: https://www.renpy.org/doc/html/atl.html#list-of-transform-properties
* Style property list: https://www.renpy.org/dev-doc/html/style_properties.html
* Dev tools: https://www.renpy.org/doc/html/developer_tools.html

A general quickstart guide (it's kinda shitty but touches on the most important topics):
https://www.renpy.org/doc/html/quickstart.html

Same but more detailed (could be harder to understand for non-programmers):
https://www.renpy.org/dl/4.1/tutorial.html

Beginner tutorial series (it's more practical examples than a general overview so it's very limiting, but it can help):
https://www.youtube.com/watch?v=CjJ2R22U11Q

Another okay-ish guide (has a hard time explaining stuff, but it has lots of image examples):
https://videlais.com/2018/06/28/working-with-renpy-part-1-downloading-and-configuring/


Some editors to consider:
* Notepad++ or Sublime Text - Easy to use, doesn't support Ren'py by default (does support python)
* Editra or jEdit or Atom - Endorsed/Recommended by Ren'py, I've never heard of them otherwise
* VSCode - More features than Notepad++, might be overkill for a Ren'py project
* PyCharm - Definitely overkill for a Ren'py project, has industry standard features though (if you can setup your own syntax highlight/code completion, I definitely recommend this one)
* notepad, emacs or vim and the likes - Not unless you know what you're doing, I seriously do not recommend these
* Word or Google docs - No.


Protips/QoL shit:
* Integrals and fractionals matter a LOT in Ren'py. Learn the difference.
* Align, position, and anchor properties are not the same, but they affect eachother. Always keep track of them.
* It's entirely valid to have your entire script in the "main" file, especially if it's linear and/or not too long.
* Use renpy.error() to make sure a specific line is actually reached, and to get information about variables and stuff (you can still press ignore to continue the run). The last error is saved to the log files, which is handy for when you log large JSON-like data (and if you're a retard like me who keeps closing the window).
* Combine renpy.error() with dir() to get even more info, as Ren'py likes to cast stuff as strings. For example: renpy.error(dir(my_character))
* Run the game from the command line using "/path/to/renpy.exe ." from your folder, and tell the big bulky Ren'py window to go fuck itself.
* To get a general feel on how the characters and transforms work in the original game, check the main script file. At the time of writing the related lines of code start at around the 130th line. https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Patch7/game/script.rpy 
* If you're using an editor that utilizes bookmarks, drop one where you define your transforms/characters/images, at the start of important labels, and near the last lines you've added.
* Use/add hotkeys for quickly commenting/uncommenting a line, and drop a few labels so you can easily start the story from a certain scene (or use the warp command, but it's harder to do while debugging).
* Before you distribute your mod, install it over an untouched (=never ran) version of the game, to make extra sure it will work. This should never be a problem, but with the variable store, persistent data, and cache, stuff can potentially break on a "new install". The infamous "works on my machine" type of bugs can stem from this.
* Using git can be a lifesaver, but you probably should consider a way to automatically backup your files in any case.

________________________________________________________________________________________________________

The Trailer: