ToME: the Tales of Maj'Eyal

I kinda like the idea of making fearscape a detrimental effect on the player.
But that could make it too easy to dispel?
Perhaps.

This problem is inherent to fear-scape, which will always be hard to balance on randoms.
It is better to tackle this specific problem (e.g. limit the possibilities for generating fear-scape talent)

omfg if you want to play nightmare in adventure mode,
just mod the game!

If you can't code it yourself, ask someone to write an add-on for you.

This discussion, however, is just a waist of time.

I got fearscaped in the gorbat pride.
When I came back one ooze was not disappearing.
When I swapped spaces with him my player got cloned.
The ooze was in range of an antimagic bush.

Got some issue here with beta 43 on lubuntu (32 bit afaik). [CPU] Detected 2 CPUs ALSA lib conf.c:3314:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so ALSA lib control.c:951:(snd_ctl_open_noupdate) Invalid CTL hw:0 AL lib: alsa.c:797: control open (0): No such file ...

Those are some nice icons. Also, what is "SAI"?

test is afflicted by a rotting disease!
test hits test for 10 blight damage

Starting program: /t-engine4-linux32-1.0.0beta42/t-engine [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [New Thread 0xb7fc6b40 (LWP 6144)] [New Thread 0xb77c5b40 (LWP 6145)] [New Thread 0xb6810b40 (LWP 6146)] [New Th...

Seem to be related to particle emitter for me: dumb ai uses T_FIREFLASH Adding entity 328 after 1 Particle emitter error 9797710 (8): attempt to call a nil value Particle emitter error 9797710 (8): attempt to call a nil value Particle emitter error 9797710 (8): attempt to call a nil value Particle e...

Grey wrote:Or maybe just by visiting Zigur and reading some of the lore there.

Except not everyone will read the lore

If traps triggered only once, that would actually make sense and eliminate many of the annoyances. Right now, I am running with the no-traps addon. Traps+auto-explore has awful synergy. *suggestion* So I suggest that a traps trigger once, and then just disappears. *optional ideas* Then perhaps make ...

*clap clap* Nice work everyone. /does a funky little dance

Would it be possible to somehow branch this and develop it communally (allow multiple authors to update their class directly to the class pack)?
Like.. put it on git or something.

I have been thinking about the possibility to turn exploration into a resource. Would it be possible to code something that happens on discovering (=removing the shroud) part of the map? For example, the player has a certain percentage chance of receiving a resource for each tiles he discovers (this...

I'm mostly interested in knowing how to tell which functions to call and how to name them and such. You call the functions that you want to hook. You name the local function whatever you want In the example above: local takeHit_hook = function(self, data) That is the new function that will be hooke...

Perhaps try something like this? Goes in hooks/load.lua local takeHit_hook = function(self, data) if self:attr("protect") then if rng.percent(self.protect_chance) and not (self.ranger_pet==nil or self.ranger_pet.dead)then local distance = core.fov.distance(self.x, self.y, self.ranger_pet.x...