/prog/ Challenge α: BBPong

This is a rudimentary game of pong, implemented in BBCode:

|oooooo|
|oooooo|
|oooooo|
|oooooo|
|oooooo|
|oooooo|

The challenge is to output to stdout a string that will compile to this game. For reference, canonical form (for all you XML-using boomers):

[spoiler]|[spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler]|[/spoiler]
[spoiler]|[spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler]|[/spoiler]
[spoiler]|[spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler]|[/spoiler]
[spoiler]|[spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler]|[/spoiler]
[spoiler]|[spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler]|[/spoiler]
[spoiler]|[spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler][spoiler]o[/spoiler]|[/spoiler]

, and the sexpcode form:

{spoiler |{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}| }
{spoiler |{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}| }
{spoiler |{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}| }
{spoiler |{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}| }
{spoiler |{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}| }
{spoiler |{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}{spoiler o}| }


Notes:
☙ 6 rows. 6 columns for the ball, plus two for the paddles.
☙ It is not necessary to output any of the reference implementations poasted above. What is necessary is an output that will result in BBPong when parsed as a tinychan poast.
☙ No esoteric languages (except perl).
☙ Smallest program wins.
☙ Deadline is 20210331Z.

i can’t figure this one out. sorry

a='{spoiler ';s=`${a}|${a}o}${a}o}${a}o}${a}o}${a}o}${a}o}|}`;c=()=> console.log(s);c();c();c();c();c();c()

Made it far shorter:

a="{spoiler ";b=a+"o}";console.log((a+"|"+b.repeat(6)+"|}\n").repeat(6))

^{(This is the first time I'm actually enjoying /prog/.)}

omg optimized

r=s=>s.repeat(6);a="{spoiler ";b=a+"o}";console.log(r(a+"|"+r(b)+"|}\n"))


wait, thats longer. shit shit shit. im out of ideas

bampu pantsu for more /prog/ramming, even if it's normie-tier code golf

even if it's normie-tier code golf

as well as very old pasta

>>8
Does not matter. Anything to make people poast code here is a noble attempt.

//Comments with PHP-style verbosity for the full
//effects that each of them cause. It will make
//for a much better reference from the code itself
//and much easier to read and understand.

s:"{spoiler ";{s,"|",(,/{s,"o}"}'!6),"|}"'!6}

>>11
virus! don't run.

>>11
You killed admin--kun's poor sexpcoder

Lispmark is better than sexpcode.

eels is a horse fucker

POOR PEDO

timestamp dubs