周末去围观了艦これ咖啡

嗯最近艦隊これくしょん,简称艦これ实在是非常火,于是虽然咱没有玩但是还是跟着某朋友一起去围观了艦これ和奸笑社咖啡一起合作搞得艦これ咖啡——于是要说艦これ火到什么程度,这次偶们可是大清早不到6点钟就已经赶到店门口了,但这个时候都已经有100来号人排队了ww喂人家11点钟才开始营业诶好不好(摔

嘛不管怎么样好歹是拿到了晚上7点半的入场券,于是偶跟朋友晚上7点半再次来到店内,首先看到的就是店里面的大屏幕的广告,不愧是奸笑社www
IMG_1197
IMG_1205

桌子上的垫板是第一舰队的
IMG_1198

菜单——不愧是奸笑社,价格很好很强大w
IMG_1201

菜单背面是这次的特典
IMG_1203

上菜了——首先是朋友点的祥鶴&瑞鶴
IMG_1211

然后是偶的第六駆逐艦隊丼
IMG_1216

点心首先是偶的ぜかまし(島風)酱w
IMG_1217

然后是金剛的红茶set www
IMG_1218
IMG_1222

店内展示品——里面那件ぜかまし酱的cos服好想要www
IMG_1224
IMG_1226
IMG_1228
IMG_1230
IMG_1232
IMG_1234
IMG_1236
IMG_1238
IMG_1240
IMG_1242
IMG_1244
IMG_1246
IMG_1248
IMG_1250
IMG_1252

当然除开吃了的东西以外还有各种特典,比如吃的东西送的第六舰队和ぜかまし酱的垫板
IMG_1266

以及长门的杯垫以及卡片外加badge 3个
IMG_1270

吃完出来还看见lovelive的痛摩托一辆ww
IMG_1260

话说这次还在秋叶原发现一家新开的专门卖挂画之类的萌物的店(当然卖萌物的店是很多啦,但是以绘师和插画为主题的这应该是第一家),于是进去围观了一下,买了本珈琲貴族的线稿本w
IMG_1264

然后送的袋子竟然是这么大一个www真是赚了
IMG_1262

里面的装饰很漂亮,说实话偶都好想问那家店房租多少好想搬进去住了(喂泥垢
IMG_1194
IMG_1195
IMG_1196

好了这个星期就说到这里吧w

p.s. 话说现在艦これ非常火,那么艦これ里面最火的角色又是谁呢?——毫无疑问绝对是偶家的ぜかまし酱——看看这次的C85的场刊,连续4页全是ぜかまし酱233
Ba4uhJDCUAEiZm7

Author: 星野恵瑠

Mac user, Niji-Ota, Chinese, Now working in Japan at MAGES. Inc., Future's aim is that one day my name can be listed in Wikipedia

9 thoughts on “周末去围观了艦これ咖啡”

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

(;;) (:D) (!!!!) (……) (^o^;) (==) (OoO) (=v=o) more »Note: Commenter is allowed to use '@User+blank' to automatically notify your reply to other commenter. e.g, if ABC is one of commenter of this post, then write '@ABC '(exclude ') will automatically send your comment to ABC. Using '@all ' to notify all previous commenters. Be sure that the value of User should exactly match with commenter's name (case sensitive).