HTTP 200 OK
Allow: GET, POST, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept
{
"count": 65,
"next": "https://swarfarm.com/api/v2/news/?format=api&page=2",
"previous": null,
"results": [
{
"id": 68,
"url": "https://swarfarm.com/api/v2/news/68/?format=api",
"title": "SWARFARM shifts to Bestiary Only",
"body": "Hey guys, QuatZo here – I’ve been the only developer working on SWARFARM since early 2021. Some of you might also remember me from SWStats. Unfortunately, I’ve got some bad news – SWARFARM’s going to be scaled back, and only the Bestiary feature will remain. The account management, profile sharing, and game log collection features will all be removed, and with them, all user accounts and data. The login option will disappear, and the Bestiary will be the main (and only) feature available. Below is more information about this decision and some history on the platform.\r\n\r\nI don’t remember much from the time when Porksmash was managing SWARFARM, so I’ll start from October 2020, when he announced that he was stepping down and looking for someone to take over the project. I decided to do it because I had the technical skills, was an active Summoners War player, and used SWARFARM regularly to manage my account more effectively. I was also running SWStats, a tool used on the official Summoners War Discord, which helped players find popular builds for monsters via a bot. This gave me the confidence to take over, and by December 2020, I was officially in charge.\r\n\r\nThings were going fine until September 2021, when my life changed drastically, forcing me to step away from both Summoners War and third-party apps like SWARFARM and SWStats. For SWARFARM, I kept the Bestiary up to date, but SWStats was left abandoned. I thought I’d come back to the game and the projects at some point, but it turns out life had other plans.\r\n\r\nBy early 2022, things calmed down a bit, so I thought it was time to get back into it... but I had lost interest in the game. Although I couldn’t get back into Summoners War, I still felt like I owed it to the SWARFARM community to keep things running. I tried to make some progress but found myself lacking the motivation needed for real development. The only big feature planned was merging SWARFARM with SWStats, but as you know, that never happened. In April 2022, I officially shut down SWStats so I could focus on SWARFARM.\r\n\r\nMonths went by, and in June 2023, Com2us announced the \"Reloaded\" update (v8.0.0). Usually, when a new update dropped, I’d hear from streamers and developers, which gave me the push to return to working on SWARFARM. I knew how much players relied on it, and that tools like SWOP and SWGT depended on our API. For the next three months, I worked on improving the platform, adding new filters to reports, new rune sets (like Intangible), and finally, the long-awaited RTA section.\r\n\r\nBy the end of 2023, I re-engaged with the player community. I had mostly been in touch with content creators and developers, but a year ago, I felt ready to start working on the app again. You can find posts from September 2023 on the SWARFARM homepage, where I shared updates about the platform, future plans, and priorities. The last update was on September 12. Two days later, on September 14, Com2us rolled out v8.0.9, which included \"security enhancements\" that unfortunately disrupted third-party tools like SWEX (for collecting data), SWGT, and SWARFARM (for aggregating that data). This completely killed my motivation. All the drive I had to keep working on SWARFARM was gone. We waited about a month and a half (if the dates aren’t exact, forgive me – I’m referencing posts from the SWARFARM homepage) for a fix for SWEX, which came in v8.1.2. However, not everything was fully restored – some data, like boss stats, remained inaccessible. I lost my remaining motivation and reverted to just keeping the platform running.\r\n\r\nAfter discussing things with Porksmash (the creator of SWARFARM who still funds the servers through Patreon), we agreed that neither of us has the time to keep supporting the platform. We can’t keep up with all the game updates – I learn about them from people like Cerusa or Seiishizo. As a result, we’ve decided that, at some point (I’m not sure exactly when, as it depends on my schedule), SWARFARM will be scaled back to just the Bestiary. All user data will be deleted, and only administrative accounts will remain.\r\n\r\nAlso, the Patreon will be closed. On behalf of both myself and Porksmash, I want to thank all of you for your support. All funds have gone toward keeping the server running, and we never made a profit from the project. We’ll be switching to a cheaper and faster server (finally moving from HDD to SSD), as we no longer need such a large infrastructure. 90% of the database was made up of log files.\r\n\r\nI’m sorry things have ended this way, but life happens.\r\n\r\nAll the best to the community and the game.",
"created": "2024-09-07T05:28:12-07:00",
"sticky": true
},
{
"id": 26,
"url": "https://swarfarm.com/api/v2/news/26/?format=api",
"title": "Discord server for organizing development",
"body": "I've created a discord server for people interested in contributing code to SWARFARM. This will be where development efforts are organized, and an easy place to answer questions and share my experience in the codebase. If you're interested, first take a look through [the repo](https://github.com/PeteAndersen/swarfarm/) on GitHub and get yourself set up with a development environment. If you want to work on something, [join the Discord server](https://discord.gg/EuJyvTGkxQ) to discuss it and/or ask questions.\r\n\r\nI'd really love to get a small core group of people who can continue to develop SWARFARM into the future. If you're interested in taking on this role, please join the [join the Discord server](https://discord.gg/EuJyvTGkxQ) and send a message to porksmash#1344.",
"created": "2020-11-03T20:38:54-08:00",
"sticky": true
},
{
"id": 67,
"url": "https://swarfarm.com/api/v2/news/67/?format=api",
"title": "Changes after v8.1.5 Update",
"body": "- Bestiary and skill effects updated w/ new balance patch\r\n- Moved from old Building system to new Skill Level system (**re-import your profile if you are missing monster stats**)\r\n- Deleted references to old Building system (building tab, option to edit and calculate missing points, building comparison between users, etc.)\r\n- Added intangible artifacts\r\n- Optimized data log collection (at least 3x faster)\r\n\r\nIn addition, Com2us changed the way of getting (and informing) dungeon data from the server, at the start of the run. It means that we are no longer able to get the boss stats from GB, DB, SB, ... As of now, dimensional hole, raid and rift still collects that. I'll investigate it further, but at the first glance I didn't see any command that could contain that type of data.",
"created": "2023-12-01T00:47:58-08:00",
"sticky": false
},
{
"id": 66,
"url": "https://swarfarm.com/api/v2/news/66/?format=api",
"title": "Cease of archiving logs",
"body": "Because of incoming v8.1.4 update & overall drop rate improvements, I've decided to temporarily disable task responsible for archiving 2-week old data logs. Thanks to this, you will be able to compare old drop rates to new ones. It means that latest data log you can check, will be from 1st November.\r\n\r\nAs mentioned before, the ability to check archived logs will be available in new SWARFARM version (in progress).",
"created": "2023-11-14T22:36:18-08:00",
"sticky": false
},
{
"id": 65,
"url": "https://swarfarm.com/api/v2/news/65/?format=api",
"title": "Status of SWARFARM after update v8.1.2",
"body": "With today's patch, there were some changes related to 3rd party tools, which resulted in the SWEX ability to collect data as before the v8.0.9 update. It means that we are collecting data logs again.\r\n\r\nOn the side note, I've archived all data logs before v8.1.2 update. The archive will be browseable in new version.",
"created": "2023-10-27T10:12:00-07:00",
"sticky": false
},
{
"id": 64,
"url": "https://swarfarm.com/api/v2/news/64/?format=api",
"title": "Status of SWARFARM after update v8.0.9",
"body": "With the newest patch, I'm forced to make some changes in how SWARFARM will function in the future in reference to the news I've made 2 days ago. In short, we are no longer able to store data logs, or update dungeon monster stats. Xzandro explained the reason for these changes, so let me quote him.\r\n\r\n## Quote from Xzandro\r\n> After today's patch, com2us introduced new encryption keys/methods on pretty much all game events. Only event that is unaffected is the one, where you directly export your profile data file, to use in for example SWOP and SWARFARM. This seems to be a deliberate decision by com2us, because there is no way, that this is coincidence.\r\nYou could think that this is good news, but it is not really. Although SWOP is widely unaffected, SWARFARM's data logs will not work currently and pretty much all other 3rd party tools, that need automatic data other than the profile file provided by SWEX will not work.\r\n[...]\r\n Release of SWEX 0.0.55\r\nI [released a new version](https://github.com/Xzandro/sw-exporter/releases/latest), that removed the `Disabled Merge sealed monster storage` option and set it to false by default, because this option currently prevents SWEX from exporting your profile data, since com2us uses new encryption there too.\r\nSo either manually disable the `Disabled Merge sealed monster storage` option in the SWEX settings or update to the newest version.\r\n\r\nAs you can see, if you download newest SWEX version (or *disable merging sealed monster shrine storage*) you should still be able to export your profile data, but that's all.\r\n\r\n## What works and what not?\r\n1. *Bestiary data*, f.e. skill multipliers - **WORKS**; SWARFARM wasn't using SWEX to obtain that data and its source hasn't changed\r\n2. *Profile data*, f.e. list of monsters, fusion - **(PARTIALLY) WORKS**; as mentioned by Xzandro, profile command is still functioning properly and the only thing which may be missing (I didn't check that yet) is list of monsters located in sealed monster shrine storage\r\n3. *API* - **WORKS**; strictly connected to Bestiary, works as intended\r\n4. *Data logs* - **FROZEN UNTIL FURTHER NOTICE**; with commands from all events we've been gathering (dungeon runs, shop refreshes, wishes etc.) being encrypted, we can no longer extract the detailed info from them; it means that we no longer can keep an eye of drop rates changes made by com2us; it's probably biggest hit taken by SWARFARM in this update; basically 1/3rd of the site becomes obsolete\r\n5. *Boss & wave stats* - **FROZEN UNTIL FURTHER NOTICE IN v.8.0.8**; this data was being parsed from command at the start of dungeon run; since we no longer can get that data, there is nothing I can do; reason same as for data logs\r\n6. *Personal logs* - **FROZEN UNTIL FURTHER NOTICE**; same as Data logs\r\n\r\n## What about SWARFARM changes announced 2 days ago?\r\n1. *Optimization of profile parsing* - **UNAFFECTED**\r\n2. *Database optimization* - **UNAFFECTED**\r\n3. *Archive system* - **UNDECIDED**\r\n4. *Browsing archived data* - **FROZEN UNTIL FURTHER NOTICE**; there will be nothing to compare to\r\n5. *Fixing deadlocks* - **UNAFFECTED**\r\n6. *Migrating to front-end framework* - **SPED UP**\r\n7. *Creating more optimized API v3* - **UNAFFECTED**\r\n8. *Feedback & github issues cleanup* - **UNAFFECTED**\r\n9. *Live sync* - **FROZEN UNTIL FURTHER NOTICE**\r\n \r\nThe priority list has changed a little bit. Optimizing data logs seems quite meaningless after the update.\r\n\r\n## Final speech\r\nI'm really sad that a lot of tools people were relying on will stop working. Community devs dedicated their personal time to make something for other members and it has been rendered useless by just one change. Com2us knew what they did, which they showed by profile parsing still being intact. Instead of coming to terms with some of the community's ideas, popular tools and starting to live in synergy with us, their actions have taken many of us back to the days of Excel. Most of you will probably not see any problem in actions taken by Com2us, because bestiary has been unaffected and most popular tool (SWOP) still works and it is ok, understandable.\r\nRight now, when Com2us makes some change to drop rates, we won't be able to collect as big simple size as before. People will need to start manually record their runs, which will result in... 2k, 5k? In comparison to SWARFARM's 2-weeks timespan 200k+ (as of writing this news, GAH has over 260k records). With Beast Horn drop rate being incredibely low (~1/2000), one person can not collect reliable data.\r\n\r\nWe'll see how it goes, but I don't expect Com2us to put resources into providing reliable and **secure** API for community tools. Neither of starting to show drop rates or skill multipliers in game either.",
"created": "2023-09-14T04:15:32-07:00",
"sticky": false
},
{
"id": 63,
"url": "https://swarfarm.com/api/v2/news/63/?format=api",
"title": "Status of SWARFARM",
"body": "It's gotten a little dry here, *huh*? Don't worry, it's not a goodbye message. *Right?* ***RIGHT?***\r\n\r\n## Introduction\r\nSince the Reloaded Update, I've been adding new stuff which may or may not be useful for you as users, for ex. generating reports by filtered date or new \"Rune Builds\" menu option in Profile. Some I announced, some did not. But... I've neglected the site's performance for too long. You know that, I know that, everyone knows that. The site was running poorly, there was a lot of API errors, people have been (and still are) seeing \"Server Error (500)\". Lately I've heard a lot of phrases like \"Great, SWARFARM is down ***AGAIN***\" and probably it's the push (or rather slap in my face) I needed.\r\n\r\nWith that in mind, I would like to apologize for not taking care of SWARFARM in terms of performance and stability. All I did in last one and a half, or even two years, was updating Bestiary with balance patches and new monsters. Would I call it strange? It depends. I'm not playing Summoners War for even longer, but I'm still responsible for this site. That lack of maintenance led to the problem I'm facing today. In order to resolve it, I'm currently working at a lot of things you may not even notice.\r\n\r\n## Status\r\n1. *Optimization of profile parsing* - **IN PROGRESS**: as of today 4x faster locally, aiming to 10x; on server it will be even faster because I'm cutting off thousands of SQL queries (hi fellow IT guys) which doesn't have that much of an impact on local database with only one ongoing connection\r\n2. *Database optimization* - **IN PROGRESS**: as of today 15x faster queries, aiming to... as fast as possible\r\n3. *Archive system* - **IN PROGRESS**: instead of storing everything in one place, old data will be moved to other (\"archived\") tables; it should speed up generating reports\r\n4. *Browsing archived data* - **PROTOTYPING**: I'm still thinking of the best solution to allow seeing old reports, for ex. from B12 before Reloaded update or B10 year ago\r\n5. *Fixing deadlocks* - **PLANNING**: IT guys will know what I mean, but basically it's the situation when you are in a store and want to take milk from the shelf, but there is a man standing near it, so you pretend to look at the eggs until he goes; but of course, he waits until you go so he can take the eggs from shelf you are standing next to; you are both waiting for each other to move; the same happens with database connections in some cases\r\n6. *Migrating to front-end framework* - **RESEARCH PHASE**: basically, Django Template Language isn't the best. Also SWARFARM code may be labelled as legacy; it still uses Django 2.2 where there is official 4.2 moving into LTS and 5.0 in development. Using proper framework would definitely improve user experience, but sadly I'm not a graphic designer and it's quite hard for me to come up with good design. Also, upgrading backend libraries could potentially increase the performance (with Python 3.11)\r\n7. *Creating more optimized API v3* - **RESEARCH PHASE**: at first I need to collect as much data as possible about how often API v1 & v2 are being used, which one is inefficient, what data is missing; of course v1 and v2 will remain functional for the sake of backward compatibility\r\n8. *Feedback & github issues cleanup* - **TO DO**: basically, fixing errors reported there, adding new stuff based on feedback\r\n9. *Monster reports* - **ON HALT**: some of old users may remember that SWARFARM started asking for consent to use your data in (un)anonymous reports about monster builds; something similar to old SWStats or in-game stats provided by Com2Us; the modal still shows for new users, but unfortunately I'm not planning to work on that, at least for now. Right now generating such reports is inefficient; maybe I'll get back to it once I do the performance & stability stuff; no promises here\r\n10. *Live Sync* - **TURNED OFF/ON HALT**: too much workload for database right now, we'll see after performance & stability stuff\r\n\r\n## Update? When?\r\nNo date announced. I don't want to work under pressure of time. I want to make this update as good as possible.\r\n\r\n## Known limitation\r\nServer in which SWARFARM is running still uses HDD instead of SSD. It drastically decreases the capabilites of our database. The best option would be to upgrade from current dedicated server to newer one, with SSD and better parameters, buuuuut... It's a lot of time from planning, through testing to executing to set everything up so you won't notice any downtime.\r\nMoney is also a factor, infrastructure is not free. Porksmash's policy was to make SWARFARM completely free no matter what. I stand by that. So don't worry, there won't be any paywall, neither ads. That being said, all that stuff I'm working on is so we don't need to move to better/newer dedicated server. First software, then hardware. \r\nThe only \"income\" for SWARFARM is Patreon, which still being taken care of by Porksmash. From what I know, current patreons donate enough to make the server pay for itself with a slight excess. As you may be guessing, it's not enough to get better/newer server. In my country, something great for SWARFARM costs about 90$/month, not including backup storage etc.\r\nAs I mentioned earlier, I'm not going to implement any paywall or add ads on the site. I'm grateful to you all for supporting this project and just wanted to let you know what limitations we are facing. **Thus, I would like to thank all the patreons for support you provide.**\r\n\r\n## Some numbers for nerds like me\r\n1. Almost **600 000 000 records in data log** tables since March 2019; these include runs, shop refreshes, wishes, drops; basically everything we collect automatically through SWEX profile\r\n2. In just september (~12days), we've collected over **7 000 000 more data logs**, which means that SWARFARM gets at least **7 requests from SWEX per second**; not to mention visitors, auto profile upload, and all these other community tools (like SWOP) getting data directly from us\r\n3. We store almost **10 000 000 monster instances**, from which \"only\" ~130 000 are LD5's (incl. farmable)\r\n4. Monsters? Who cares... **Runes** is what's important in this game - currently approx. **30 000 000** in our database\r\n5. What about you? Over freaking **50 000 registered users**!\r\n\r\n\\* I will share more data after performance & stability update\r\n\r\n## Worth mentioning\r\n- Xzandro - for being... Xzandro, everyone knows him. On a serious note, for all the help he gives\r\n- Cerusa - for taking care of all skill effects, which need to be updated manually every balance patch\r\n- Seiishizo - for providing a good feedback and promoting site\r\n\r\n## Pepperidge farm remembers\r\nDid you know that *Porksmash was working on [SWARFARM UI version back in 2019]( https://alpha.swarfarm.com/bestiary)? It hasn't been touched since then*\r\n\r\n## Last words (feel free to ignore)\r\nBecause of my professional life, I forgot how fun it is to work on side project in which you don't have deadlines (except site-breaking updates) and are in full control. I've been burned out because of stuff I had to do and had no control over no matter how stupid it was. Happily it changed and now the fun of working as a programmer is back. So I hope that I'll be working on this site for a little longer.\r\n\r\n*By the way, is anyone reading these news? lol*",
"created": "2023-09-12T15:07:06-07:00",
"sticky": false
},
{
"id": 62,
"url": "https://swarfarm.com/api/v2/news/62/?format=api",
"title": "Rift Beast filter by Damage, up Personal Logs max threshold",
"body": "Hey! Today I've added option to filter Rift Beasts reports by damage (score), next to filter by date. You can use both, only one at the same time or neither. Keep in mind that it generates new reports, which may take some time. Don't spam the \"Filter\" button, thanks.\r\n\r\nAlso, small QoL for personal data logs. I've increased maximum threshold from 2k to 4k. I'll keep observing how long it takes to load data. If server can keep up, there is a possibility to increase the cap even further.",
"created": "2023-07-16T07:30:33-07:00",
"sticky": false
},
{
"id": 61,
"url": "https://swarfarm.com/api/v2/news/61/?format=api",
"title": "New Rune Builds section & uncovering RTA Builds",
"body": "Hello everyone. Today I have 2* new updates for you.\r\n\r\n1. Some of you may know that for a loooong time, while checking monster details, there was RTA section hidden behind blur with \"IN PROGRESS\" message. Guess what, it's now visible. Basically, it shows monsters' equipped RTA build. The only difference between RTA & normal build is that you can't edit RTA build yet... And I don't know when (if) it'll be available.\r\n\r\n2. By checking your Profile, you should find new option in the side menu, under \"Artifacts\", named \"Rune builds\". It shows your rune build stats WITHOUT taking into consideration monster data - it sums runes and artifact bonuses, then displays it. Basically, you can compare different builds in term of hard data without worrying about monster base stats. It also adds set effects, so having active Rage set will result in +40% CRIT DMG, Swift set in +25% SPD etc.\r\n\r\n\\* Also, some other fixes you wouldn't even notice.\r\n\r\nI hope you find it helpful. Let me know if you experience some issues with new features.",
"created": "2023-07-10T15:17:46-07:00",
"sticky": false
},
{
"id": 60,
"url": "https://swarfarm.com/api/v2/news/60/?format=api",
"title": "[BETA] Date filter for dungeon reports",
"body": "Hello everyone. Since Com2Us decided to (once more) change drop rates in new dungeons, even before 2-week timespan (which we use as a standard in SWARFARM), I've added a way for you to check drop rates by given time frame. In order to use this feature, just go to given dungeon (i.e. [GBA2](https://swarfarm.com/bestiary/dungeons/giants-keep-abyss/2/) [sadly, it's not Game Boy Advance 2]), scroll to the section with sample size and you'll see quite simple form filter. Just select dates and filter.\r\n\r\nFYI, 2-week is still our standard timeframe, and you can't go higher than that. If you filter by more than 2 weeks, it'll shrink in respect to end date.\r\n\r\nIt ain't much, but it's honest work.",
"created": "2023-07-04T09:06:23-07:00",
"sticky": false
}
]
}