-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Random .ans files does not appear to be working as it should #1635
Comments
Just name them welcome.0, welcome.1, welcome.2, etc. no need for .ans. Also, place them in gfiles/menus/wwiv/gfiles/ for now. We may change this location to just gfiles/. Thanks for submitting issues, btw. -=<(xenos)>=- |
Of course it had to be that easy, and of course I try every alternative but those, :) thank you! |
PS could we difficult to add it to all .ans files as an option? I'd love to have random logoff.1 2 3 etc... system.ans to system.1 2 3 etc.. ? I would think like with .c132.ans there would be a way to more broadly change how WWIV sees any files prioritizing .1 2 3 etc .. then .c132 or .c160.ans then .ans, .msg, and down the line .. ? Or does this idea affect multiple .cpp files and is a more of an overhaul? |
Adding which files to randomize is easy. We just need to identify which ones. If you can come up with a list, I can work on making those randomly shown. The key file that WWIV looks for for randomization is basefilename.0. I might work on something to make the randomizable files configurable in |
I've tried different variations of naming files and am unable to get random welcome.ans files to work as it should. If I have:
welcome.ans
welcome.001.ans
It only displays welcome.001.ans
If I have welcome.001.ans and no welcome.ans it displays nothing.
If I have welcome.001.ans and welcome.002.ans and welcome.ans it only displays welcome.001.ans
If I have welcome.ans and welcome002.ans it only displays welcome.ans
I've tried many other combinations including welcome1.ans welcome001.ans, etc.. and only a singular file will ever display.
What would be the correct syntax and or has this feature been removed?
Thank you!
The text was updated successfully, but these errors were encountered: