Topic on Talk:Teams
From Blaseball Wiki
- (cur prev topic) 00:40, 15 January 2023 . . Pokeylope (talk | contribs) commented on "standardizing new rosters" (Yes, but not trivially. The External Data parser functions don't support sorting, so I'd have to move it into Lua. I'll take a look at do...) . . +217
- (cur prev topic) 00:05, 15 January 2023 . . KCToxic (talk | contribs) commented on "standardizing new rosters" (Is it possible to have the new roster display order players by their orderIndex field? For some reason both the frontend and backend list...) . . +245
- (cur prev topic) 23:31, 14 January 2023 . . Pokeylope (talk | contribs) commented on "standardizing new rosters" (I added {{NewRosterDisplay}} which pulls from the new API. It doesn't display buried players but works otherwise.) . . +143
- (cur prev topic) 12:48, 14 January 2023 . . Moondragon (talk | contribs) commented on "standardizing new rosters" (I like "The Shadows are currently empty or unavailable" as a placeholder! Having the collision victims visible on the site is good: I can...) . . +198
- (cur prev topic) 03:29, 14 January 2023 . . KCToxic (talk | contribs) edited a post on "standardizing new rosters" . . +63
- (cur prev topic) 03:28, 14 January 2023 . . KCToxic (talk | contribs) commented on "standardizing new rosters" (Important update: Shadows are now visible to teams that have them on the website. Therefore perhaps we can instead go for something like...) . . +189
- (cur prev topic) 02:17, 14 January 2023 . . KCToxic (talk | contribs) commented on "standardizing new rosters" (I think a standard is useful. I think the team pages should switch to using RosterDisplay's manual fields, just to make it easier to edit...) . . +899
- (cur prev topic) 01:57, 14 January 2023 . . Moondragon (talk | contribs) commented on "standardizing new rosters" (hi i didn't know where else to put this and i have no idea if it's gonna get seen, oh well anyway i think we should come up with a standa...) . . +906