Would it be possible in the future that we get a number with each submission?
Like…
You’re number 65 kind of announcement 
Could be an auto mail even, it’s a suggestion ofc
8 Likes
Or, if the entire list was given, like monthly.
And then we can calculate the aproximate date of releases for ourselves.
2 Likes
Seems to not be a set schedule, and depends on what captain is making for the week etc
But then that makes me think with each weekly release we can have it something like:
23-28
(list of new releases for the week)
Numbered releases!
While we also have our numbers from the submission list.
3 Likes
A queue would defintely be very useful
1 Like
Having a good time eating those cakes! ;)
Yes! It’s already much work for Captain
So focusing on what we have for the week in a numbered sequence would give us a chance to know when our turn comes! Provided we are given a number of course!
@KetherTour (You know! Monthly would work more for now when we don’t have a number yet, like perhaps biweekly to make it easier, then if we happen to upgrade we’d be good to go with the numbers)
Yep that’s the whole point… More on the present/still following the weekly set from Captain, and giving projects some time to decide or know an estimate of their release date in advance etc
I think if we also know an estimate in advance chances are people will be more ready compared to suddenly knowing they are next!
3 Likes
:D
Similar scripts i believe also exist
it’s not advanced technology haha
doable, upgradable, or dismissable :D
3 Likes
lol, where did you pull that up from 
It also expects the sheet to track the number of “processed” entries (
CURR_COUNT), and a location to store the last “processed” entries count (LAST_COUNT). This prevents arbitrary sheet updates to trigger a notification to the next unprocessed individual.
- Config sheet that tracks:
- the current checked count (and optionally, a start box in the config sheet)
- a mutable box for the last count (script will update this)
- the submission count (based on non-blank entries)
I guess it could work lol
1 Like
here :D
5 Likes
yes but you have to walk the way through like this :D
3 Likes
haha see ya in the lands of rainbows :D
1 Like
i have no idea, that means i have have to check each day and write it here
no other way to automate it i think, but i rather actually spend the time… making them lol.
24 Likes
lol yup
but check the scripts etc, or if any to automate the process.
if not, we will keep it to the surprises :D more fun lol
3 Likes
I think we can make a list
sometime…
lol
I dunno… I will look into it, cause it would definitely be helpful
any way to automate it?
we gonna have to hire somebody huh
18 Likes
expansion 
2 Likes
it’s a lot, but with each passing week you will find people asking what their project number in queue is,
and with the increase in projects it will be harder to track etc
better to start at 60 than 100 :D !
i found that script but just about that, others were paid services, or consult with someone and see if any possible solutions abound
there must be i think lol
but it starts with us not asking really haha
3 Likes
Rather, why not we think of maintaining a separate thread for the nft sequence, and leaders enter the details in it as soon as google form submission is done. what’s say ?
But there is a chance that few leaders miss entering the details intentional or unintentional, but that count should be trivial.
I think this will minimize the workload on the captain, and the onus is on us.
we can maintain something like chronologically,
S.No:
Project Name:
Submission time: HH:MM BST
9 Likes
yeh but i think
some are private, well i guess they can just add private if they wish to keep it non public
17 Likes
The only way this can work is if it’s mandatory
2 Likes
Yea, the private ones needn’t even have to mention the project name or something. Just enter the serial number and submission time, that should do .
5 Likes
For private ones, add your username to your submission
In the NFT name, at the end l put
(Submitted by SC448)
1 Like