Jayarr

Seeing as the venator we chose was an edit of another map and not something we fully worked from the ground up, it's hard to say. If I'm reading this post right, this is going to be utilized on the event server for GMs, and as much as I'd love to have the time to fix every broken map we have for events, I just don't see it happening. After the current map is done, there are other projects that I'll have to focus on, so the likelihood of me fixing the venator map any time soon isn't high, sadly. That's not to say this suggestion shouldn't stay up, if the community wants it then we'll find a way to squeeze it in at some point, I'm certain.

Unfortunately, this suggestion has been DENIED. If the same suggestion is submitted again within 60 DAYS of this post it will be automatically denied. // LOCKED // MOVED TO [CW] SERVER SUGGESTIONS - DENIED

We already have memorials in the bunks, and I think it's better to keep it that way. I appreciate the concept, as I'm sure most do, but it doesn't need to be shoved in ours faces. Edit: There are not actually any in bunks, but we'll get that squared out yes a founder allowed me to deny this

Please contact a founder for permission to post model suggestions.

-1 You've had quite a few chances at this point. Sure, you can be funny at times, but you are more annoying then anything. If there was actual effort made to play, then sure.

That's great and all, but everything you just mentioned only functions on a case to case basis and isn't consistent enough to warrant such behavior for a whole team. Enforcing required tours and more "enthusiastic" engagements would never really work from a volunteered staff team who already have to put in a good bit of work on their own accord, as cool as the idea is

The problem with the TR problem is it's more work where it doesn't need to exist in some instances. The whole infrastructure that surrounded the TR team in the past was only a useful ticket to personal promotions within the staff team itself, and didn't really help much else, not even player assisted income, compared to what we have going with the quiz and the occasional player held trainings. I personally find it within staffs best interests to focus on things like the GM team, and as proven by how much work has been forward into that team itself and how many events are being actively held, it only proves the point that shifting focus away from training was nothing more then beneficial. However, I believe I get one standpoint from this post; and that may be that staff should have another branch to focus some effort into aside from the GM team itself. What that branch may be is entirely open to discussion, but I come from the personal standpoint that staff should have choices on what they wish to do for their time in the team, other than being a GM. TR, however, is certainly not the answer at this time. Even so, the points made would be valid at a point where we had very steady income like that of which we saw in 2018, but with the current statistics, the TR team would just hinder us more than assist us.

Question Answered

I don't

This suggestion has been IMPLEMENTED. (Suggestions that have been implemented into the server)

This suggestion has been ACCEPTED. // LOCKED // MOVED TO [CW] SERVER SUGGESTIONS - ACCEPTED

This suggestion was denied three years ago for a very serious reason, and while three years may seem a lot, nothing about these two addons has changed from what I can tell. The ability they have to break and/or crash the server is pretty crazy. The tool would definitely be useful, but the two suggested aren't where it's at.

Could you specify which models have this issue?

This is a good move before suggesting this map to be utilized on main. I severely doubt in it's ability to uphold performance on high pop due to the fact that its ship to ground alone. It'll require thorough testing to even pass something like this off, and there are many more factors to take into consideration past performance itself.

