Jump to content

Search the Community

Showing results for tags '3rd Party Issue'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Gamers Lounge
    • Announcements
    • General Discussion
  • Area 51 - Development Zone
    • silEnT Mod - Enemy Territory
    • LESM - Lua Enhanced Server Mod
    • Omnibot - Development, Discussion & Support
    • Enemy Territory Modding
  • Guides, Reviews & Support
    • A Collection of Essential Guides
    • Mod and Software Downloads
    • Game Server Hosting, Support and Reviews
    • Web Hosting, Development & Reviews
  • Help & Discussion Center
    • OS Customization, Discussion and Support
    • PC, Console & Mobile Gaming
    • Programming (C#, C++, JAVA, VB, .NET etc.)
  • Advertising Forums
    • Clans / Guilds and Gaming Communities
    • Game Server and Voice Server Offers

Categories

  • Enemy Territory
    • Software
    • Mods
    • LUA
    • Maps
    • Map Scripts
    • Soundack
  • Call of Duty 4
    • Mods

Categories

  • News
    • PC Gaming
    • Console Gaming
    • World
    • Entertainment
    • Science
    • Technology
    • Software

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. I found this little bug on my server today: If a map-specific config has a forcecvar value that is not specified on the default config, after playing the map and switching to new map, clients who play with ET:Legacy are not forced to change that cvar back to default value. Here is an example that we encountered on our server today: On our server, radar.cfg has forcecvar r_wolffog "0" and r_drawfoliage "0". We played radar, and forcecvars worked normally. Then we switched to Baserace. For me, fog was automatically forced back to 1, like the default value in ET is. But my friend who played with ET:Legacy, still had it on 0 and could toggle it. Same bug happened on et_ufo after that. But when I modified default.cfg to have forcecvar r_wolffog "1" and r_drawfoliage "1" and changed map to battery, my friend with ET:Legacy was forced to have r_wolffog "0" and couldn't change it. I was able to reproduce the entire issue just few minutes ago, with the exception that I couldn't change r_wolffog back to 1 after having forced it to 0 on radar. My friend played on Linux with ET:L 2.71 RC3, and I tried this on Windows with ET:L 2.71 RC4. Server is running silEnT 0.8.2.
×
×
  • Create New...