Jump to content

kajto3

ET Member
  • Posts

    750
  • Joined

  • Last visited

  • Days Won

    3

kajto3 last won the day on November 10 2023

kajto3 had the most liked content!

Contact Methods

  • Youtube
    https://www.youtube.com/user/kajto3
  • Steam
    kajto3
  • Discord
    kajto3#0097
  • Website URL
    https://ratemyhud.com

Profile Information

  • Alias
    =F|A=PlaYer!
  • Admin
    15
  • Server
    ETL Euro #1
  • Gender
    Male
  • Interests
    ET, Music, Movies, Internet, Coding, and ET
  • SL
    47380894
  • TB
    6029616
  • Location
    PL

Notes

  • T-M
    3-3

Stats

Recent Profile Visitors

7898 profile views

kajto3's Achievements

Proficient

Proficient (10/14)

  • Conversation Starter
  • Very Popular Rare
  • Dedicated Rare
  • Reacting Well Rare
  • First Post

Recent Badges

1.3k

Reputation

4

Community Answers

  1. I've been working on our ETL servers, which are different compared to silent (stuff like sprees is controlled by Lua API which is fully customizable, while silent has it built into the mod). Haven't touched silent for years and don't work on silent FA servers either. BUT, I know where to check for cvar explanations and I found this: https://mygamingtalk.com/wiki/Silent_Mod_Server_Cvar#g_spreeOptions Apparently you CAN exclude bot kills from spree kills, as long as you put 256 inside bitmask cvar value: 256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees) The rest is up to you
  2. All the best bud, keep working and having fun 👍
  3. Some questions: 1. What mod are you using? Or is it default mod, either etmain (if 2.60b) or legacy if (ETLegacy). 2. I mentioned the ET versions. Which one are you using? 3. So your final purpose is to run the server locally and share it with friends? Or as a dedicated server? What OS will be used?
  4. What I meant by AV was anti-virus. You mentioned Windows Defender, so yeah let's try with it disabled, but why only you would have this issue though... Also, I wasn't expecting "probably" as an answer for PC specs 😄 what I meant was your PC specification, like CPU, graphics etc
  5. So there is something that slows your ET down wonder if you wait long enough, you'll be able to connect to a remote server eventually. Still, the fact that 64bit ETL works just fine is most interesting. Are you using any AV software? Do you install your ET/ETL on Onedrive or some other cloud storage? Your PC specs maybe? Tried with default/fresh config?
  6. And you were able to play on that hosted server right? Creating a server from the main menu is slightly different than creating a local server on your PC and connecting to it from your regular client. So, let's host a server from your ETDED.exe (ET 2.60b), which will be more compatible with your ET 2.60b client. 1. You will need your default ET 2.60b directory with ETDED.exe inside of it (it should be there by default, unless you removed it). If you have a lot of files in etmain, it might be a good idea to create a new directory with only essential files, which are: pak0.pk3, mp_bin.pk3 and qagame_mp_x86.dll 2. Create a shortcut to ETDED.exe by right-clicking on it -> Create shortcut. 3. Right-click the shortcut, go to Properties, in the Target box (first from top) add a space after "path\to\your\etded.exe" and paste: +map oasis +set net_port 27960 4. When it starts, you can type the status cmd inside of it, it should show you the map name and an empty list of players. While it's running, you can test your 2.60b or ETL 32 bit clients with it. Just do /connect 127.0.0.1 from your game and you should be able join your own etmain mod server. I'm just curious if your game freezes because it's something on your PC or is it a problem with connecting to other servers
  7. Have you tried creating a local server from your 2.60b and connecting to it? For example, create a shortcut to your etded.exe, run it with +map oasis parameter inside Target box, try to connect to localhost or 127.0.0.1
  8. Since Legacy has replaced ETPro as a mod for competitive games - a little update is required. ~ BEFORE YOU START IN ORDER TO PLAY ON LEGACY MOD WITHOUT INCOMPATIBILITY ISSUES, IT IS RECOMMENDED TO USE THE ET: LEGACY CLIENT. If you don't use it already, you can download it from here: https://www.etlegacy.com/ (make sure to use 32 bit version!) Take your time and read the wiki pages written by ETL devs. Installation, path structure, change-log, new cvars, commands. Everything you need. https://github.com/etlegacy/etlegacy/wiki ~ BINDS & SCRIPTS Basic scripts that'd barely changed over the years + some new stuff you need to know. Selfkill: bind [key] "kill" (it will auto tapout) Enemy spawntimer: bind [key] "resettimer" (you don't need multiple binds - the correct spawntime for given map and team will be set automatically) (optional: bind [key] "sharetimer", in order to share the spawntimer you've set) Spawn selector: bind [key] "setspawnpt 1; play sound/menu/select; echo ^0[^7spawn @ 1^0]" bind [key] "setspawnpt 2; play sound/menu/select; echo ^0[^7spawn @ 2^0]" bind [key] "setspawnpt 3; play sound/menu/select; echo ^0[^7spawn @ 3^0]" bind [key] "setspawnpt 4; play sound/menu/select; echo ^0[^7spawn @ 4^0]" bind [key] "setspawnpt 5; play sound/menu/select; echo ^0[^7spawn @ 5^0]" bind [key] "setspawnpt 0; play sound/menu/select; echo ^0[^7spawn @ default^0]" Some spawnpoints are different in Legacy compared to ETPro. You can use /spawnmenu or /listspawnpt to make sure you spawn at the correct place. Class selector: bind [key] "class m 1; echo ^0[^7medic^0]" bind [key] "class e 1; echo ^0[^7engi w/ smg^0]" bind [key] "class e 2; echo ^0[^7engi w/ rifle^0]" bind [key] "class f 1; echo ^0[^7fops^0]" bind [key] "class c 1; echo ^0[^7sten^0]" bind [key] "class c 3; echo ^0[^7sniper^0]" bind [key] "class s 2; echo ^0[^7mobile mg^0]" bind [key] "class s 4; echo ^0[^7panzer^0]" ~ CUSTOMIZATION Over the years of Legacy mod development, there were lots of cvars removed and some added. At least 50 removed cvars are HUD-related cvars. Legacy has an advanced HUD editor that allows players to customize their UI for maximum convenience. If you wanna see some other players' custom HUDs, you can check this page: https://ratemyhud.com/ The HUDs were made by players, you can preview and download them. Some also include a .cfg file! Go to /about page for more info, like installation details. The first thing I did when I put my hands on the HUD editor was moving my spawntimer and enemy spawntimer closer to the center of the screen. This way I almost never selfkill on full spawn. Make some stuff bigger (my radar/minimap, yeah), some stuff smaller, get rid of something or move it somewhere else, and you'll be done and good to go with your own setting. More about the HUD editor --> https://etlegacy.readthedocs.io/en/latest/hudeditor.html There's also a tutorial by @Shoresy, where he talks about Legacy configuration and how to use HUD editor: Here are some cvar and their values recommendations that might be useful in competitive gameplay: Make sure you can see teammates changing their classes: cg_fireteamLatchedClass "1" Make your popups stay longer, so you see for example, how many enemies already died: cg_numpopups "9" cg_popupStayTime "12000" cg_popupFadeTime "20000" Have demo autorecord enabled, so you have a way to confirm or learn something after the match. set your cg_autoaction to "1" or one of these "3" "5" "7" (different value - different auto actions taken except for taking the demo) Enable bullet tracers for enemy only. This way you can often determine where the enemy was shooting from. cg_tracers "3" This one might be just my preference - but I'm so used to playing this enabled. Setting cg_simpleItems to "1" (enabled except for objectives) or "2" (enabled for all items) transforms the stuff that lies on the ground (medpacks, weapons, obj, etc.) into more distinguishable, shiny objects. Much easier to find stuff around. Comp games tend to be fast, so you need to be fast. Speed up your console open/close animations with this cvar: con_openspeed "15" Enable quick chat binds. For example, when you hold a grenade and use weapalt (right mouse button press by default) you'll say "Fire in the hole!". This can be done with this cvar: cg_quickchat "1" Even though you'll use comms, sometimes it's good to emphasize something in-game. All quickchats: https://etlegacy.readthedocs.io/en/latest/cvars.html#cg-quickchat Hide gun/disable gun animations. This might feel weird at start, but having the guns doing less movement or having them hidden completely, can greatly improve visibility. In Legacy, you can use either cg_drawGun "0" (hide all weapons/tools) or cg_drawGun "2" (hide primary and secondary weapons only). To control weapon animations, there is cg_weapAnims bitflag cvar. Default is 15 meaning all animations are enabled. Choose and add together the animation values you want to see. | 0 None | 1 Move | 2 Firing | 4 Reload | 8 Switch | (I prefer to use cg_weapAnims "13" - firing anim disabled and cg_drawGun "1" - no weapons hidden) Show spawnpoints during warmup. There's a cool feature that draws exact spawnpoint numbers on the floor/where you spawn. Since newer maps and ETL overhauls use more spawnpoints (not to mention the so-called minor spawns) this makes it easier to find out the perfect spawnpoint to spawn from. cg_drawSpawnpoints "1" You'll need to adjust your cg_fov and sensitivity values if you're switching from other mods. Due to game changes, those might feel slightly different. Fov value can be converted (for example using this formula - replace ETPRO_FOV with your fov: https://www.wolframalpha.com/input?i=atan(3%2F4*tan(PI*ETPRO_FOV%2F360))*360%2FPI) And here's list of all cvars that I use, if you just wanna copy-paste seta cg_fireteamLatchedClass "1" seta cg_numpopups "9" seta cg_popupStayTime "12000" seta cg_popupFadeTime "20000" seta cg_autoaction "5" seta cg_simpleItems "2" seta con_openspeed "15" seta cg_quickchat "1" seta cg_drawGun "1" seta cg_weapAnims "13" seta cg_drawSpawnpoints "1" I'm not covering any renderer cvars here, there's plenty of tutorials on this I think. The Legacy mod changes in that area were less significant than the UI for example. Anyway, here are more cvar explanations: https://etlegacy.readthedocs.io/en/latest/cvars.html (as of writing this tutorial, not all cvars are described, sadly). In general, ETL devs have fixed many cvar default values, so that new player with standard config will have pretty much "plug&play" client. Not to mention, the in-game menus are much more intuitive - you just hover on a setting and it tells you what it does. For undemanding people - all you need is a few clicks and you're ready to go, while default ET 2.60b/ETPro config is quite unplayable. Speaking of old ET versions - it is highly NOT recommended to use old configs with Legacy. These 2 commands will come in handy while playing with configuration: - /cvar_restart - self explanatory, resets all cvars to their default values - /cvar_trim - when used, it will remove all invalid/unknown cvars from your currently loaded config. If you think you've got a mess in your .cfg, consider using this command, and then using /writeconfig *filename.cfg* to save it to a file. ~ COMMS Since Discord became popular, it took over all ET players using other apps for communication (like TS3, etc.). Having a working mic and actively supporting your team by giving accurate comms is crucial in successful team-play. Don't worry if you don't know how to say something or how to call a specific place - takes like 5 times playing a map to learn. You'll just describe what you see and more experienced players will understand you with no problems. And NEVER worry about your accent/bad english. You're having a perfect opportunity to learn how to use spoken version of the language, no one will hate you for that. ~ TACTICS Those have not changed. Even though there were new features added, like dropping the objective (which has never existed on ETPro), this is still the same game, only better IMO - some still miss the old days - I don't do much, really. If you're new on that, I found this old tutorial about ETPro scrimming basics, most of the tips are still useful: --- I'll do my best to update this tutorial when some changes are needed. Meanwhile, don't hesitate to reply to this thread or DM me if you've got any questions. Happy fragging!
  9. Use 32 bit version. Updating your ETL client should cause no issues, but joining a server with legacy mod 2.82+ might.
  10. Welcome to Fearless Assassins! Hope you have some great time here
  11. Hello and welcome to FA, been having some good games on ETL server, keep it up
  12. As always, happy to announce a new ET: Legacy update! After nearly a whole year, we've lived to see a round version number 2.82 Feel free to download at https://www.etlegacy.com/download (remember to use 32 bit version if you also play on other mods than Legacy) Full change-log: https://github.com/etlegacy/etlegacy/wiki/Changelog#2820---march-2024 Summary & gfx by @kemon:
  13. kajto3

    ET Server Suggestion ETL:US and ETL:EURO - map suggestions.

    While we wait for @daredevil to enable the mapscript change (see Discord), version 14 of etl_supply was released and uploaded to FA ETL US.
  14. A new version (v14) was just released - fixes some issues that came with this big update. I added it as a new version here. Meanwhile, you can also get it from etlegacy.com page: https://www.etlegacy.com/packages/etl_supply_depot_v14
  15. ETL Supply V13 View File That's the 13th version of etl_supply overhaul by Kemon, ETLegacy team. Similar to other ETL overhauls, this map includes a neatly written mapscript with various customization options. Waypoints from previous versions should work properly, they can also be found here https://app.assembla.com/spaces/omnibot/subversion/source/HEAD/Enemy-Territory/0.8/et/nav Here's the full changelog including all changes from version 1-13: Submitter kajto3 Submitted 03/05/24 Category Maps Map Type Objective Map Size Medium Large Map Theme Day Attacking Team Allies Waypoints Other - Provide Link Known Issues None  
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.