fontaine

Added maps de_forlorn and de_amelia.

Wow 1st
 
Thank you!
 
Someone wants to fight some people for top donation.

Wow 1st
 
Thank you!
 
Someone wants to fight some people for top donation.

Wow 1st
 
Thank you!
 
Someone wants to fight some people for top donation.

Wow 1st
 
Thank you!
 
Someone wants to fight some people for top donation.

Thank you, SirMeowsAlot for your donation of 375.00 USD!
Your donation will be put to good use, and helps keep this community running.
 
Thanks for the support,
Syndicate Gamers Staff and Community
 

"do black people have a flag?"

A quick look through the forums would of brought you to this post in our Recruitment forum
 
 
 
 

I JUST WANTED TO GIVE MY MONEY

I JUST WANTED TO GIVE MY MONEY

I JUST WANTED TO GIVE MY MONEY

I JUST WANTED TO GIVE MY MONEY

I JUST WANTED TO GIVE MY MONEY

I JUST WANTED TO GIVE MY MONEY

So apparently some of the bugs we had were because our themes were not upgraded with the 4.1.9 release. I have gone ahead and updated all of our themes. In the process everyone's theme was reset back to default (unfortunately, no way to avoid that). If you notice any problems, please post in the Forum Upgrade Bugs forum. 
 
Spectrum updated to newest version (fixes unread content feed and other bugs) Brave updated to newest version (fixes unread content feed and other bugs) Dashboard updated to newest version (fixes unread content feed and other bugs) Subway updated to newest version (fixes unread content feed and other bugs) Fixed calendar widget display problem
 

Have to wait for the developer to release the new version that doesn't kill our forums.

Hmm weird I'll check out IPB forums and see if other people are experiencing this.

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

I've been gone for a while and was happy to see how welcoming everyone was when I rejoined the servers. Just wanted to show my support to sG! 
 
Thank you for the awesome servers and all the friends I've made so far