IC Dev Sprint 2

I_like_pie · March 17, 2021, 3:52pm

Thank you those who responded to our feedback request. We’ve got a nice amount of work logged out of this , including the specific items below that we’re planning for Sprint 2.

Here’s what is planned to be delivered in the next 2 weeks:

1. A galaxy setting for NAPs to be nullified near the end of round, so that a last minute free for all can be possible.

Thank you @You_Fool for the suggestion.

This setting will be by hours before EOR, but future work has been logged to support by tick for different tick speed galaxies.
The hours before EOR should be a galaxy setting (72, 48, etc).
This setting will effect all NAPs, but future work has been logged to support an option where this only effects NAPs that have this as part of their terms.
The mass-nullification will be logged in family news where appropriate.
There will be no warning on triggers about old NAPs; they will completely removed.

2. Galaxy time-based settings to update automatically, so that you don't have to log out and in.

2. Galaxy time-based settings to update automatically, so that you don’t have to log out and in.

Thank you @The_LiGhTgUnS for the suggestion and @You_Fool for the additional info.

Any expiry of a time-based galaxy setting should not require a player to log out and in for the change to work.
Future work has been logged to optimize how this will work in the long term, as this change in the short term may negatively impact server performance.

3. The rankings on your profile page to be automatically updated, so that your round history is accurate.

3. The rankings on your profile pages to be automatically updated, so that your round history is accurate.

Thank you @TheBigOne for the bug report.

After a round ends, rankings should be updated automatically.
Future work has been logged to resume the redesign, as this ranking data handling may change in the long term.

4. Research needs for ongoing round stats, so that you can visualize round progress.

Thank you @You_Fool for taking the initiative to produce this for the community.

The work here is going to be research, meaning I don’t intend to have anything actually done for it by the end of this sprint.

Rather, the goal is to have a clear understanding of what is needed to build this into the game directly, and to log clearly-defined work so that it can be committed to in a future sprint.

Logged Work

This work isn’t planned for this sprint, but has been added to our backlog:

Ready for Development

These are mostly defined and ready to be picked up. This list does not reflect prioritization.

The ability to report other players, so that you can help improve the experience for everybody.
The ability for players to block/ignore other players, so that you have more control over your conversations.
Portal cost to be the same on single-build and multi-build pages, so that you have a consistent sense of cost and value. (@The_LiGhTgUnS) — post
Coordinates format to be standardized, so that the game is easier to understand. (@Hala) — post
Add notes to a planet from the planet page, so that you can keep track of misc information. (@The_LiGhTgUnS) — post
Add notes to planets from list and system views, so that you can more easily manage information.
Recall specific amounts of units from deployed fleets, so that you have more control of your military. (@MEMEGA) — post
A countdown timer for end of round, so that you can plan for EOR jumps and/or EOR battles. (@Exposed) — post
An email notification before EOR, so that you can plan for EOR jumps and/or EOR battles.
A suggested build before EOR, so that you can consider fleet jumps for EOR jumps and/or EOR battles. (@TheOldSchool) - post
An per-NAP option to expire near the end of round, so that a last minute free for all can be possible for those who want it.
A galactic event that nullifies NAPs, so that there are new opportunities to attack. (@The_LiGhTgUnS) — post

Needs Refinement

These need refinement, possible research, and/or have unanswered questions. This list does not reflect prioritization.

Website to perform better under heavy load
Website pages and interactions to respond as fast as possible
New rounds to begin without dev involvement, so that our dev resources are being used efficiently.
Schedule and communicate planned dev/admin hiatuses, so that I do not experience as much stress and potential burnout.
Explore “SCORE” business plan as mentioned by Randak from pbbg.com
Define a process for posting our video hangouts to IC’s YouTube channel.
Define a process for posting audio from our video hangouts to IC’s soundcloud channel.
Define a process for sharing our hangout content on various social media.
Plan next video hangout.
Support multiple evolutions.
Archive data from and shut down our old inactive server.
Optimize the game’s memory usage.
Fix high memory usage on the wiki.
Adjust monitoring and alerts for the wiki.
Fix high memory usage on the blog.
Adjust monitoring and alerts for the blog.
Clarify rules on impersonation.
Create tool to resolve impersonation reports via an admin interface
Integrated chat experience
Add IC’s various services to the server status report page
Improve the family join process and balance
Ongoing territory grouping visualization, so that you can see conflict zones and changes in control.
An easier process to make territory groupings, so that creating them manually requires less time and effort.
:99 to be supported in the system list tool (@The_LiGhTgUnS) — post
build silenz.org tools functionality directly into the game
replicate “IC Tools” functionality directly into the game
make it more clear to players when they are in p-mode or near it
Galaxy settings to be returned from a cache, so that we reduce db hits and improve page load times.
Resume/recover bootstrap-vue redesign work
Community Twitch Stream/Update/Hangout sessions

The focus for Sprint 2 is feature work and bug fixes based on community feedback.

Hala · March 17, 2021, 4:56pm

Looking good Pie!
Question: how did you come to this prioritisation of the backlog? As in: how did these items end up in the upcoming sprint?