Jump to content


Veteran Driver VII
 TruckersMP Profile
  • Posts

  • Joined

  • Last visited

About TheDarkAngel7

  • Birthday 11/29/1997

Profile Information

  • Gender
  • Location
    United States, Indiana
  • Preferred Trucks
  • American Garage Location
    New Mexico: Santa Fe
  • EU Garage Location
    The Netherlands: Rotterdam
  • Known languages

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TheDarkAngel7's Achievements



  1. I'm really enjoying driving around Utah, for me it's the road layouts that make me want to go there more and more.
  2. I never said that... I'm well aware that slots change. "/mute 1752" mutes the player who is occupying slot 1752, the player who is occupying that slot gets unmuted if you restart the game and he's still occupying that slot, or if they restart and get a different slot. Let me clarify when I say perm mute, when you "/pmute 1752", whoever is in that slot you get the TruckersMP ID of that player who is in the slot and you won't hear that player again, if someone else occupies 1752 you'd hear them. When a Game Moderator bans the player who is in slot 1752, it doesn't mean that nobody can use slot 1752 again would it? ?
  3. Currently I shut off the CB or switch channels if I get someone over the CB who "ate their mic". However, that makes it impossible for me to catch those players who abuse the CB by playing their music over it. A /mute command would help. Also it would help if all it took was a number as an argument to mute someone (/mute 45, /mute 1752... etc). Something to add on to this is that the mutes are only good during the session, the players will get unmuted after you restart your game, but I'd also like to see a "Perm Mute" so if someone cussed you out on the CB for example , you can perm mute them so you don't hear from them anymore (I'd report them too).
  4. I do agree that /fix should work for trailers. Having gone down the CD road many times (being a 5 year veteran), I've been in a few accidents that clearly were not my fault (and I would inevitably report the player who caused the accident and they'd get banned). I don't like having the feeling of pulling a damaged trailer to my drop off when it wasn't me who damaged it. This would be beneficial for those new players who all the sudden find themselves in the path of those trolls on the road, currently if a troll strikes their trailer and the trailer gets so severely damaged... tough luck, they'd hardly make any money from their job. If we have a /fix command for trailers they can fix their trailer in those situations. That's why we'd have a cooldown just like the /fix command has right now. Plus if a player has a near perfect journey the difference in payment between your trailer having 5% damage and no damage is not very substantial to the point where it'd be abuse.
  5. @Prime Alright, fellas, this is hot off the press from SCS Software, posted September 12th: They will be releasing Oregon for ATS at some point in October 2018, the wait is coming to a close for that state! Which means we have at minimum 2 weeks left to wait, and at maximum 6 weeks left to wait. http://blog.scssoft.com/2018/09/oregon-rising.html No news on when Baltic DLC will be released for ETS2 yet...
  6. I like both DLC's, most ATS players have complained why SCS decided to do New Mexico before they did Oregon because New Mexico is a "Brown State". I'd like to see SCS do Utah or even perhaps Washington state as the next state after Oregon.
  7. If I'm rammed in-game I do report in-game first, then I do a /pinfo in game. However, if the player that rammed me quits the game before I can do /pinfo, then I can't get his TruckersMP ID via that command. That's when your logs come in handy! When you get out of the game head to your Documents/ETS2MP/logs. You'll see a bunch of log files in there, in order to get the ones for today, sort by date from newest first. The logs for that day will appear on top. The log file you're specifically after has this name format: log_spawning_day.month.year. I recommend opening this is Notepad++ and you can find the player that rammed you based on your footage, their TruckersMP ID (TMPID) is in that file. Sample of that log file (if they had a trailer): [11:08:58] Spawning GameTruck (ibeastiy(3546) - TMPID: 805695 - Tag: He's my president #) Additional data: [11:08:58] Spawning GameTrailer (ibeastiy(3546) - TMPID: 805695 - Tag: He's my president #) Additional data: Sample of that log file (if they didn't have a trailer): [11:09:00] Spawning GameTruck (MarcineQ(1696) - TMPID: 1254517 - Tag: ) Additional data:
  8. Very nice idea, however, if someone spams messages there should be like a couple minutes of cooldown before that pop-up goes off again.
  9. I'd say avoid the rush areas if you don't have a machine that can handle it, some of the nasty collisions are part of someone lagging and then we get a pile of trucks stopped.
  10. This could also just be Calais being what's it's known to be, lol. Not saying this isn't a bug just making a joke.
  11. I'm going to college currently and I'm pursuing Software Development. The next class I take for it would have a lot of learning Python involved.
  12. You chat on the CB by holding down X. The mod will send out the sound from your microphone, provided the settings are setup correctly. You can change CB channels by clicking either side of the biggest button the CB. The way you bring up your cursor is by hitting Tab and right click to bring up your cursor. Another way to change CB channels is with "/channel [number]" in the chat. The CB currently doesn't display the correct channel when you do that command but your CB channel will change. You can turn off the CB by clicking on one of the smaller knobs on the CB.
  13. Not sure if this would be a great command, I think it takes too much realism away from the game being this is a simulator.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.