I'm not sure what you mean. The instructions on installation are all in the readme. I'll try to answer your question as soon as I'm more clear on what you're asking.

~Hirato Kirata

I Would love to upload a screenshot (in fact I even had one prepared). But quin has made it so configuration content nodes do not accept screnshots. You can always launch the menus using the -k switch if you think it's going to be problematic.

I could probably upload a few to imageshack and link to them from here...

~Hirato Kirata

Yeah, just put it in the URL field or link to them in the node text.
The node text would be preferable, as the URL is easily missed.

I was going to place them in the text area. but originally as thumbnails. But thought against it, possibly due to heavy traffic :)

There are 4 shots I took, they're not that much different to the original menus (despite being over 3.5X the size)

~Hirato Kirata

The files in other are miscellaneous files, you can pretty much just ignore them. They're pretty much just extras I included for a few people's interest.
diff files just list the differences between an older, and a newer file, if you didn't know that, just ignore it.

In the readme, it gives you two ways to do it, the second method is manually, and the first is much less typing/copying.

for the first method, you merely need to copy the files in /other/data into /data, for the second, you need to remove and add a few lines, the readme is very clear on that.

EDIT 1

I also forgot to mention you'll need to delete config.cfg for the alias to load. or you can set it via the jukebox (I accidentally made a typo in there, so feel free to fix it)

~Hirato Kirata

I did the manual way, I read the readme. But it didn't work.

Maybe that is why it doesn't work - guess I gotta get rid of config.cfg

Yeah, but setting it by the jukebox is annoying - it should automagically start playing a song on the map like fanatic's did.

the normal menus do normally close. I've enclosed a great amount of the guibuttons with guistayopen, a command I requested for use in one of my maps, currently heavily laden with cubescript (29KB of it is scripts so far, not written too efficiently either, but written well none the less).

guistayopen keeps the menu open, and if you look at the script, you'll see it placed in quite a few areas. the biggest reason for it was "convenience", which I realise may also be a royal pain for others. least you'll find you won't need to navigate to some of the menus more than once to create duplicate results. ;)

feel free to remove the guistayopen commands from menus.cfg if it's being to much of a pest. (don't forget the closing ] )

~Hirato Kirata

When editing say a newent, it is much more convenient for the menus to stay open, but when doing say a quicklight it is a pain in the ...

I guess it would be a case of turning off the guistayopen command where one felt it was appropriate - and that may not necessarily be to everyone's agreement, so a hard thing to judge no doubt. Cheers.

just to correct you, the skyboxes do work, but only in CVS :D

when I get time, I'm probably going to rewrite everything from scratch, so those typos will be of little importance :)
glad ye like em :)

~Hirato Kirata

all known problems... for non CVS users...

just wait a few weeks, the next release should be here soon

~Hirato Kirata

eventually, but I've been rather busy recently with school, sandbox and IRC. I can assure you it won't be for at least a few weeks. Also has been doing some crazy stuff, like guibitfield and guieditor, and I've yet to learn how to use them to their fullest.

~Hirato Kirata

I simply extended it to (at "mrfixit ironsnout ogro mrfixit_blue ironsnout_blue ogro" (+ $playermodel (* 3 $teamskins))), so it'll display the appropriate team icon if you happen to have /teamskins toggled on
so if there's a problem, you'll have to be more specific :)

I'm not sure what you mean with the ingame editor stuff too, as they're present in the version I uploaded

and sorry for the stuff that really are missing or incomplete, I'm still working on finishing it up, the release version is below 1.00 at the moment y'know :)

~Hirato Kirata

The default model list used to previously be different, and contain MORE models than the default settings, eihrul of course asked me for that list, and now both this one, and sauer's is equal, so there should be no difference... suppose I can remove that

and I find it a bit difficult to believe the default_map_settings are outdated, but I'll look into it, (I need it for the jukebox)

EDIT
I quickly ran a diff on the default configuration file, and mine, this was the only difference between mine and the release sauerbraten one

