[cool_myll]

Originally Posted by psychonic None, as far as SM itself is concerned.

Will paths work the same for plugins? Eg:

"vote_warnings" { "default" { "message" "{TIME} seconds until vote." "notification" "H" "sound" "" } "10" { "sound" "vo/announcer_attention.wav" } "9-4" {} "3" { "sound" "pl_hoodoo/alarm_clock_ticking_3.wav" } "2" {} "1" { "message" "Prepare to vote!" } }

Or the paths for sounds will change?

[CuriousG]

Originally Posted by pheadxdll Couple questions, I haven't downloaded the beta to see what it looks like. 1. Reading through the FAQ, it appears as if there won't be any changes needed for plugins that use custom content. Looks like files will automatically go to that downloads/ directory on the client and the game will search that downloads/ directory for the file when you attempt to precache it. Am I correct in this assumption? 2. And where will custom maps/models go on the server? Is there a downloads/ directory there too, can we use a folder in addons to make our game customizations?

There is a downloads directory on the server but it isn't utilized but the server (to my knowledge). As of right now, custom maps go in the normal tf/maps just like before, I'd assume the same for models. When the client downloads the map, it puts it in steamapps/common/Team Fortress 2 Beta/maps

[CuriousG]

Originally Posted by psychonic I stand corrected. The new addons/ path mapping added for clients is screwing with MM:S's loading. We're working on a fix and will surely have it ready long before the changes are live in TF2, CS:S, etc.

Is this the dreaded metamod-fatal.log that contains:

L 02/19/2013 - 23:48:21: Could not detect any valid game paths in gameinfo.txt

[zeroibis]

Will this break sounds and texture and models used by plugins? Would such a change also effect custom maps that reference default textures be effected in the same way if this is the case.

I am sure MM and SM core will run fine but I worry about all the plugins and maps that might break due to the file structure changes and how they may effect referencing files...

[psychonic]

I'm seeing the same questions(s) three or four times here. To clarify:

This will not affect custom files. They will end up at a different location on the client, but as far as the server cares, it doesn't matter. you can still use the same normal path to access them. (sound/blah/, models/blah/, etc.)

If they leave the addons directory mappings in the dedicated server, you can probably also on the server do /addons/<your addon or plugin name>/sound, models, whatever, and then still reference it in the plugin with the normal path (sound/blah/, models/blah/).

Again, the paths in plugins will not need to change as all of the various paths all get normalized into the same search path (addons/<whatever>/ on server, downloads/ on the client, the loose files/dirs already in tf/).

[Dr. McKay]

Originally Posted by CuriousG There is a downloads directory on the server but it isn't utilized but the server (to my knowledge).

Player sprays go into it.

[Powerlord]

Originally Posted by Fletcher Dunn The choice of the directory name “addons” for where to put modified files was a bad one. It conflicts with the server addons directory, where SourceMod et al are usually installed. I’m changing this to be “custom” instead, so there won’t be any conflict or any need to change any existing stuff. “addons” will stay as it has been, meaning it’s particular to the *server* addons. I’ll update the FAQ with this change. There will be a TF beta release in an hour or so.

[CuriousG]

I can confirm SM is working again in beta.

[nineteeneleven]

where can I get a working version of SM/MM for the beta. I tried the latest snapshots and the server just crashed on load.

edit: never mind my beta server was out of date. Metamod is loading now, but sourcemod is not.

Edit2: I can manually load sourcemod with 'meta load' and sourcemod will show with 'meta list' but 'sm version' returns unknown command.

Edit3: I had to add it in the metaplugins.ini and it loaded fine.

[zeroibis]

So should we do this update on top of an existing install or treat it like the OB update and do a fresh install and copy over the folders addons, cfg, maps, materials, sounds, and models without overriding the new versions and then replace mapcycle, maplist and gameinfo?

Will we need to change anything with fast dl or if we do the above everything works fine?