Server Help

[h04x]

I downloaded the 1.3.5 release (windows), unzipped, set my settings, got an error, figured out that I forgot to disable the python modules, disabled the python modules, and got up and running. I jump in my test zone to check everything out..

My flag is missing..

I checked, rechecked, etc, but I can't figure out why my flag decided to take a vacation without submitting the proper paperwork. I have the new flagcore module loading, $FLAGGAME_BASIC is set in flags.conf, flags.conf is #included in my arena.conf, points_flag is attached to the arena...

What am I missing? Is python now requred to have flags at all?

Thx for any help in advance.
_________________
.:h04x:.
Developer/Sysop
Gemini South


------------------------
salty nuts - borAX

[Dr Brain]

Yes. Python is not optional.
_________________
Hyperspace Owner

Smong> so long as 99% deaths feel lame it will always be hyperspace to me

[-Smong-]

You need to attach fg_wz (which is a python module).

I think the only downside to python is you keep having to ?rmmod/?insmod when developing, with C modules you could just use install and restart the server after it crashed.

[h04x]

Ok...
So I download the full Python 2.4 dev release with source, and install it. I go back to my modules.conf and set the pymod:pymod and <py>wz_fg modules to load up. I fire up 1.3.5 and get an error - Cant import cPickle, but it still enters main loop. I jump in my test zone again, and lo and behold...

No flag.

What do I need to do to remove the salty cucumber error and any ideas on why my flags are still on vacation? I'm a total python n00b (never even used it before, although I do have quite a bit of C, C++, and Java knowledge), but I still managed to open the wz_fg.py module in Idle and look around to see if there was any configuration information I needed to set, but from what I could see it appears to be reading config info from the .conf files.

<shrug> ..

[Grelminar]

Two possibly-helpful hints:

One: 2.4 isn't really supported. The supplied python is built with 2.3.4. It probably can't load the 2.4 cPickle that you downloaded. Try removing 2.4 and installing 2.3.4.

Two: "Attaching" means listing a module in file arenas/blah/arena.conf, section [Modules], setting AttachModules. Before you can do this, the module also has to be loaded (usually via modules.conf). I'm aware this is kind of awkward and annoying. I welcome suggestions for how the selection of which modules get attached to which arenas can be improved.

[h04x]

Aight..
Downloaded 2.3.4, installed. Attached wz_fg in arena.conf using "wz_fg\"

Code: Show/Hide I <cmod> loading C module 'pymod' from 'pymod' I <pymod> loading python module 'fg_wz'

No more salty cucumber errors and my flag is no longer AWOL. One last problem tho (btw - thanx for all the help so far guys) I grabbed the flag, and got this error from the console.

Code: Show/Hide E <pymod> python error unpacking results of function FlagTouch in interface I_FLAGGAME

I jumped out of the arena to look at the console and had this:

Code: Show/Hide E <pymod> python error calling function Cleanup in interface I_FLAGGAME Traceback (most recent call last):   File:"C:\....\fg_wz.py", line 343, in cleanup      spawn(sets.neutowned, sets.neutcenter, neut_flag)   File:"C:\....\fg_wz.py", line 321, in spawn      func(a, fid, x, y, r, myfreq)   File:"C:\....\fg_wz.py", line 132, in neut_flag      a.fg_wz.neuts.append(i) AttributeError: 'asss.Arena' object has no attribute 'fg_wz'

[SuSE]

heheh, I always liked that image

shame it's meaningless

[h04x]

Yeah, I know. But funny none the less..

[Grelminar]

The unpacking error is annoying but harmless. The other is a simple typo: replace "fg_wz.neuts" with "fg_wz_neuts".

Both of these, plus a bunch more flag-related bugs, are fixed in my working copy and cvs, and will be in the next release.