Noxico

(This post had no text. It was tagged #i18n #efforts #dutch #mix merge)

Between all the recent work on TML (pure token trees without XML wrapping), wordwrap rewrites, and checking if cacti inside of rocks are still a thing (they shouldn’t), why did I ever do this?

X DISCUSS: Time compression
• Walltime events (night, Fri 13, full moon…) (see girlkawa – time.txt)
• Robe and Wizard Hat items
X Timed swimming so you can cross bodies of water
X Has Gills token, allows unlimited swimming
• Aquatic TF, comes with gills
• Doesn’t Breathe token, for slimes and such
X Slimes can’t enter the water for fear of dilution, to balance Doesn’t Breathe and Has Gills
• An in-game story about a cursed king who’s always in the rain, dark, or sunlight
* Better Him/Her/It considerations (see girlkawa – heherit.txt)
X Support for nipple-less breasts
* Remove concrete babies, add a temple where the midwife dæmon takes them instead
* Replace sex scene system with new design
• Add swaffel support
* Detect item stacks, use action menu to pick one
• Make corpses a kind of container so you can loot from them instead of scattering shit all over

Where • is not done, * is in progress and X is pretty much done.

I don’t know what to work on. There’s too many options! What do?

I’d been pondering the use of XML in Noxico and feeling inspired by YAML and BML, I converted the item database, which is basically a series of token trees wrapped in XML containers, to pure tokens. If I give TokenCarrier.Path() the ability to search for specific values, allow HTML-style Unicode entities both for loading and saving, and hack in the merge feature, I might be able to drop XML entirely.

I haven’t actually put this in the game proper, but here’s the proposed new format in a practical example, compared to the original XML version.

Good idea?

My laptop is fully repaired and cleaned out. I’m picking it up tomorrow morning.

The replacement part is finally here. It’ll most likely be installed this Friday. Then, comfortable development can continue.

I’ll likely focus on Chelsie for a bit though, or some of the other items on the list like showing a list of items on a given tile to pick up instead of taking the first one detected. I don’t want the pants, stupid game, I want the sword!

I’m afraid I can’t be arsed to continue development on Noxico for a while. I’m pretty much devoid of motivation and one of my arrow keys is busted, due to be replaced some time late next week.

Noxico development will continue later. I just can’t promise it’s any time soon.

I was alerted on Twitter of a 100% CPU usage on Linux. So I took a look at it myself.

Noxico 0.1.2.1 on Windows 7 with .Net: CPU usage at 20-something.

The exact same binary on Linux Mint (on a VM) with Mono: CPU usage at around 85%.

Different ways of expressing the usage aside, I’m really starting to feel Mono compatibility is not worth the effort. If it’s not recent versions of MacOS X breaking the keyboard input, it’s inexplicably high CPU usage and lowered framerates. At least the broken graphics after I reimplemented PNG mode made a modicum of sense.

So by now I’ve pretty much had it up to here with Mono compatibility.

And the best part is, if I were to rewrite the game in something that can run natively on both Windows and Linux (let’s assume multiple binaries sharing a single set of data files)… I’d have to rewrite the entire game.

Which I’ve been working on since November 2011.

Is Mono compatibility worth the effort?

After some deliberation with a certain other Kawa, I’ve removed the need for food from Noxico. Foodstuffs now only serve as healing items, with minor TF effects.

They already did that, but there’s no more need to sate your hunger.

Instead, screens can run out of enemies. That way you have to keep moving if you want to keep getting better.

Perhaps I’ll add a thing where newly-spawned enemies get the items dropped by earlier-killed ones?

A while back, I added specific script handlers to items. Aside from when using them, there were optional scripts for equipping and removing items.

Just now, I added timers. To set them up, the item must have a timer token and a timer script block. The token can have a minute count as its value, which defaults to 60 if missing. Every time that amount of time has passed (which is checked in a bad way for now but whatever) the script is executed.

If the timer token has an evenunequipped child token, merely having the item in your inventory triggers the effect. If not, it’ll only activate while worn.