Editing and Customization > Community Content

Re: community maps fixed for v5.0

(1/3) > >>

fleet84:
most are just fixed versions of the community maps done in the simplest way i know, which is using the program "vide" "pak file lump editor" and taking all the assets of the previous versions of goldeneye source and attaching well everything into the bsp file itself. others are altered to fix minor things like missing assets that can never be found no matter which version and some fixes for the ventilation systems, but all the rest are just the original files themselves stored in the archive folder of bz2.

https://www.dropbox.com/sh/hpuxvuquh4a19jw/AAD9bEE5z6Z3K85WBYm4_vlXa?dl=0

Adrian:
 Fleet, we appreciate you taking the time to put this together and help consolidate our community content and get it working with v5.0. However, getting a map up and running with the latest build of the game should ultimately be the responsibility of the map's author; I'm currently wrapping up a new revision of Chateau DuClare and will release it soon.

 When updating a map, it's more than simply packing in the missing content. The author might want to update certain assets, tweak the layout, adjust playability, etc. A map is an author's vision; it becomes undermined when old revisions are brought back into circulation. If an author chooses to update and release their map, that is their business.

 It's also worth noting there are soundscape files, music script files and loading screens all linked to the BSP. By adding the _fix suffix to the maps, these links are broken. I hate to lecture, but quality control must be exercised when re-releasing third-party maps; there are many steps involved and plenty of room for things to go awry.

 Also, there are a handful of maps in that archive that didn't need fixing since they were released after v5.0 came out: ge_osiris_a2, ge_hokona_a1, quake_e1m7 and ut_codex_v2

Again, thank you for taking the time and effort to do all of this, but next time at least ask the authors before you go through with it.

Troy:
I think he meant well, but I'd have to side with Adrian on this.

Entropy-Soldier:
Yeah, we understand where you're coming from but without the proper steps being taken this can cause problems for map authors who want to update these maps down the line, or want them to pass into the halls of history.

It's honestly our fault for not making this clear somewhere on this forum, since the pitfalls of this aren't super obvious.  I've made a post which will hopefully clear things up for people in the future, but obviously it's too late in this case.

I would recommend getting permission from as many of these map's authors as you can to update their maps and keeping the rest for your own personal use.  Don't worry if you can't get permission for all of them, some of these maps have had their day already and are ready to move on.

mabeenot:
I for one am very happy to see this. A lot of the community maps from earlier versions of GES are abandonware. I think the responsible thing to do is to always contact the original creator when possible. But so long as you appropriately label a map that you've "unofficially" made changes to, there's no crime committed in providing the community with a functional version of maps that were released under the same free license as GES itself.

Navigation

[0] Message Index

[#] Next page