We are proud to present the new duel map for ET (also possible to play 2on2) - Badplace4_beta8! Originally, The Bad Place was DM4 from Quake1 - "One of the three id Software maps included in the "big five" for 1on1 play, created by American McGee" - the version most known to us all is the RtCW remake badplace3 used to create the ET multi_huntplace.

This modified version of The Bad Place is brought to you by  MaTeJ, who has worked on maps such as tjwar_a1_fixed and crypt_final_fixed - his remake of the multi_huntplace map is a better, more complex version with some minor bug fixes and generally attempted to make the map more fun to play and tactical.

A list of changes/bugfixes can be found inside pk3 file in readme.nfo (open it with default windows notepad or Notepad++/DAMN NFO Viewer) Badplace makes use of horizontal and vertical movement/aiming, this makes you practice mouse movement aiming in all ways.



Map Info
 

• Genre: WAR (1on1&2on2)
• Type: Frag
• Gametype: SW
• Timelimit: 5min

Global Map Rules

• Class: FieldOps
• Frag: Deathcounts
• Grenades: Allowed
• Artillery/Support: Disallowed
• Selfkills: Allowed
• Spawnkills: Allowed
• No pauses: Due to bug (item respawn)

Settings

• Recommended Mod: ETPro
• Recommended Client Settings: r_fastsky 0 - tele-camera
• Recommended Client Settings (4 Fireteam): /b_locationMode 0
• Recommended Client Settings (4 Fireteam): /b_locationMaxChars 25
• Additional Client Settings: /cg_wolfparticles 1 - steam of broken pipe

Spawn Settings

• Default Random Spawn: /setspawnpt 0
• Alternative Random Spawn: /setspawnpt 2

Items on Map

• 1x AMMO Resupply Spot 15sec Violet
• 9x 5HP Healing Spots 15sec Green
• 5x 20HP Healing Spots 20sec Yellow
• 3x 50HP Healing Spots 25sec Red

Known Bugs
 

• Acid stops hurting one player once another player falls into it. Once player is dead, acid starts hurting previous player. Acid damage chains (ETMain Bug).
• All Healing/Resupply Spots, when player is at full HP/AMMO, still disappear when taken, but won't give any extra HP/AMMO. This is possible for tactical reasons. We enjoy it, so it stays (Cannot be fixed due to ET limitation).
• Cushion textures won't play footsteps sound when a player falls (ETPro bug).
• Deploy tunnel is blocked when one teammate is lagged inside (2on2 only). Solution: Change spawn to Default/Alternative, depending on which tunnel the lagged player is in, or kick the teammate.
• Green Healing Spots should give 5HP bonus up to 200HP maximum player health, descending each second by 1HP to 100HP (max FieldOps HP), like it was in RtCW (Cannot be done due to ET limitation).
• Hidden Sequence crashes occasionally when the player is shooting to the target while the script is switching to INVISIBLE mode. In the next attempt, the same target would be automatically skipped.
• Limbo Camera displays nothing when player is deploying. After deployed - works fine.
• Pause doesn't stop respawn countdown for Healing/Resupply Spots.
• Resupply Spot should give 3 additional grenades instead of ammo pack (Cannot be done due to ET limitation).
• Sometimes OverBounce occurs (Q3/ET bug).

HQ Config

* Use the high-quality config if exploring the map or searching for secret buttons and such!

Configs are inside the map pk3. Type these into console:

• /exec hq_bp.cfg - for global configs
• /exec hq_bp_dev.cfg - for developer mode configs

README NFO

Check the readme.nfo inside the pk3 map file for more information. Recommended to use DAMN NFO Viewer

Authors

Original Author (RtCW): Refuse
Remade Author (ET): MaTeJ
Version Idea (ET): LoCk

Future

In the near future, if this map-project is a success we will create a valhalla duel remake edition with medpacks to make it more 1on1 style.

Download or test the map here

Source: etpro.de | crossfire

This version is not network compatible with the previous versions. In this release we focussed on fixing stuff. This should make the game a little bit more stable, we still have a long way to go

New features:

• Version check, when we release a new version you will be notified in the main menu
• Obituaries ! (SomeDude? was killed.) Experimental, I'm open to changes.
• Votes have now sounds.
• support for MOTD's (message of the day) on servers, so server admin can advertise their forums, etc

Fixes:

• Fixed a possible divide by zero which could result in a client crash
• The forest map is playable again
• Now a wrongly set g_limbotime value will not crash the server
• TitaN655? fixed the ingame notes
• All maps now have a default wait time of 20 seconds, so you have time enough to check the scoreboard.
• When g_limbotime was lower or equal to (sv_fps/1000) you couldn't respawn, now it cannot be set lower.
• Notebook was missing
• Restart server immediatly when its empty don't wait 5 seconds, because this resulted in AI script errors
• Mission failed now restarts the map and doesn't fade to black
• Master server has now a hostname (I bought rtcwcoop.com yay!), I also made sure that the IP's in your config files are replaced by this
• hostname, this should also fix the empty serverbrowser issues on some clients
• Cleanup in serverinfo cvars
• When a server is spawned bots are removed first.
• Challenge is reset when a client disconnects
• Don't call GAME_CLIENT_DISCONNECT when a client reconnects.
• Some memory cleanups when clients disconnect
• MAN-AT-ARMS fixed the fog, great !
• Cinematics are completely removed in crypt1 and church
• Maxlives maxlives fixes (restart map if everyone is dead), also updated the HUD for this

Here you can see the update check in action:

Source: etpro.de | splashdamage

Urban Terror support improved, QuakeLive support added.
 

You are encouraged to run this latest version and if you experience any issues, you can report them here or on the IRC channel.

Official GtkRadiant Site:
http://icculus.org/gtkradiant/

GitHub Project Page:
https://github.com/TTimo/GtkRadiant

Mailing List:
http://icculus.org/mailman/listinfo/gtkradiant


Post your thoughts and bug reports below. Thanks.

Filing a bug report:

• Make sure to summarizes the problem.
• Accurately describe how to reproduce the bug in precise steps. If it cannot be reproduced, it will be difficult to fix.
• Precisely describe the observed result and the expected result.
• Check your settings and configuration in case these are relevant to the problem.
• Make sure you list your relevant hardware, operating system, version of GtkRadiant, or any other system information.