Abyss

[grzywacz]

Obviously not, especially at 2AM.

[Assasin]

i could so use this for the dark elves...

[ILikeProgramming]

i could so use this for the dark elves...

Yep. It would be helpful.

[turin]

It doesn't work for me. I get a bunch of missing transitions; I think it is all of the concave transitions missing.

This is the code I use. (I have the abyss use letter "@", since "x" is taken in my campaign.) Am I doing something wrong?

Code: Select all

#abyss
{TERRAIN_BASE_PROB_FL	@	stars5	20	base	-100}
{TERRAIN_BASE_PROB_FL	@	stars4	50	base	-100}
{TERRAIN_BASE_PROB_FL	@	stars	50	base	-100}
{TERRAIN_BASE_PROB_FL	@	stars3	20	base	-100}
{TERRAIN_BASE_FL	@	stars2	base	-100}
{TERRAIN_ADJACENT_CORNER	@	@	!@	52,76 chasm-convex}
{TERRAIN_ADJACENT_CORNER	!@	@	@	56,68 chasm-concave}
{DISABLE_TRANSITIONS	@}

[Jormungandr]

That is so shiny it hurts. I mean that in the best possible way.

[turin]

He's back!

[yobbo]

My question is, will they function as an alias of cavewall, or chasm? As an alias of cavewall makes the most sense, since no one would want to fly over that, but it might be chasm...

change "aliasof=X" to "aliasof=W" in stars.cfg.

Preferably this terrain should not be used in scenarios with flying units.

The terrain letters "x", "y" and "z" are reserved for campaigns. "@" should work though. The line

Code: Select all

{TERRAIN_ADJACENT_CORNER   @   @   !@   52,76 chasm-convex}

should in stead be

Code: Select all

{TERRAIN_ADJACENT_CORNER   @   !@   !@   52,76 chasm-convex}

(extra "!" )

i could so use this for the dark elves...

as long as you don't explain it .

[yobbo]

I just uploaded a new version of the zip file (get it from the first post in this topic (or here)). Only difference is that I included the chasm graphics, so you shouldn't need wesnoth 1.1-svn to make it work. Someone had already invalidated my stars.cfg by changing the name of the chasm icon in svn anyway .

[guest]

-- an alias of cavewall makes the most sense, since no one would want to fly over that --

change "aliasof=X" to "aliasof=W" in stars.cfg.
Preferably this terrain should not be used in scenarios with flying units.

It is up to the scenario designer (c.f. turin's quote above, emphasis added). I wouldn't fly over that. If the scenario designer thinks it makes sense, it makes sense. Period.

Never ever try to explain why there's a hole in the world. Plot-wise, just ignore it. It's the most natural thing ever.

[turin]

Ah. I see what my error was... (even if I have no clue what it meant.)

[yobbo]

It is up to the scenario designer (c.f. turin's quote above, emphasis added). I wouldn't fly over that. If the scenario designer thinks it makes sense, it makes sense. Period.

Hmm, if I had some flying units and a starry abyss I would:
1) Think "wow, I wonder if I can fly over that"
2) Try to fly over it
3) Start thinking too hard about the precise mechanics of a hole in the world

Anyway, yeah if it works it works.

Ah. I see what my error was... (even if I have no clue what it meant.)

I'd love to explain - but well, you probably don't really want to know .

[Nicolas]

I remember my first wesnoth version,now it has so much improved!
(The mountains and hills:from where are them? the lastest version?)

[Flamie]

maybe it would be possible (useful?) to add a blue&cloud:ish replacement for the stars for floating islands and the like?