Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Patch log from last night: BATTLES - Smoother large Conquest battles: droid pathfinding is much cheaper on the server - Friendly squads and droid waves now pace themselves with server load - Droid lanes are remembered per map, so battles on event maps set up faster - Tool-spawned droids no longer fight Conquest's droids - Droids no longer lose their blaster on your screen after walking out of view - Force powers can no longer grab friendly escorts, prisoners or survivors BATTALIONS - New ACTIVITY tab: see your battalion's trainings and events by month - New BLACKLIST tab for battalion officers - Sub-units: each company now has a Lead and two Officers on the Branches board - BCMDs can override a branch slot's checklist, and overrides now stick - Battalion page no longer breaks on names with special characters JEDI - Force targeting: your power takes who you are looking at, with a target mark and a lock key (middle mouse) - Duelling arenas for spars (arenas are being set up) QUALITY OF LIFE - Voice list: names no longer stay after someone stops talking - Backpacks no longer float behind crouched troopers - Field Ops jobs lend you the tool the job needs - Q menu: new Unselect button - Trainer desk no longer hitches when opened - Clearer wording on the Conquest vote STORE - Balance tuning for the Bulwark, Commander and Railwarden STAFF - Standby mode (/standby) - Snitch has been removed
  3. Today
  4. Bug Type (Server:): CW Severity level (Low - Medium - High): Medium Evidence (if you can): https://medal.tv/games/garrys-mod/clips/nYGB9rJiTTCCr82P1?invite=cr-MSxXWGgsMjE2NDYyOTMz Description of the bug (If it's a black screen issue, please provide your SteamID64): When im in a pile of droids the droids do not fire until I stop blocking, and even then they do not shoot consistently. How can we recreate it: Be a Jedi
  5. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  6. this has already been reported. Going to void this.
  7. Bug Type (Server:): This CT has ARC role Severity level (Low - Medium - High): Low Evidence (if you can): Description of the bug (If it's a black screen issue, please provide your SteamID64):This CT has ARC role How can we recreate it: By looking at this CT
  8. When equipping the RK-6 in first person a grey cloth appear on the left half of the screen. It takes up about a quarter of the left half of screen and moves when reloading or changing elevation like falling. When adsed, holster, or swap weapons it goes away. Almost looks like the cape for the model clips into the first person mode even when it isn't equipped (just what it seems like to me, probs wrong). I assume it is a grey cloth since I am 104th. just wanted to bring it to y'alls attention.
  9. Bug Type (Server:): Conquest supply carring - speed reduction bypass with jetpack Severity level (Low - Medium - High): Low Evidence (if you can): https://medal.tv/games/garrys-mod/clips/nYEAmO9tIAFPk1NkM?invite=cr-MSxrR0IsMjQxMzEzNDg Description of the bug (If it's a black screen issue, please provide your SteamID64): Use jetpack to bypass the slow reduction How can we recreate it: Do that specific type of conquest
  10. This has been marked as acknowledged and marked as a bug that is being looked into. This will remain unlocked in the case that more information becomes present. // MOVING TO ACKNOWLEDGED REPORTS
  11. Bug Type (Server:): Duty board Conquest - Defence type Severity level (Low - Medium - High): Low Evidence (if you can): Forgot to clip Description of the bug (If it's a black screen issue, please provide your SteamID64): AFK People get teleported to the conquest. How can we recreate it: Start the duty board conquest
  12. This has been marked as acknowledged and marked as a bug that is being looked into. This will remain unlocked in the case that more information becomes present. // MOVING TO ACKNOWLEDGED REPORTS
  13. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  14. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  15. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  16. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  17. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  18. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  19. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  20. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  21. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  22. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  23. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  24. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  25. This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
  26. This has been marked as acknowledged and marked as a bug that is being looked into. This will remain unlocked in the case that more information becomes present. // MOVING TO ACKNOWLEDGED REPORTS
  27. @Finn i was messing around with this on main and dev. I cant replicate this issue at this time. I did see this error earlier yesterday in console. We will keep an eye on it, Going to mark as complete
  1. Load more activity
×
×
  • Create New...