Existing players used to logging in with their character name and moo password must signup for a website account.
- F9DFCQ 1m Why work when you can update your @wow?
- Burgerwolf 58s PANCAKES
- Sivartas 5s
- Rillem 5s Make it personal.
c Logic 11s
- Dale 2s
- cata 12s
- Diamond 1h After Winter, must come Spring.
- SmokePotion 20m Right or wrong, I'm getting high.
- baewulf 7s
- BubbleKangaroo 1h
- zxq 18s Blackcastle was no ordinary prison.
- NightHollow 52m
- LadyLogic 26m
- Vanashis 2h
a Mench 16m Doing a bit of everything.
And 27 more hiding and/or disguised
Sindomedome logo
a cyberpunk roleplaying game
banner art by Grand Failure
Connect to Sindome @ moo.sindome.org:5555 or just Play Now
  • BgBB
  • Ideas
  • Pagination for node-content-search
  • And maybe only show one match per node?

Pagination for node-content-search
And maybe only show one match per node?

Login to post. Membership required.
Jump To
Newest Post
node-content-search maxes out at 25 results. It might be nice to add a page number as an optional 2nd argument to be able to view additional results. Pagination would mean that 100 results could be retrieved but it would take up 4 whole commands. You'd have to exhaust several commands (or even program uses) if you wanted to do a broad grid search.

Bonus: Maybe only show one match per node?

One issue with the current implementation is that each match shows up as a separate result, so you could conceivably block all results by creating a page that has 25 instances of a match if you know someone is going to search for it.

By ikunaut at Aug 14, 2025, 12:01 PM | 0
Sorry for double post. Had some further thoughts for how to solve this and I'm not sure what is easiest to do in the MOO so I figured they'd be worth adding:

I think that having open-ended AND/OR/NOT in the search query is probably too much to ask for since it is so open-ended. But something like this would probably completely solve what I am running into:

1. Only return each node once in the results

2. Order results so that the most recently edited nodes appear first

3. Add page number and maybe excludes to the args

4. Make the args accept comma-separated values

#node-content-search

Argument: STRING – Comma-separated values (Match if ANY are found)

Optional: INTEGER -- Page number

Optional: STRING -- Comma-separated values (Exclude if ANY are found)

#endnode-content-search

(I think put the excludes after the page number because having to put a "1" when you don't care about pagination seems more reasonable to me than having to put in something to exclude just because you want to see page "2")

By ikunaut at Aug 14, 2025, 1:41 PM | 0
Jump To Oldest Post