This is certainly and interesting suggestion. There have been a few, if not multiple instances, where this topic has cropped up for DU. Over the years, quite numerous things have happened to the battalion itself that raise an otherwise questionable brow to its nature. I feel like I should maybe highlight these instances, as while they're not key fundamentals on how the battalion may behave today, they certainly are echoes of what it could be/already may be. 1. DU existed outside of the realm of our server, before we even had Synergy. On the prior server, there was a lot of misunderstandings and otherwise hatred targeted toward DU. This was typically held by misled feuds that often times resulted in the battalion maintaining a bad name for itself, thus detracting any new income of people willing to help. This has been the case multiple times on this server in the past, and in some instances I'm certain it is the case now. But this leads on to number 2. 2. When our server was created after the split from the other one, there was a decision made for which battalions would stay, and which would go. DU was obviously on that list, as not only was it an inactive battalion, but the people that surrounded it in its toxic image were still persistent. This lead to an overall dismissal of the battalion for the next year to come. What this accomplished is that it's image was completely wiped and its slate cleaned. When DU returned, not a single instance of any of its "prime" members returned. This will be expanded upon in 3. 3. Fast forward that year I mentioned, and Ginyu had won a bet with Joah to add the unit back to the server. The terms were agreed upon, solely if the BCMD could get active numbers within the first month. With this, the first BCMD was Dargon, accompanied by his friends. Whilst they did kickstart the battalion in the best way possible, Dargon himself resigned about two weeks after getting the position due to the general concept of the battalion not dragging any attention at that time. This was pretty grim, as I had joined up a week after he got BCMD and worked up to LTC, and I didn't want to see it removed. I applied for BCMD myself after a huge debate between Zander and Joah, but they waived me and I got the position on the same day as the app. But one thing that has always stuck with me was the words Joah said in that interview. "If you don't get the battalion active within the next two weeks, we will be removing it.". This was the icing on the cake. There was a long road ahead, and I'd like to keep it attentive to the subject at hand, DU. 4 will refer to numbers and income. 4. While the first few weeks of the battalion were otherwise slow but constant in numbers, however it did begin to pick up. This was not only due to my constant push and strive to recruit anyone and everyone I could, but the main factor and the only reason I did get as many recruits as I did was because of server population. These two words right here are the sole reason that I believe, at the battalions current state, and the servers current state, my decision is concrete. My DU was one of the most active, dawning over battalions like 501st or 212th and outshining them in our numbers most every day. And I'm not the only BCMD to have done this, there are others down the line like Dennis who have achieved these numbers at points. But, this was due to how well off the server was in these times. Even in the second rendition of endor, before anaxes, there was plenty enough income for the battalion itself to strive. This just can't be achieved right now, in my eyes, and that leads me to 5. 5. Battalion clutter. Simple as. I currently see it as there's too many battalions with too little numbers, which only takes away the income to other battalions. With how vastly spread out our choices are, it's easy to overlook the concept that we just don't get enough people to maintain balance between them all. In a perfect world, yes, the number of players were have now is enough to keep all of them at atleast 10+ people a day. But that's not how it works. People are attracted to mainstream battalions first and foremost, i.e. 212th and 501st. With that known, those will always be ahead of the curb. Past that, this server really works on CTs joining whatever the living hell they feel like. You're lucky if you can pull them in half the time, due to them being minges. That said, this ties to 6. 6. At last, the main and sole reason I personally think DU may need to have a break, is the fact that this is not the first time they have been down in the slumps. I mentioned that this is a repeating image multiple times prior in my post, and right now, all I see is more of the same. I get backing up battalion who have these up and down phases, hell all of them do. But behind current understandings of the battalions culture itself, as well as other reasons listed such as battalion number spread, server activity, and general incentive to make this battalion fundamentally fit and work on our server, it's running it's course. Now with all on my opinions stated, I will personally leave my vote to a +1 due to the outlying nature of how many factors have to be considered and talked around for this battalion to even be a thing. Seeing as it's what pushed me and made me on the server, I will always love DU to the grave, but maybe that's where it belongs right now.

Small is exactly what we want. Main server isn't catered to only events in the grand scheme of things, and making the map bigger would only create more issues. For example, extensive has seen a lot of updates since the last time we played it, and the more KingPommes does to that map, the worse it gets in terms of performance. I can tell you right now that the second we switch to that map and sit on it for at least 10-20 minutes, the complaints about lag and the pure horror of hosting an event on it will be catastrophic. Another issue with having the map itself expanding out into a bigger size would be the fact that you just won't run into anyone as often as you should. We want people to see one another in multiple spots, and with extensive, there'd be one or two meeting spots at most. Yes, it's great for RP, but if times call for it that's exactly why we have event server.

+1 Actual blessed suggestion

This is more of a question for someone like @Jad. I personally am unaware of the fact of if our server currently utilizes Fast DL at the current moment or not, but what you mention is most certainly common practice for any gmod server. Typically content from any server will get sent to your steamapps\common\GarrysMod\garrysmod\download folder, as well as your steamapps\common\GarrysMod\garrysmod\cache. This is more helpful than harmful, as the content it's placing into your folders helps you load faster because you have the content, rather than it being deleted every time like you say. There's a couple of key controls server owners have at their disposal to handle how this feature is dealt with, but I'm personally clueless. In my eyes, what @Maverickmentioned is more likely the case, where this is seemingly a client related issue. Maybe your specs aren't the best, or as you said, your EU ping doesn't benefit you. There's lots of factors that come in to play.

I could just make loading screens...but some guy is trying to get me to make high command posters at the same time. What a real shame, y'know?

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

This is likely a limitation of source, knowing how big and expansive jimbo makes his maps. The only solution would be to decrease the general size of the map, which isn't really a priority, nor do I know when it will be. I'll move this to acknowledge and see if I can do more extensive testing along the line at some point, but as stated, not really a priority

This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS

I believe this is an issue due to not being subscribed to the correct content packs. Regardless, I haven't seen nor heard of this for a few months, so I'll move this

Is this still an issue? @Opa or @Noodles

This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS