magicor-devel — Public list regarding Magicor development and related issues.

[Magicor-devel] Magicor level editor working in windows

[Claudio <cla...@ya...>]

Got level editor working in windows. Theres a small
glitch with the editor.conf path, but probably it can
be left as is.
It was easy, basically the same changes to magicor.py
Not in the repository, It will require adjust of
makefile for unix people, and I think I created enough
chaos the last time with this file. Better coordinate
with Peter so that him do the makefile.
Strange thing: aspect ratio into the editor seems to
be wrong ( a little squashed ); is not a problem
really.
Well, with this people with all dependencies will be
happy, and I will include a instalation section for
whom had python + pygame but not the other modules.
Including in the binary installer probably is not in
the near future, and I suspect that if included will
add 10MB to the package, going for a grand total of
22MB , zipped.

cya
Claudio

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar

[Magicor-devel] rev90 die after win as original - rev 91 ...

[Claudio <cla...@ya...>]

rev90: die after win as original, ie penguin must
survive the 'happy time' after all fire is out to
really win. If killed in happy time, die.

rev91: cosmetic detail, enabled fragments efect after
ice dies punctured. (seen at space10 that no effect
was on)

 

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar

Re: [Magicor-devel] rev 89 : level issues - die after win continued

[Claudio <cla...@ya...>]

--- Peter Gebauer wrote:

> > if a fire begins to fall, increment can_propagate
> > if an entity activates other, increment
> can_propagate
> > if an entity activated cannot activate another,
> 
> Would it not be easier to check that no blocks, no
> fires and no player is 
> falling? If all those objects are stationary you can
> finish the level, but 
> if one of them is moving you have to wait.
> We would have to make a special check on lava to see
> if it's currently 
> igniting.
> When nothing is moving, falling or igniting we can
> finish.

We have crossed another time. Err, I will be happy to
settle in the proposition of the 'welcome message'. We
only have to take care at level design that there are
at least one solution in wich the 'happy' jump does
not kill the penguin. In the space-09, there are one
'clean' solution and one 'near solution' so its not a
problem. Like you say, the death after 'win' is into
the rules.

cya
Claudio

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar

Re: [Magicor-devel] rev 89 : level issues - die after win continued

[Peter G. <pe...@us...>]

> if a fire begins to fall, increment can_propagate
> if an entity activates other, increment can_propagate
> if an entity activated cannot activate another,

Would it not be easier to check that no blocks, no fires and no player is=
=20
falling? If all those objects are stationary you can finish the level, bu=
t=20
if one of them is moving you have to wait.
We would have to make a special check on lava to see if it's currently=20
igniting.
When nothing is moving, falling or igniting we can finish.

How's that?

> decrement can_propagate
> if a fire stops to fall, after chek for posible
> neighbor activation , decrement
> etc for ice falling, ice cracking and wathever
> Then we change player.finished()
> from
>     def finished(self):
>         if not self.dead and not self._finished and
> self.canMove():
> to:
>     def finished(self):
>         if not self.dead and not self._finished and
> self.canMove() and not can_propagate:
>=20
> How you see this ?
>=20
> cya
> Claudio
>=20
> __________________________________________________
> Correo Yahoo!
> Espacio para todos tus mensajes, antivirus y antispam =A1gratis!=20
> =A1Abr=ED tu cuenta ya! - http://correo.yahoo.com.ar
>=20
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share=
 your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Magicor-devel mailing list
> Mag...@li...
> https://lists.sourceforge.net/lists/listinfo/magicor-devel
>=20

Re: [Magicor-devel] welcome and die after win

[Claudio <cla...@ya...>]

Oh, seems our mails have crossed. Well, with this new
clarification in the level-04.lvl both wins are 'by
the rules', so forget all the can_propagate stuff.
(I will revert all the die after win changes today,
later, I promise)