-playasong = [ music (concatword "fanatic/" (+ 1 (rnd 41)) ".ogg") playasong ]
+playasong1 = [ music (format "fanatic/%1.ogg" (+ 1 (rnd 31))) playasong ]
+playasong2 = [ music (format "ng/%1.ogg" (+ (rnd 17) 1)) playasong ]
+playasong = [if (= (getalias allowng) 1) [ (concatword "playasong" (+ (rnd 2) 1)) ] [playasong1]]

~Hirato Kirata

i just saw that all the map models and textures of private stan sauer were missing with when i used your files
maybe I do something wrong? :P

Thanks for the feedback

I use pretty much the same method for the menu entries as I did before. I was thinking of doing a main menu like that in the last endeavour, but I decided against it and restarted. I think it was a bit too difficult to do with then :D
Just I started MOSTLY from scratch, so I had a lot of room to customise everything for my liking. not to mention all I learned in my previous endeavour.

I'll keep the colour stuff in mind (red clip entries in the menu anyone?)... I'll see if there's a few PRACTICAL places to do so.

now... was getting everything working, and loading up the menus in any way difficult or painful, as that's what I really need to know... you have to admit though, it's a LOT easier than the last one ;)

~Hirato Kirata

I'm aware of the first one, and has been fixed a good while ago, The problem was I never finished the GUI :D

I'm not too sure what you mean by exec autoexec.cfg, but I'll take a look in the options menu in case there is a mistake
and ascii control chars (whatever they are), isn't something I can actually do anything about

In other news, I'm currently reworking a bit of art (icons) before I do the V0.1 release, with the fixed savemap/loadmap menu

~Hirato Kirata

exec autoexec.cfg means that the ingame editor stuff isn't able to execute the autoexec.cfg from inside the game.
I'll try to find more bugs that have to be fixed.

I'm really looking forward to a new version of your menus!

~byte

I seriously don't know why you're getting it in the first place, let alone the alias it cannot locate.

The entfind menu (which is one of the most tested and obfuscated, due to the overly clever tricks I use), is what I'm assuming you're referring to. There should be no reason for such a message, all the variables it'll need are already declared in the menus, along with those from stdedit.cfg, like /entfind, enttypelist, ea, et.

assuming you installed (and ran) it correctly, try deleting config.cfg, as I said, I can't see any reason for this malfunction in the script
I should probably say thanks, that 'bug report' did allow me to locate another bug in the particle menus :)

~Hirato Kirata

i didnt give as much details before, it was the new mapmodel option on the main menu when in edit mode, and it says "unknown alias lookup: tmpt" and "unknown alias lookup: tmp1" over and over again also, whenever i delete the config file, it just makes a new one after running it!

that's most unusual, that menu doesn't even use those aliases.

guibutton "New Mapmodel" "showgui mapmodels"

that's the code for the button going to the menu
and this is the menu

newgui mapmodels [
    loop i (nummapmodels) [
        guibutton (mapmodelname $i) (concat newent mapmodel $i)
    ]
]

~Hirato Kirata

Try searching the files in your Sauerbraten directory for "tmp1". See if you can figure out what's referring to it.

nevermind, i figured it out myself, just took awhile before it played one of the Cube songs since theres so many others now.

just in case you didn't solve it, open the included default_map_settings.cfg and define a playasong3 alias and replace
if (= (getalias allowng) 1) [ (concatword "playasong" (+ (rnd 2) 1)) ] [playasong1]
with
if (= (getalias allowng) 1) [ (concatword "playasong" (+ (rnd 3) 1)) ] [playasong1]

that's assuming you downloaded the NG music pack and have it activated :D

gosh... sequential playing looks like a mess...
and I still need to ask for a /palias, p as in persistent...

~Hirato Kirata

The main reason I didn't bother making an SP menu is due to the obsolete and outdated nature of the SP module, it has realistically received no real attention since the cube days, though I suppose I can put that in my todo list, a list of SP maps, though I promise you, it'll go into the current maps gui :)

