Noxico


A quick explanation

As you can see, I’ve decided to ditch the static site and use the blog as the site. Because eh.

You might wonder, and that’s a very small might, where the info went. Where are the files? Where’s… everything?

It’ll be back over time. Perhaps even by next Monday. You can see the reference is already there, and the board, dead as it is, is still at its usual place. It’s just not linked yet.

Leave a Comment

And here we are then

Tumblr has officially shut the door on NSFW content a couple weeks back and the Noxico blog was one of the victims. I just finished reposting almost every post on there worth reposting, and a bunch that weren’t. The only thing missing is asks.

Well, let’s see what we get. I already posted a status update on my other blog last month so… that just leaves the drive to actually do something.

Leave a Comment

Here’s an idea I had earlier: Arbitrary board sizes.

The minimum would be like 80×25, the screen size, and connected boards would have to have matching edges. That is, a board that’s N tiles tall can only be connected on the east and west sides by boards that are also N tiles tall.

Surface boards could be 128×128, or 128×64 to adjust for tall tiles, which would make for nice “powers of two” work and fully covers the equal side lengths rule. Dungeons could be any size, considering those are currently only connected by stairways and such.

This would of course invalidate old saves.

Comments/opinions, please?

[ ] Leave a Comment

Latest commit adds these two things to debug builds. Just aim at a blank spot and you get these options instead of nothing at all.

The “Beasties” item in the menu is already taken care of, but I did later find out that Urta has no tallness and thus broke the Look At function, which is not yet fixed.

[ ] Leave a Comment

Open issues that I’d like your thoughts on

First up we have something about clothing. Specifically, tearing it apart and soiling it in various ways: https://bitbucket.org/Kawa/noxico/issues/14/clothing-statuses

Second, there’s a more technically intricate thing about replacing the scheduler that I’ve recently gutted: https://bitbucket.org/Kawa/noxico/issues/16/goals-needs-drives

Pick one, leave your comments here or, if you can, there.

[ ] Leave a Comment

Cutting down on the body parts

Hi, we’re not dead yet! Here’s a thing that I’ve been pondering and just put in source control as an issue. I thought I’d mirror it here on Tumblr for coverage.


Right now, a given character can have any amount of penises and vaginas stuck down there, all different, and any amount of breasts, each row different. This complicates things like sex. Enormously.

I think actually getting the sex parts done would go a lot better, and actually playing them likewise, if we severely cut down on the whole “mess of genitalia” thing.

I’m thinking, a character would have a single penis token or none, with its size and type, and it may have a double token in there to signify there’s two. Similarly, there can be only one vagina token or none, the ability to have two very much up for discussion. Any extras would be limited to cocknipples, nipplecunts, tentacles, and tails.

[ ] Leave a Comment

A Request for Opinion

Today I’ve been working on the sexual interaction data, both adding new stuff and some of the long-planned format changes. I’d like your opinion on this.

This is the new “Fondle Nipples” action:

choice: fondle_nipples
    _n: Fondle [b:his] nipples
    limitations
        not: 0 havingsex/restrained
        hasnipples: 1
        canreach: 1 breasts
    effects
        stat: 1 stimulation 6
        stat: 1 climax 2
        message
            - [t:Youorname] rub{s} [b:yourornames] [b:nipplesize] [?:nipples].

That’s the old style. The new style replaces the limitations and effects blocks with chunks of Lua code, reducing the parsing code’s overall size by pretty much almost all of it:

choice: fondle_nipples
    _n: Fondle [b:his] nipples
    filter: (not top.Restrained()) and bottom.HasNipples() and bottom.CanReachBreasts()
    effect
        <[[
            bottom.Raise(Stat.Stimulation, 6)
            bottom.Raise(Stat.Climax, 2)
            message({"[t:Youorname] rub{s} [b:yourornames] [b:nipplesize] [?:nipples]."})
        ]]>
-- Alternatively, as a oneliner:
--  effect: bottom.Raise(Stat.Stimulation, 6); bottom.Raise(Stat.Climax, 2); message({"[t:Youorname] rub{s} [b:yourornames] [b:nipplesize] [?:nipples]."})

Now, the old-style message command token picks one of its children at random. The Lua version takes a single string or a table of random picks, which may themselves include more tables of random picks, and can have a color parameter to make the message stand out more. That’s why there’s those {} in there; to remind and invite to add more variations.

All that being said, what say you?

[ ] Leave a Comment