To all the people doing levels: The order of apareance
of a level in the Level select screen is sensitive to
case, to what separator you have between word an
digits, and zeros are significatives ( all this
refered to the field 'title' of the map. By example

egypt 01
Egypt 02
Egypt 3
Egypt-03
space 01
space 02

will look in a strange order. As revision 89 I
standarized to:
  capital 1st letter
  lowercase other letters
  one space after word
  two digit number, padded with zero if necesary

If nobody complains, can we settle for this standart ?
 
Question svn related: after editing a level (as text)
in a windows machine if you do svn diff to see what
has changed, you get all the lines flaged as changed.
This is for the diferent EOL marker in win vs unix, I
know, but Q: isn't there a command to flag a file as
text-ignore_line_endigs_in_diffs?
Anybody knows ?

cya
Claudio

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar

[Magicor-devel] rev 89 : level issues - die after win continued

[Claudio <cla...@ya...>]

I uniformized the title field of the level (1st leter
in caps, followings in lowercase, separator a blank)
so that levels dont mixed.

I added temporary level-04.lvl ( later I will change
name).Besides being interesting, look at that Peter:
even when the old style ( can die after last fire is
out) in this level you can kill all the fires, be
ready to die in lava, as per your rules, but the chain
reaction is long so happy state ends and you got the
level ).Note: you can win by the rule, but also not by
the rule: kick under the fire, build_ice, kick_block,
go up to the double block.
If you really want to enforce that rule (is
interesting) then probably we need a 'can_propagate'
counter, doing as:
set to 0 at level begin
if a fire begins to fall, increment can_propagate
if an entity activates other, increment can_propagate
if an entity activated cannot activate another,
decrement can_propagate
if a fire stops to fall, after chek for posible
neighbor activation , decrement
etc for ice falling, ice cracking and wathever
Then we change player.finished()
from
    def finished(self):
        if not self.dead and not self._finished and
self.canMove():
to:
    def finished(self):
        if not self.dead and not self._finished and
self.canMove() and not can_propagate:

How you see this ?

cya
Claudio

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar

[Magicor-devel] Welcome!

[Peter G. <pe...@us...>]

(this mail may have been sent multiple times do to my mailman ignorance)

Hello and welcome to the Magicor devel list.

First up let's talk about the bug fixing. Claudio has been very busy making
sure that Magicor works on Windows as well as fixing a few glitches in the
matrix.

Regarding the death/finish level bug, I have resolved it by making sure that
if the player dies before the thumbs up the level restarts.
So, you basically have to finish the map and survive for a few seconds more.
This is to prevent kamikaze ice bombing on fires that are laced with traps
or burning lava.

Frederic has taken it upon himself to sort the levels according to
difficulty. This is a major task, but well worth the effort once it's done.
It will enhance the game experience, hooking the noobs rather than deterring
them because the levels are too difficult.

I'm working on the tutorial levels that will come with the game without the
extras download.

For convencience, if we get a Windows installer (or one runnable EXE-file)
it should include all the extras data. It has come to my attention that
the vast bulk of Windows users do not care much for prompts or unpacking
instructions.
If a Windows user feels the EXE-file is too big to download, he or she can
simply download the source tarball.

We've been ranked quite high on all reviews so far, that's nice.
There's more than 200 hits on the website every day, I think the Windows
release will bring about more users.

I plan to have the RC2 ready this weekend so I'll be bustin' my as to get
those levels done. Good luck!

/Peter

[Magicor-devel] Test

[Peter G. <pe...@us...>]

test

[Magicor-devel] svn update

[wagner f. <fre...@im...>]

hi there,

i've uploaded some levels on the svn (to test my svn access).

i've been a bit overwhelmed these last days but hopefully things will be a =
bit=20
better today so I will try to sort the levels by an approximation of diffic=
ulty.

i'll also upload all files necessary to build debian packages from source

so in short, i'm not dead :)

Fred

[Magicor-devel] fix die after win bug

[Claudio <cla...@ya...>]

updated to rev 69, seems ok in windows.

This letter was sent directly to you and trough the
mail list, to see if it is up. Apoligies if double
hit.

I found a little bug where you die after win. Can be
seen (repeteable) at level space09, if you send two
ice blocks and kill the fires.
I think that entering in happy mode the penguin jump
and gets killed.
Looking at the code there are two posibles fixes:
.change the player.die() method so that it refuses to
die if level completed
or
.change each
if ... and not player.dead: player.die()
to
if ... and not player.dead and not ??player_win??:
player.die

The first is simpler, I commited that, rev 70. If you
prefer the other, tell me or revert and change at
will.
__
>80 on popularity in sourceforge ? WOW, AWESOME!!

cu
Claudio 

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar