[DeaD_EyE82]

Hi,
I've already read somewehre, that the pipe-versions of dod:s hl2dm and css have problems with the search path of the vdf-files for loading meta plugins.

Now I'm testing my converting script for our customers, because css will be ported to pipe next week tuesday. I've take an example server from one of our customers. MM:S ist loading normally, but mm:s does not load sourcemod with the sourcemod.vdf.

I've tested the stable release (1.9.2) and the snapshot 1.10-dev Build 830. Both doesn't work with the new path of mm:s.

When I'm using the metaplugins.ini, mm:s loads sm. So, I've some possibilities to fix it with scripts. First might be, to add automaticly the line to the metaplugins.ini for loading sm. But what is after an update, when we get this functionality back? Then I've to remove this line from every server (no problem, we have scripts for this)? But not every customer is updating thier server.

Give me an advice how to handle with the update. I don't have tested it with dod:s. So I don't know, if this functionality already working with dod:s againg after the conversion.

BTW: Is there a link like metamod.tar.gz.latest and sourcemod.tar.gz.latest? This might be a good thing for us.



Some infos for server operators:
When you are using the new pipe-system for css and put maps into cstrike/custom/somedir/maps/, the server will only find this maps, when the whole path have no capital letters. I'll report this bug to the mailing list.

Here an example of both variants:
css_pipe_captial_letters_in_path
css_pipe_no_captial_letters_in_path

[asherkin]

Originally Posted by DeaD_EyE82 Give me an advice how to handle with the update.

Update MM:S to the latest snapshot.

[DeaD_EyE82]

Do you mean a snopshot from the stable branch?

EDIT: Both didn't work with vdf-Files.

So I'll add with my script the path automaticly to metaplugins.ini.

#Fix for mm:s-plugins:
if [ ! -z "$(find cstrike/addons/metamod/ -maxdepth 1 -mindepth 1 -type f -name '*.vdf' 2>/dev/null)" ]; then 
	awk '/file/ {print $2}' cstrike/addons/metamod/*.vdf | tr -d '"' >> cstrike/addons/metamod/metaplugins.ini	
fi

Maybe someone can use it.

[pubhero]

Why you want using .vdf files?
Simply use the metaplugins.ini for the metamod based plugins and the sourcemod.
Thats all.

sample

addons/stripper/bin/stripper_mm
etc.

[Bacardi]

Because those vdf files comes with mods and works also
I don't have to do this one extra step for loading those.

Anyway, there is two way load MM:S plugins, make your choice.

Originally Posted by pubhero Why you want using .vdf files? Simply use the metaplugins.ini for the metamod based plugins and the sourcemod. Thats all. sample addons/stripper/bin/stripper_mm etc.