regarding the colours (grr! it's not color in proper English! :P), I've rewritten it to allow movement both ways, even though it's operation is a bit vague to me at present, just need to remember how everything works. for 0.11 it'll be included, and I'll probably try to rework the binds a bit to accept key mutators (like shift, ctrl, alt), also planned is a gui to contain all the editmode helpers, including this :)

changeoutline = [
	VARoutlinestatus = (mod (+ $arg1 $outlinestatus) (listlen $outlinecolours))
	if (> 0 $outlinestatus) [
		outlinestatus = (+ (listlen $outlinecolours) $outlinestatus ) //just making sure it'll fit
	]
	
	if (= (+ $outlinestatus 1) (listlen $outlinecolours)) [
		echo "Outline 0"
		outline 0
	] [
		echo (concatword "Outline " (+ $outlinestatus 1))
		outline (at $outlinecolours $outlinestatus)
	]
]

and while I won't be using any of your scripts, keep at it... though you may want to fix up that if in the third script :)

~Hirato Kirata

Thanks for pointing out the broken script. Forgot to escape the greater than and lesss than. The script should have looked like this (I wanted to edit the script in my original post, but can't since the edit link is gone):

"delta_edit_1" = [
	gridpower (+ $arg1 $gridpower)
	fs = ( div (* (* $gridpower $gridpower) 100) 9 )
	if (< $fs 10) [ fs = 10 ] [ if (> $fs 1000) [ fs = 1000 ] ]
	floatspeed $fs
	echo (format "gridpower = %1; floatspeed = %2" $gridpower $floatspeed)
]

As for the improper use of "color", I think I got that, seeing you are Australian :-) But me being German, I often mix American and British English variants by mistake. I might even produce gruelties such as "gray colour" or "grey color". Doesn't that hurt? Of course you could even argue that grey is not a colour at all, but that discussion would be way off topic I guess...
Back on topic again, I reckon you have planned much more for these extensions, and so I'm really anxious to see the next revisions.

Oh, and one more thing. I want to apologise for that stupid comment about using "sleep". I made it sound as if this was generally a bad thing to use, although I really only meant this special case. I even made a joke about it. Don't know in what mood I was there. I surely didn't want to upset you, or anyone else. This also wasn't meant to criticise your coding style at all. At the time I wrote this, I just thought this was a funny remark, which it probably wasn't.

So again, sorry.
~Pointer

It's all good, don't be sorry. You offered your opinion, and I don't see it being offensive in any way. We're all learning stuff every day :o)

Oh, and the edit link is gone? Damn bloody drupal.. *sigh*

That's certainly a relief, thanks. Nevertheless, I should (and will) be more considerate in the future.

Concerning the edit link, it seems to vanish as soon as someone replies to a comment. Maybe it's by design (from drupal). Would this be an issue to post in Quadropolis users/Feedback?

~Pointer

I suspect it's because Quin edited your comment.

That can't be the reason, as I also cannot edit my other posts as soon as someone replies.

~Pointer

Right, so if someone responds you can't change it later to make yourself look good and the other person look bad. Otherwise you could start flamewars and not get caught, Moderators can edit them still if need be.

Makes sense to me, thanks.

~Pointer

I've been aware of that for a long time now.
it's been fixed in my copy, I just haven't uploaded it yet, since I'd like to get the changelog a bit bigger before I upload 0.11

and then there's plenty of updates CVS versions need

~Hirato Kirata

sensitivityscale has been removed from CVS, now its just for example /sensitivty 10.5 , anyways, unless you want to put up with that message constantly, just use the regular release, or remove that option from the menus.cfg file, if you know how

turns out there were quite a few problems...
This should fix most of it, so enjoy version 0.12! :)
~Hirato Kirata

the particle menu from the quickedit stuff, or the one dubbed accessed via new particle?

~Hirato Kirata

mind telling me WHERE so I can correct it? ;)
~Hirato Kirata

Actually its really pretty easy to find if you use TotalEdit and C++ formatting in it. it makes things way easier to edit and read. Also you might consider removing the "Approve" command since (as i know) it's serverside
Most of the "bugs" are missing ", i only checked the menus, not tested them. So i don't know if they cause actual problems, i'm only notifying you. they can be found here:

1) guitab "Gamemode"
guitext "Key: 3Singleplayer Only 0Multiplayer Permitted

2)guitext "Height (recommended: area/3)"
guislider newpartfireheight 0 500
guitext "Colour (RGB)

3) guitab "Bars
guibutton "Create" "newent particles $newpartbartype $newpartbarprcnt (coltopart)"
guibar

4) guititle "Power Ups"
guibutton "Health" "newent health
guibutton "Health Boost" "newent healthboost"

These are the ones i found. Also i don't know if you see the same things i'm seeing, but with TotalEdit i spotted several places where there was an FF code or whatever and after that a number. What could that be?

-------------------

Your menus give me an idea. i'll install them on my backup sauer and see what new there is that i could implement in my script :)

funny, the only one I did find on my own was the one you didn't mention :P

I've addressed them in the new release...

on that note, V0.14 is out! try the mastermode menu and tell me what you think! :D [and I really would love some feedback on the mess that is the entfind menu ;)]

~Hirato Kirata

game mode tab has a problem. cannot find icon "t" or something, look into it

funny thing, master gui is also bugged. unknown command isai xD
it appears many menus don't work cause of it. take a look, you must have made a typo somewhere
also the sliders that work as a menu scroll are inverted. you have to scroll them up to go down and that's confusing. think you can fix it?

| game mode tab has a problem. cannot find icon "t" or something, look into it
I'm aware of that one already and fixed it locally (I only seem to pick those up in C code :P)

| funny thing, master gui is also bugged. unknown command isai xD
isai is a valid command, least when I checked, the menu operated fine for me; I'm quite certain that isai is a command that's included in trooper as well, can anyone confirm this?

} it appears many menus don't work cause of it. take a look, you must have made a typo somewhere
what other menus than master?

} also the sliders that work as a menu scroll are inverted. you have to scroll them up to go down and that's confusing. think you can fix it?
this is why hirato/mods/reverse.diff exist :P

EDIT: it would seem trooper edition does lack isai, I've added a hack to work around that, thanks for the heads up

~Hirato Kirata

check the title ;)

~Hirato Kirata

i don't know where to put that to be exact.. and i'm sure others will also ask this, so could you make it to open everytime you press F3 on a particle? that would make things much easier than browsing to it.

I take it you're ignorant to the workings of contexteditgui, so allow me to enlighten you.

contexteditgui = [
if ($hmapedit) [
showgui brushes
] [
if (enthavesel) [
initentgui;
do [ showgui (et) ]
] [
if (havesel) [
showgui materials
] [
showgui quickedit
]
]
]
]

the most significant lines are these in our case

if (enthavesel) [
initentgui;
showgui (et)
]

this will initialise the entity menus
and if you've a particle entity selected, it will open the particles GUI, so it already works like that (ie, show up when F3 is pressed)

also when I uploaded the file, I placed the instructions for installing it at the top in the form of comments, just follow them and you'll be fine
if worst comes to worst, just chuck it into your autoexec.cfg ;)

~Hirato Kirata

I haven't even learned half the ways the simplest things in cubecript can be combined, so don't expect me to understand everything.
In anyway i'll see what i can do to make it work

works fine now :D

misan wtf? Hirato made these particle menus and i guarantee they work fine!!
it seems like fisch forgot a part of the script. I think it the coltopart or something. Fisch, please check the txt file again and make sure you copied everything needed from within ;)

afraid not.
you can try using a combination of loop and sleep to do multiple additions or removals.

for example
loop i 10 [ sleep (* $i 100) addbot ]

glad you solved your heightfield issue :P

~Hirato Kirata

Hirato: as far as i know its not possible to use sleep in a loop >.>

try it..

I DARE you

~Hirato Kirata

i'm quite amazed how this actually works, mind explaining to me? :)

open hirato/data/config.cfg, and modify the variables there as needed
you'll need to clear out your other config.cfg.

and I'm aware of the jukebox issue, thank you

~Hirato Kirata

try this update, it should work better in regards to jukebox playback

~Hirato Kirata

this node is 3 years old, dont expect a lot of compatibility or support.

how DARE you make note of this! abnormal people never take note of the year a script was in before installing it on a game which has gone 2 versions further since then! after all, ctf and justice editions barely make any difference right? >_>

Please take your time, read over the node info, and take note of the big bold print at the top that says: "This content is compatible with older edition(s) of the game it was made for, but not guaranteed to work with the current or development versions."

there's a reason they're optional :P
they're a bit over compressed as well though...

~Hirato Kirata